SEC Filing Proof
REMOTE · SEC-FILING-PROOF.MATTSKOWRONIS.WORKERS.DEV · SCANNED SEP 22
Verify whether an official SEC filing supports a specific financial claim.
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 Security63
- 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 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 Usability75
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 242 tokens (~242/item across 1 items; 1 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 Management100
- No destabilizing schema changes in the last 30 days.Pass
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
- 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 1 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 2 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 Filing Proof MCP server?
SEC Filing Proof is a hosted endpoint at https://sec-filing-proof.mattskowronis.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-filing-proof.mattskowronis.workers.dev
claude mcp add --transport http dev-workers-mattskowronis-sec-filing-proof-verif 'https://sec-filing-proof.mattskowronis.workers.dev/mcp'
{
"mcpServers": {
"dev-workers-mattskowronis-sec-filing-proof-verif": {
"url": "https://sec-filing-proof.mattskowronis.workers.dev/mcp"
}
}
} {
"servers": {
"dev-workers-mattskowronis-sec-filing-proof-verif": {
"type": "http",
"url": "https://sec-filing-proof.mattskowronis.workers.dev/mcp"
}
}
} [mcp_servers.dev-workers-mattskowronis-sec-filing-proof-verif] url = "https://sec-filing-proof.mattskowronis.workers.dev/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"dev-workers-mattskowronis-sec-filing-proof-verif": {
"type": "remote",
"url": "https://sec-filing-proof.mattskowronis.workers.dev/mcp",
"enabled": true
}
}
} openclaw mcp add dev-workers-mattskowronis-sec-filing-proof-verif --url 'https://sec-filing-proof.mattskowronis.workers.dev/mcp' --transport streamable-http
mcp_servers:
dev-workers-mattskowronis-sec-filing-proof-verif:
url: "https://sec-filing-proof.mattskowronis.workers.dev/mcp" {
"McpServers": {
"dev-workers-mattskowronis-sec-filing-proof-verif": {
"Transport": "http",
"Url": "https://sec-filing-proof.mattskowronis.workers.dev/mcp"
}
}
} assistant mcp add dev-workers-mattskowronis-sec-filing-proof-verif -t streamable-http -u 'https://sec-filing-proof.mattskowronis.workers.dev/mcp'
{
"mcpServers": {
"dev-workers-mattskowronis-sec-filing-proof-verif": {
"type": "http",
"url": "https://sec-filing-proof.mattskowronis.workers.dev/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.
- 18 Sept 26 +1
- Stability: 0.97 → pass security
- 16 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 90 to 93. That category is still filling its 30-day observation window: 27 days of observed history at the previous scan, 28 at this one. The score rises as the window fills, whether or not the server changes.
- 14 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 83 to 87. That category is still filling its 30-day observation window: 25 days of observed history at the previous scan, 26 at this one. The score rises as the window fills, whether or not the server changes.
- 12 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 77 to 80. That category is still filling its 30-day observation window: 23 days of observed history at the previous scan, 24 at this one. The score rises as the window fills, whether or not the server changes.
- 9 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 67 to 70. That category is still filling its 30-day observation window: 20 days of observed history at the previous scan, 21 at this one. The score rises as the window fills, whether or not the server changes.
- 7 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 60 to 63. That category is still filling its 30-day observation window: 18 days of observed history at the previous scan, 19 at this one. The score rises as the window fills, whether or not the server changes.
- 5 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 53 to 57. That category is still filling its 30-day observation window: 16 days of observed history at the previous scan, 17 at this one. The score rises as the window fills, whether or not the server changes.
- 3 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 47 to 50. That category is still filling its 30-day observation window: 14 days of observed history at the previous scan, 15 at this one. The score rises as the window fills, whether or not the server changes.
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 22 Sept 2026 · Probed https://sec-filing-proof.mattskowronis.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=mattskowronis.workers.dev | CN=WE1,O=Google Trust Services,C=US | 29 Jul 2026 | 27 Oct 2026 | ECDSA 256 | ECDSA-SHA256 | 44bf413451c6bd740e02ce6e253795fc |
| SANs: mattskowronis.workers.dev, *.mattskowronis.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-filing-proof.mattskowronis.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-filing-proof.mattskowronis.workers.dev/mcp | Verified | 200 | |
| http (plaintext) | http://sec-filing-proof.mattskowronis.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 →
verify_sec_filing_claim Verify SEC Filing Claim ~180
Verify whether a company's official SEC filing supports a specific financial claim. Input ticker or CIK plus claim. Returns filing/XBRL evidence and supported, contradicted, insufficient-evidence, or explicit ambiguity/failure states. Not a market-data feed or investment advice.
| Name | Type | Req | Description |
|---|---|---|---|
| cik | string | – | SEC Central Index Key. Provide ticker or CIK. |
| claim | string | yes | One atomic financial claim to check against official SEC filings. |
| filing_type | string | – | Optional filing hint such as 10-Q or 10-K. |
| fiscal_quarter | string | – | Optional fiscal quarter such as Q1. |
| fiscal_year | integer | – | Optional fiscal year. |
| period | string | – | Optional period hint such as latest quarter or FY2025. |
| ticker | string | – | Issuer ticker symbol. Provide ticker or CIK. |
| Name | Type | Req | Description |
|---|---|---|---|
| cik | string|null | yes | – |
| claim | string | yes | – |
| company | string|null | yes | – |
| evidence | array | yes | – |
| filing_date | string|null | yes | – |
| filing_type | string|null | yes | – |
| period | string|null | yes | – |
| period_end | string|null | yes | – |
| period_start | string|null | yes | – |
| reasoning_summary | string | yes | – |
| retrieved_at | string | yes | – |
| service_version | string | yes | – |
| source_status | string | yes | – |
| source_urls | array | yes | – |
| ticker | string|null | yes | – |
| verdict | string | yes | – |
No examples provided.
What is the SEC Filing Proof MCP server?
SEC Filing Proof is an MCP server listed in the public MCP registry as dev.workers.mattskowronis.sec-filing-proof/verify-sec-filin…. Verify whether an official SEC filing supports a specific financial claim. This page covers its hosted endpoint (https://sec-filing-proof.mattskowronis.workers.dev/mcp).
Is the SEC Filing Proof MCP server safe to use?
SEC Filing Proof scores 81 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 Filing Proof MCP server expose?
SEC Filing Proof exposes 1 tool: verify_sec_filing_claim. Their descriptions and schemas cost roughly 180 tokens of context every time the server is loaded.
Does the SEC Filing Proof MCP server require authentication?
No. We connected to SEC Filing Proof without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the SEC Filing Proof MCP server still maintained?
SEC Filing Proof is still listed as active in the MCP registry. We last reached this channel on 22 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.