mcpbeat Sign in

SEC API MCP Server

answering

SEC API is answering right now. Last checked 9 min ago.

SEC EDGAR filings, XBRL financials, Form 4 insider trades and 13F holdings with source URLs.

Uptime history 18 hours of history
18 hours agonow
100.0%
Uptime 24h
66 of 66 checks
—
Tools
hidden behind auth
308 ms
Response time
average over 24h
OAuth sign-in
Access
streamable-http

Nothing serious here today

Today is the operative word: we check SEC API every 15 minutes and re-read its code on every release. Watch it and you find out the day that stops being true.

Three servers free · no card

Connect this server

Endpoint below is the one we actually reach during checks — not the one copied from a README. Last verified 9 min ago.

run in your terminal
claude mcp add server --transport http https://sec-api.dev/api/mcp
Settings → Connectors → Add custom connector, then paste this address
https://sec-api.dev/api/mcp
~/.codex/config.toml
[mcp_servers.server]
url = "https://sec-api.dev/api/mcp"
.cursor/mcp.json
{
  "mcpServers": {
    "server": {
      "url": "https://sec-api.dev/api/mcp"
    }
  }
}
.vscode/mcp.json
{
  "servers": {
    "server": {
      "type": "http",
      "url": "https://sec-api.dev/api/mcp"
    }
  }
}

This endpoint answered with an authorization challenge. The server is running, and it signs you in through your browser: there is no API key to paste.

Endpoints

URLTransportStateLatencyChecked
https://sec-api.dev/api/mcp streamable-http sign-in 265 ms 9 min ago

Alternatives to SEC API

same job, measured the same way
SEC EDGAR Insider Trades & Financials
by monriah-studio

SEC EDGAR for agents: Form 4 insider trades, cluster buys, filings, XBRL financials and search.

7 tools answering
Filingrail MCP
by adamhudson777

SEC EDGAR financials, insider trades, 8-K events, and 13F holdings as MCP tools.

166 installs/wk local only
Filings Intel MCP
by datakoot

SEC EDGAR for AI agents: company filings, financials and insider trades. No API keys.

5 tools answering
Beefi
by beefi

US public company data from SEC EDGAR: financials, insider trades, 13F holdings, filings and macro.

answering
Utensil Desk
by utensildesk

SEC filings, financial facts, insider trades and 13F holdings, each value naming its filing.

answering
EDGAR (SEC filings)
by mcpwright

SEC filings in your agent: issuers, Reg CF/D/A raises, XBRL financials, insider trades.

203 installs/wk local only
SecFeed: SEC EDGAR filings
by secfeedapi

SEC EDGAR data as tools: filing search, full text, XBRL financials, insider trades, 13F, 8-K events.

40 tools answering
EDGAR Answers
by aion-autonomous-org

Normalized SEC EDGAR data for AI agents: XBRL financials, 10-K risk diffs, Form 4 insider trades.

answering

SEC API — questions

Answers built from our own checks of this server.

Why is there no tool list for SEC API?
The server answered our handshake with an authorization challenge, so it is running — but it will not describe its tools to an anonymous client. To see them you need to connect with your own credentials. We record it as alive, not as broken: 100.0% of checks in the last 24 hours got a reply.
Is SEC API working right now?
We send a real MCP handshake every 15 minutes. Over the last 24 hours 66 of 66 checks got a reply (100.0%), average response time 308 ms. The bar chart above shows every period we have measured.
How do I connect SEC API?
Copy the ready config from this page. We generate it for Claude Code, Claude Desktop, Codex, Cursor and VS Code, each in the form that client actually reads. It is a remote server, so there is nothing to install — the client connects to the address. You sign in through your browser once and the client keeps the session: no key to copy, and it refuses anonymous clients.
How do you sign in to SEC API?
No API key is involved. SEC API answers our knock with an OAuth challenge, so you authorise it once in your browser and the client keeps the session. That is also why we see no tool list: it will not describe itself to an anonymous client, and that is the server working as intended, not a fault.
How fast is SEC API?
It answers our handshake in 308 ms on average, which is faster than 45% of all working MCP servers we measure. The comparison comes from our own checks across the whole registry, every 15 minutes.