SEC EDGAR
REMOTE · SEC-EDGAR-MCP.ATLASWORD.WORKERS.DEV
Search SEC filings, read 10-K/8-K, query XBRL facts, track Form 4 insider trades.
Available components
Last scanned (4 hours ago)
Scores higher than 53% of remote servers
Reachable. Last reached 5 Nov 2026.
Category Finance and Payments
How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →
Endpoint Security46
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation not fully verified: no authorisation is required to call this server, and 5 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe. See how to fix → View diagnostics → Unverified
- HTTPS enforcement could not be verified: the plaintext port answered with HTTP 405, which proves neither a plaintext path nor enforcement. View diagnostics → Unverified
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability73
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 747 tokens (~149/item across 5 items; 5 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management77
- Stability observed for 23 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage94
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 82% of tool parameters carry a description.Partial
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 5 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 5 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities60
- Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28. See how to fix → Fail
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 5 Nov 26 −3
- Stability: pass → 0.77 functional
- 26 Oct 26 0
- Stability: 0.97 → pass security
- 25 Oct 26 0
- Stability: pass → 0.97 functional
- 17 Oct 26 +53
- Injection markers: unverified → pass ▲ security
- Stability: unverified → pass ▲ security
- Transport: fail → pass ▲ security
- Authorization: Authorisation not fully verified: no authorisation is required to call this server, and 5 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe. security
- MCP protocol: unverified → fail ▼ functional
- Endpoint reachability: not serving MCP → reachable ▲ functional
- Tool coverage: unverified → 100 ▲ functional
- 16 Oct 26 −53
- Endpoint reachability: reachable → not serving MCP ▼ security
- Stability: pass → unverified ▼ security
- Tool safety: pass → unverified ▼ security
- Transport: pass → fail ▼ security
- Authorization: Authorisation not yet verified: we couldn't confirm whether this endpoint requires it. security
- Capabilities: fail → unverified ▼ functional
- Tool coverage: 100 → unverified ▼ functional
- 15 Oct 26 +53
- Injection markers: unverified → pass ▲ security
- Stability: unverified → pass ▲ security
- Transport: fail → pass ▲ security
- Authorization: Authorisation not fully verified: no authorisation is required to call this server, and 5 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe. security
- MCP protocol: unverified → fail ▼ functional
- Endpoint reachability: not serving MCP → reachable ▲ functional
- Tool coverage: unverified → 100 ▲ functional
- 14 Oct 26 −53
- Endpoint reachability: reachable → not serving MCP ▼ security
- Stability: pass → unverified ▼ security
- Tool safety: pass → unverified ▼ security
- Transport: pass → fail ▼ security
- Authorization: Authorisation not yet verified: we couldn't confirm whether this endpoint requires it. security
- Capabilities: fail → unverified ▼ functional
- Tool coverage: 100 → unverified ▼ functional
- 13 Oct 26 +53
- Injection markers: unverified → pass ▲ security
- Stability: unverified → pass ▲ security
- Transport: fail → pass ▲ security
- Authorization: Authorisation not fully verified: no authorisation is required to call this server, and 5 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe. security
- MCP protocol: unverified → fail ▼ functional
- Endpoint reachability: not serving MCP → reachable ▲ functional
- Tool coverage: unverified → 100 ▲ functional
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 5 Nov 2026 · Probed https://sec-edgar-mcp.atlasword.workers.dev/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=atlasword.workers.dev | CN=WE1,O=Google Trust Services,C=US | 6 Oct 2026 | 4 Jan 2027 | ECDSA 256 | ECDSA-SHA256 | 849f7ed9810844780e649475a5b8ff86 |
| SANs: atlasword.workers.dev, *.atlasword.workers.dev | ||||||
| CN=WE1,O=Google Trust Services,C=US (CA) | CN=GTS Root R4,O=Google Trust Services LLC,C=US | 13 Dec 2023 | 20 Feb 2029 | ECDSA 256 | ECDSA-SHA384 | 7ff31977972c224a76155d13b6d685e3 |
| CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) | CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE | 15 Nov 2023 | 28 Jan 2028 | ECDSA 384 | SHA256-RSA | 7fe530bf331343bedd821610493d8a1b |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of sec-edgar-mcp.atlasword.workers.dev. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| dev. | present | 60074 | 8 | Verified |
| workers.dev. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://sec-edgar-mcp.atlasword.workers.dev/mcp | Verified | 200 | |
| http (plaintext) | http://sec-edgar-mcp.atlasword.workers.dev/mcp | Inconclusive | 405 |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
edgar_get_8k ~116
Recent 8-K material event filings for a company, with classified event types ('material_acquisition', 'executive_change', 'auditor_change', 'results_of_operations', etc.). Use this when the user asks 'has anything material happened with <company>'.
| Name | Type | Req | Description |
|---|---|---|---|
| cik | string | – | – |
| limit | integer | – | – |
| since | string | – | Only return 8-Ks filed on or after this ISO date (YYYY-MM-DD). Default = last 90 days. |
| ticker | string | – | – |
No output schema declared.
No examples provided.
edgar_get_company ~79
Company metadata by ticker or CIK: legal name, SIC industry classification, exchanges listed, fiscal year end. Use this when the user wants to know who/what a company is, before drilling into filings.
| Name | Type | Req | Description |
|---|---|---|---|
| ticker_or_cik | string | yes | Either a stock ticker (e.g. 'MSFT') or a CIK number. |
No output schema declared.
No examples provided.
edgar_get_facts ~185
Get XBRL-structured financial facts for a company (revenue, operating income, net income, cash, assets, etc.). Accepts common-name aliases ('revenue', 'eps') OR XBRL concepts ('Revenues', 'EarningsPerShareDiluted'). Returns one row per (fiscal_year, fiscal_period), preferring latest-filed when amendments exist.
| Name | Type | Req | Description |
|---|---|---|---|
| cik | string | – | 10-digit CIK. Provide either ticker OR cik. |
| concept | string | yes | Financial concept. Common aliases: 'revenue', 'operating_income', 'net_income', 'cash', 'total_assets', 'total_liabilities', 'eps', 'eps_basic'. Or pass an XBRL us-gaap concept directly (e.g. 'Revenu… |
| ticker | string | – | Stock ticker, e.g. 'MSFT'. |
No output schema declared.
No examples provided.
edgar_read_filing ~130
Fetch the full text (HTML) of a specific filing by accession number. Useful when the user wants to read the actual content of a 10-K/8-K. Truncates at ~80K characters; use search to narrow first.
| Name | Type | Req | Description |
|---|---|---|---|
| accession_number | string | yes | Accession number, e.g. '0001564590-24-029333'. |
| cik | string | – | 10-digit CIK (zero-padded). Used to construct the document URL. |
| ticker | string | – | Stock ticker (used to resolve the CIK; pass either this or cik). |
No output schema declared.
No examples provided.
edgar_search_filings ~237
Search SEC EDGAR filings for a US-listed company. Returns recent filings (10-K, 10-Q, 8-K, S-1, Form 4, etc.) filtered by ticker or CIK, form type, and date range. Use this when the user asks 'what did <company> file' or needs to find a specific filing.
| Name | Type | Req | Description |
|---|---|---|---|
| cik | string | – | 10-digit CIK number (zero-padded). Provide either ticker OR cik. |
| date_from | string | – | Optional ISO date YYYY-MM-DD; only filings on or after this date. |
| date_to | string | – | Optional ISO date YYYY-MM-DD; only filings on or before this date. |
| form_type | string | – | Optional form type filter, e.g. '10-K', '8-K', '4'. Prefix-matched, so '10-K' matches '10-K' and '10-K/A'. |
| limit | integer | – | Max filings to return (default 25, max 200). |
| ticker | string | – | Stock ticker, e.g. 'MSFT'. Provide either ticker OR cik. |
No output schema declared.
No examples provided.
How do I install the SEC EDGAR MCP server?
SEC EDGAR is a hosted endpoint at https://sec-edgar-mcp.atlasword.workers.dev/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
remote · sec-edgar-mcp.atlasword.workers.dev
claude mcp add --transport http guptaprakhariitr-sec-edgar-mcp 'https://sec-edgar-mcp.atlasword.workers.dev/mcp'
What is the SEC EDGAR MCP server?
SEC EDGAR is an MCP server listed in the public MCP registry as io.github.guptaprakhariitr/sec-edgar-mcp. Search SEC filings, read 10-K/8-K, query XBRL facts, track Form 4 insider trades. This page covers its hosted endpoint (https://sec-edgar-mcp.atlasword.workers.dev/mcp).
Is the SEC EDGAR MCP server safe to use?
SEC EDGAR scores 68 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the SEC EDGAR MCP server expose?
SEC EDGAR exposes 5 tools: edgar_search_filings, edgar_read_filing, edgar_get_facts, edgar_get_8k, edgar_get_company. Their descriptions and schemas cost roughly 747 tokens of context every time the server is loaded.
Does the SEC EDGAR MCP server require authentication?
No. We connected to SEC EDGAR without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the SEC EDGAR MCP server still maintained?
SEC EDGAR is still listed as active in the MCP registry. We last reached this channel on 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.