# SEC Filing Proof (remote · sec-filing-proof.mattskowronis.workers.dev)

Verify whether an official SEC filing supports a specific financial claim.

- Trust score: 81/100 (high trust)
- Change this week: +2
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-09-22

## Components

- remote · `sec-filing-proof.mattskowronis.workers.dev`: 81/100 (this document), [markdown](https://verifymcp.io/servers/dev-workers-mattskowronis-sec-filing-proof-verify-sec-filing-claim/sec-filing-proof.md), [page](https://verifymcp.io/servers/dev-workers-mattskowronis-sec-filing-proof-verify-sec-filing-claim/sec-filing-proof)

## Channel facts

- Endpoint: `https://sec-filing-proof.mattskowronis.workers.dev/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `1.0.0`

## Trust breakdown

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. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-09-22.

- **Endpoint Security**: 63/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one.
  - HTTPS enforcement could not be verified: the plaintext port answered with HTTP 405, which proves neither a plaintext path nor enforcement.
  - HSTS check failed: the Strict-Transport-Security header is absent.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 75/100
  - AI-judged instruction clarity (excellent).
  - 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.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 100/100
  - No destabilizing schema changes in the last 30 days.
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
  - Structured output schemas are declared (100% of tools); any adoption earns full credit.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 1 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 2 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

## Install

### 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.

### Claude

```bash
claude mcp add --transport http dev-workers-mattskowronis-sec-filing-proof-verif 'https://sec-filing-proof.mattskowronis.workers.dev/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "dev-workers-mattskowronis-sec-filing-proof-verif": {
      "url": "https://sec-filing-proof.mattskowronis.workers.dev/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "dev-workers-mattskowronis-sec-filing-proof-verif": {
      "type": "http",
      "url": "https://sec-filing-proof.mattskowronis.workers.dev/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.dev-workers-mattskowronis-sec-filing-proof-verif]
url = "https://sec-filing-proof.mattskowronis.workers.dev/mcp"
```

### opencode

```json
{
  "$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

```bash
openclaw mcp add dev-workers-mattskowronis-sec-filing-proof-verif --url 'https://sec-filing-proof.mattskowronis.workers.dev/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  dev-workers-mattskowronis-sec-filing-proof-verif:
    url: "https://sec-filing-proof.mattskowronis.workers.dev/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "dev-workers-mattskowronis-sec-filing-proof-verif": {
      "Transport": "http",
      "Url": "https://sec-filing-proof.mattskowronis.workers.dev/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add dev-workers-mattskowronis-sec-filing-proof-verif -t streamable-http -u 'https://sec-filing-proof.mattskowronis.workers.dev/mcp'
```

### Other

```json
{
  "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.

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-09-18 (score 81, +1)

- [security] Stability: 0.97 → pass

### 2026-09-16 (score 80, +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.

### 2026-09-14 (score 79, +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.

### 2026-09-12 (score 78, +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.

### 2026-09-09 (score 77, +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.

### 2026-09-07 (score 76, +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.

### 2026-09-05 (score 75, +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.

### 2026-09-03 (score 74, +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.

## MCP tools (1)

### `verify_sec_filing_claim` (~180 tokens)

Verify SEC Filing Claim

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.

Input parameters:

- `cik` (string): SEC Central Index Key. Provide ticker or CIK.
- `claim` (string, required): 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.

Output parameters:

- `cik` (string|null)
- `claim` (string)
- `company` (string|null)
- `evidence` (array)
- `filing_date` (string|null)
- `filing_type` (string|null)
- `period` (string|null)
- `period_end` (string|null)
- `period_start` (string|null)
- `reasoning_summary` (string)
- `retrieved_at` (string)
- `service_version` (string)
- `source_status` (string)
- `source_urls` (array)
- `ticker` (string|null)
- `verdict` (string)

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/dev-workers-mattskowronis-sec-filing-proof-verify-sec-filing-claim/sec-filing-proof#diagnostics

## Score history

- 2026-09-22: 81
- 2026-09-21: 81
- 2026-09-20: 81
- 2026-09-19: 81
- 2026-09-18: 81
- 2026-09-17: 80
- 2026-09-16: 80
- 2026-09-15: 79
- 2026-09-14: 79
- 2026-09-13: 78
- 2026-09-12: 78
- 2026-09-11: 77
- 2026-09-10: 77
- 2026-09-09: 77
- 2026-09-08: 76
- 2026-09-07: 76
- 2026-09-06: 75
- 2026-09-05: 75
- 2026-09-04: 74
- 2026-09-03: 74
- 2026-09-02: 73
- 2026-09-01: 73
- 2026-08-31: 72
- 2026-08-30: 72
- 2026-08-29: 71
- 2026-08-28: 71
- 2026-08-27: 70
- 2026-08-26: 70
- 2026-08-25: 68
- 2026-08-24: 68

## Common questions

### 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.

## Links

- Remote endpoint: https://sec-filing-proof.mattskowronis.workers.dev/mcp
- Website: https://sec-filing-proof.mattskowronis.workers.dev/
- Changelog RSS feed: https://verifymcp.io/servers/dev-workers-mattskowronis-sec-filing-proof-verify-sec-filing-claim/sec-filing-proof.xml
- Changelog JSON feed: https://verifymcp.io/servers/dev-workers-mattskowronis-sec-filing-proof-verify-sec-filing-claim/sec-filing-proof.json
- HTML version of this page: https://verifymcp.io/servers/dev-workers-mattskowronis-sec-filing-proof-verify-sec-filing-claim/sec-filing-proof