SEC Filings
REMOTE · FILINGS.TOOLS · SCANNED OCT 7
Read SEC filings, reported financial facts and sampled filing comparisons with original sources.
Available components
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 Security80
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one. See how to fix → View diagnostics → Partial
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
- 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 Usability71
- AI-judged instruction clarity (good).Pass
- Tool/resource definitions use about 424 tokens (~106/item across 4 items; 4 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management13
- Stability observed for 4 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage75
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 11% of tool parameters carry a description.Partial
- Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 4 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
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
How do I install the SEC Filings MCP server?
SEC Filings is a hosted endpoint at https://filings.tools/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 · filings.tools
claude mcp add --transport http tools-filings-sec-filings 'https://filings.tools/mcp'
{
"mcpServers": {
"tools-filings-sec-filings": {
"url": "https://filings.tools/mcp"
}
}
} {
"servers": {
"tools-filings-sec-filings": {
"type": "http",
"url": "https://filings.tools/mcp"
}
}
} [mcp_servers.tools-filings-sec-filings] url = "https://filings.tools/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"tools-filings-sec-filings": {
"type": "remote",
"url": "https://filings.tools/mcp",
"enabled": true
}
}
} openclaw mcp add tools-filings-sec-filings --url 'https://filings.tools/mcp' --transport streamable-http
mcp_servers:
tools-filings-sec-filings:
url: "https://filings.tools/mcp" {
"McpServers": {
"tools-filings-sec-filings": {
"Transport": "http",
"Url": "https://filings.tools/mcp"
}
}
} assistant mcp add tools-filings-sec-filings -t streamable-http -u 'https://filings.tools/mcp'
{
"mcpServers": {
"tools-filings-sec-filings": {
"type": "http",
"url": "https://filings.tools/mcp"
}
}
} The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.
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.
- 7 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 10 to 13. That category is still filling its 30-day observation window: 3 days of observed history at the previous scan, 4 at this one. The score rises as the window fills, whether or not the server changes.
- 6 Oct 26 +1
- The server rewrote its instructions, which are the text every model session reads security
- Tool “list_filings” rewrote its description, which is the text the model reads security
- Schema quality: 92 → 106 ▼ functional
- Tool coverage: 0% → 11% ▲ functional
- “list_filings” reworded the description of “ticker” cosmetic
- 4 Oct 26 +1
- Stability: unverified → 0.03 ▲ functional
- 3 Oct 26 70
First indexed and scored.
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 8 Oct 2026 · Probed https://filings.tools/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=*.filings.tools | CN=YR2,O=Let's Encrypt,C=US | 20 Sept 2026 | 19 Dec 2026 | RSA 2048 | SHA256-RSA | 6ef3d5424ac84d605d741c78963e02a0f8f |
| SANs: *.filings.tools, filings.tools | ||||||
| CN=YR2,O=Let's Encrypt,C=US (CA) | CN=Root YR,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | RSA 2048 | SHA256-RSA | 4ebd24947e24d394802d84a52fd5b319 |
| CN=Root YR,O=ISRG,C=US (CA) | CN=ISRG Root X1,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | RSA 4096 | SHA256-RSA | f24b6d17f9d9ad7cb1c9fea78782699f |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of filings.tools. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| tools. | present | 13831 | 8 | Verified |
| filings.tools. | 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 |
| Header | Value |
|---|---|
| strict-transport-security | max-age=63072000 |
| content-security-policy | default-src 'self'; script-src 'self' 'unsafe-inline' https://www.googletagmanager.com https://www.googleadservices.com https://www.google.com; style-src 'self' 'unsafe-inline'; img-src 'self' data: https:; font-src 'self'; connect-src 'self' https://www.googletagmanager.com https://www.googleadservices.com https://googleads.g.doubleclick.net https://ad.doubleclick.net https://pagead2.googlesyndication.com https://www.google.com; frame-src 'self' https://www.googletagmanager.com; object-src 'none'; base-uri 'self'; form-action 'self' https://checkout.stripe.com https://billing.stripe.com; frame-ancestors 'none' |
| x-content-type-options | nosniff |
| x-frame-options | DENY |
| referrer-policy | strict-origin-when-cross-origin |
| permissions-policy | camera=(), microphone=(), geolocation=() |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://filings.tools/mcp | Verified | 200 | |
| http (plaintext) | http://filings.tools/mcp | HTTPS enforced | 308 | https://filings.tools/mcp |
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 →
compare_filing Compare with the preceding filing ~95
Use when someone asks what changed between a filing and the one before it, such as this year's 10-K against last year's. Compares the filing with the preceding available reporting period of the same company and form. Returns full sentence-change counts and bounded examples for up to eight sections, and reports when no prior filing is available. It is a sampled comparison, not a complete redline.
| Name | Type | Req | Description |
|---|---|---|---|
| filing_id | string | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| api_url | string | – | – |
| company | string | – | – |
| comparable | boolean | – | – |
| counting | string | – | – |
| current | object | – | – |
| diffRulesVersion | string | – | – |
| docs_url | string | yes | – |
| error | string | – | – |
| form | string | – | – |
| furniture | object | – | – |
| http_status | integer | – | – |
| id | string | – | – |
| message | string | – | – |
| prior | object | – | – |
| reason | string | – | – |
| reportDate | string | – | – |
| retry_after | string | – | – |
| samples_only | boolean | – | – |
| sections | array | – | – |
| status | string | yes | – |
| ticker | string | – | – |
| total_sections | integer | – | – |
| totals | object | – | – |
| usage | object | – | – |
No examples provided.
filing_facts Read reported financial facts ~94
Use when someone asks for the reported numbers in one filing, such as revenue, net income or total assets. Returns XBRL facts tagged to that filing's accession, for the API's ten supported concepts: up to 200 reported values with units and periods. It does not return all periods for a company and it does not give investment advice.
| Name | Type | Req | Description |
|---|---|---|---|
| filing_id | string | yes | – |
| limit | integer | – | – |
| Name | Type | Req | Description |
|---|---|---|---|
| api_url | string | – | – |
| company | object | – | – |
| docs_url | string | yes | – |
| error | string | – | – |
| facts | array | – | – |
| filing | object | – | – |
| http_status | integer | – | – |
| message | string | – | – |
| retry_after | string | – | – |
| status | string | yes | – |
| total_facts | integer | – | – |
| truncated | boolean | – | – |
| usage | object | – | – |
No examples provided.
list_filings Find filings by ticker ~126
Use when someone asks for a company's recent SEC filings, such as its latest 10-K, 10-Q or 8-K, by ticker or CIK. Works for any company in the SEC's ticker list. Returns up to 20 filings from the company's recent EDGAR window, each with a filing id, form type, dates, accession number and original SEC link.
| Name | Type | Req | Description |
|---|---|---|---|
| form | string | – | – |
| limit | integer | – | – |
| ticker | string | yes | A ticker in EDGAR spelling (BRK-B), or a CIK such as 320193. |
| Name | Type | Req | Description |
|---|---|---|---|
| api_url | string | – | – |
| company | object | – | – |
| docs_url | string | yes | – |
| error | string | – | – |
| filings | array | – | – |
| http_status | integer | – | – |
| message | string | – | – |
| retry_after | string | – | – |
| status | string | yes | – |
| usage | object | – | – |
No examples provided.
read_filing_section Read a filing section ~116
Use when someone asks what a filing says in one section, such as risk factors or the business description, or wants the list of sections in a filing. The filing id is one that list_filings returns. Without a section it returns the section index with no text. With a section it returns the text, at most 20,000 characters, with the original length and a flag that marks a cut.
| Name | Type | Req | Description |
|---|---|---|---|
| filing_id | string | yes | – |
| max_characters | integer | – | – |
| section | string | – | – |
| Name | Type | Req | Description |
|---|---|---|---|
| api_url | string | – | – |
| docs_url | string | yes | – |
| error | string | – | – |
| http_status | integer | – | – |
| id | string | – | – |
| index_only | boolean | – | – |
| message | string | – | – |
| meta | object | – | – |
| parserVersion | string | – | – |
| product | string | – | – |
| retry_after | string | – | – |
| section_found | boolean | – | – |
| sections | array | – | – |
| sections_truncated | boolean | – | – |
| sourceUrl | string | – | – |
| status | string | yes | – |
| title | string | – | – |
| topics | array | – | – |
| usage | object | – | – |
No examples provided.
What is the SEC Filings MCP server?
SEC Filings is an MCP server listed in the public MCP registry as tools.filings/sec-filings. Read SEC filings, reported financial facts and sampled filing comparisons with original sources. This page covers its hosted endpoint (https://filings.tools/mcp).
Is the SEC Filings MCP server safe to use?
SEC Filings scores 73 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 Filings MCP server expose?
SEC Filings exposes 4 tools: list_filings, read_filing_section, filing_facts, compare_filing. Their descriptions and schemas cost roughly 431 tokens of context every time the server is loaded.
Does the SEC Filings MCP server require authentication?
No. We connected to SEC Filings without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the SEC Filings MCP server still maintained?
SEC Filings is still listed as active in the MCP registry. We last reached this channel on 7 October 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.