Server data from the Official MCP Registry
SEC EDGAR MCP: search, preview, purchase filings. x402 USDC on Polygon. xpay + Cloud Run upstream.
SEC EDGAR MCP: search, preview, purchase filings. x402 USDC on Polygon. xpay + Cloud Run upstream.
Remote endpoints: streamable-http: https://sec-edgar-filings.mcp.xpay.sh/mcp streamable-http: https://sec-filings-mcp-1065601264332.us-central1.run.app/mcp
Valid MCP server (1 strong, 5 medium validity signals). 6 known CVEs in dependencies (0 critical, 4 high severity) Imported from the Official MCP Registry.
Endpoint verified · Requires authentication · 7 issues found
Security scores are indicators to help you make informed decisions, not guarantees. Always review permissions before connecting any MCP server.
This plugin requests these system permissions. Most are normal for its category.
Remote Plugin
No local installation needed. Your AI client connects to the remote endpoint directly.
Add this to your MCP configuration to connect:
{
"mcpServers": {
"io-github-stagproject-sec-filings-mcp": {
"url": "https://sec-edgar-filings.mcp.xpay.sh/mcp"
}
}
}From the project's GitHub README.
SEC EDGAR structured filing MCP for agents: search_filings, get_filing_sample, purchase_filing. Data lives in Supabase views (fi_listings_portfolio, fi_listings_portfolio_compact) populated by the finance-factory pipeline.
| Read first | File |
|---|---|
| Try without xpay key | docs/TRY_WITHOUT_XPAY.md — Glama sandbox or Cloud Run upstream |
| Distribution (you vs repo) | docs/DISTRIBUTION.md · docs/HANDOFF.md |
| Build / handoff | MCP_FINANCE_BUILD.md |
| Env template | .env.example → copy to .env |
| Glama | glama.json (maintainers: stagproject); build fix: GLAMA_BUILD.md |
| A2A / x402 | docs/A2A.md — Agent Card + payment mapping |
| MCP Registry | io.github.stagproject/sec-filings-mcp — docs/MCP_REGISTRY.md |
| Discovery URLs | docs/DISCOVERY.md |
Template reference: mcp_server.py (patent MCP, unmodified). Runtime: mcp_server_finance.py.
| Layer | How to use |
|---|---|
| MCP (production) | xpay URL below — tools/call on search_filings, get_filing_sample, purchase_filing |
| A2A (discovery) | Agent Card on Cloud Run upstream (xpay blocks /.well-known/*): https://sec-filings-mcp-1065601264332.us-central1.run.app/.well-known/agent-card.json |
| x402 (payment) | purchase_filing — 402 + Polygon USDC + tx_hash redelivery |
Native A2A JSON-RPC task API is on the roadmap; today agents invoke via MCP Streamable HTTP. Details: docs/A2A.md.
| Path | URL / action |
|---|---|
| Glama sandbox | Open server → Try in Browser |
| Cloud Run trial | https://sec-filings-mcp-1065601264332.us-central1.run.app/mcp — search_filings + get_filing_sample without ?key= |
Details: docs/TRY_WITHOUT_XPAY.md.
xpay proxy always needs a key; per-tool $0 is allowed on xpay (docs) but is not the same as “no signup.”
| Endpoint | URL |
|---|---|
| xpay (billing + catalog) | https://sec-edgar-filings.mcp.xpay.sh/mcp?key=YOUR_XPAY_KEY |
| Cloud Run (upstream) | https://sec-filings-mcp-1065601264332.us-central1.run.app/mcp |
Register / manage on xpay.tools. Slug: sec-edgar-filings.
Publisher checklist (finance collection, awesome list): docs/DISTRIBUTION.md.
git clone https://github.com/stagproject/sec-filings-mcp.git
cd sec-filings-mcp
copy .env.example .env
# Edit .env with Supabase + x402 keys
uv sync
# Run once in Supabase SQL Editor: sql/fi_processed_transactions.sql
uv run python mcp_server_finance.py --sse
# MCP: http://127.0.0.1:8081/mcp (PORT in .env)
Tests:
uv run python test_finance_mcp.py
uv run python test_finance_mcp.py --xpay-only --e2e
gcloud run deploy sec-filings-mcp `
--source . `
--region us-central1 `
--allow-unauthenticated `
--port 8080
Set env vars from .env (not committed). Do not deploy .env.cloudrun.yaml to git.
Listed at glama.ai/mcp/servers/stagproject/sec-filings-mcp — use Try in Browser for a no-key sandbox; production traffic uses xpay or Cloud Run above.
io.github.stagproject/sec-filings-mcp
Publish / update: docs/MCP_REGISTRY.md. Search: https://registry.modelcontextprotocol.io
MIT — see LICENSE.md.
Be the first to review this server!
by Modelcontextprotocol · Developer Tools
Web content fetching and conversion for efficient LLM usage
by Toleno · Developer Tools
Toleno Network MCP Server — Manage your Toleno mining account with Claude AI using natural language.
by mcp-marketplace · Developer Tools
Create, build, and publish Python MCP servers to PyPI — conversationally.