# FiledProof (remote · filedproof.davisvillelabs.com)

Primary-source SEC filing intelligence and financial/disclosure reconciliation for AI agents.

- Trust score: 73/100 (medium)
- Change this week: +3
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-09-27

## Components

- remote · `filedproof.davisvillelabs.com`: 73/100 (this document), [markdown](https://verifymcp.io/servers/com-davisvillelabs-filedproof-filedproof/filedproof.md), [page](https://verifymcp.io/servers/com-davisvillelabs-filedproof-filedproof/filedproof)

## Channel facts

- Endpoint: `https://filedproof.davisvillelabs.com/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `0.9.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-27.

- **Endpoint Security**: 69/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.
  - The HSTS (Strict-Transport-Security) header is present.
  - 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**: 65/100
  - AI-judged instruction clarity (excellent).
  - Context-footprint check failed: tool/resource definitions use about 4068 tokens (~312/item across 13 items; 13 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 40/100
  - Stability observed for 12 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **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 13 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 14 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a current MCP spec version (2026-07-28).

## Install

### How do I install the FiledProof MCP server?

FiledProof is a hosted endpoint at https://filedproof.davisvillelabs.com/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 com-davisvillelabs-filedproof-filedproof 'https://filedproof.davisvillelabs.com/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "com-davisvillelabs-filedproof-filedproof": {
      "url": "https://filedproof.davisvillelabs.com/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "com-davisvillelabs-filedproof-filedproof": {
      "type": "http",
      "url": "https://filedproof.davisvillelabs.com/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.com-davisvillelabs-filedproof-filedproof]
url = "https://filedproof.davisvillelabs.com/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "com-davisvillelabs-filedproof-filedproof": {
      "type": "remote",
      "url": "https://filedproof.davisvillelabs.com/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add com-davisvillelabs-filedproof-filedproof --url 'https://filedproof.davisvillelabs.com/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  com-davisvillelabs-filedproof-filedproof:
    url: "https://filedproof.davisvillelabs.com/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "com-davisvillelabs-filedproof-filedproof": {
      "Transport": "http",
      "Url": "https://filedproof.davisvillelabs.com/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add com-davisvillelabs-filedproof-filedproof -t streamable-http -u 'https://filedproof.davisvillelabs.com/mcp'
```

### Other

```json
{
  "mcpServers": {
    "com-davisvillelabs-filedproof-filedproof": {
      "type": "http",
      "url": "https://filedproof.davisvillelabs.com/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-27 (score 73, +1)

No change was recorded against any check on this day. Stability & Change Management went from 37 to 40. That category is still filling its 30-day observation window: 11 days of observed history at the previous scan, 12 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-09-26 (score 72, 0)

- [security] The server rewrote its instructions, which are the text every model session reads
- [security] Tool “filedproof.check_disclosure_changes” rewrote its description, which is the text the model reads
- [functional] New tool “filedproof.check_material_filing_changes”

### 2026-09-25 (score 72, 0)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-09-23 (score 72, +1)

No change was recorded against any check on this day. Stability & Change Management went from 23 to 27. That category is still filling its 30-day observation window: 7 days of observed history at the previous scan, 8 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-09-21 (score 71, +1)

No change was recorded against any check on this day. Stability & Change Management went from 17 to 20. That category is still filling its 30-day observation window: 5 days of observed history at the previous scan, 6 at this one. The score rises as the window fills, whether or not the server changes.

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

### 2026-09-17 (score 69, +1)

No change was recorded against any check on this day. Stability & Change Management went from 3 to 7. That category is still filling its 30-day observation window: 1 days of observed history at the previous scan, 2 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-09-16 (score 68, 0)

- [security] Tool “filedproof.build_disclosure_lineage” rewrote its description, which is the text the model reads
- [security] Tool “filedproof.build_disclosure_matrix” rewrote its description, which is the text the model reads
- [security] Tool “filedproof.build_evidence_pack” rewrote its description, which is the text the model reads
- [security] Tool “filedproof.build_timeline” rewrote its description, which is the text the model reads
- [security] Tool “filedproof.check_disclosure_changes” rewrote its description, which is the text the model reads
- [security] Tool “filedproof.compare_filings” rewrote its description, which is the text the model reads
- [security] Tool “filedproof.list_filings” rewrote its description, which is the text the model reads
- [security] Tool “filedproof.preflight_financial_fact” rewrote its description, which is the text the model reads
- [security] Tool “filedproof.reconcile_financial_fact” rewrote its description, which is the text the model reads
- [security] Tool “filedproof.resolve_issuer” rewrote its description, which is the text the model reads
- [security] Tool “filedproof.search_evidence” rewrote its description, which is the text the model reads
- [security] Tool “filedproof.verify_claim” rewrote its description, which is the text the model reads
- [functional regression] Schema quality: 218 → 260
- [functional improvement] Stability: unverified → 0.03

## MCP tools (13)

### `filedproof.resolve_issuer` (~96 tokens)

Resolve public company issuer

Resolve a ticker, CIK, or exact company name to one SEC issuer. Use this first when issuer identity is uncertain or before passing a CIK or accession into another FiledProof tool. Do not use it to list filings or search disclosure text; use filedproof.list_filings or filedproof.search_evidence after identity is resolved.

Input parameters:

- `identifier` (string, required): Ticker, CIK, or exact SEC company name.

### `filedproof.list_filings` (~159 tokens)

List SEC filings

List recent or bounded historical SEC filings with canonical source metadata and explicit coverage limits. Use this when you need form, filing-date, or accession inventory, when choosing an exact pair for filedproof.compare_filings, or when confirming coverage before filedproof.check_disclosure_changes. For passage-level research, use filedproof.search_evidence instead.

Input parameters:

- `forms` (array): SEC filing form types to include, such as 10-K, 10-Q, or 8-K.
- `history` (boolean): Whether to use bounded historical SEC submission archives when needed.
- `identifier` (string, required): Ticker, CIK, or exact SEC company name.
- `limit` (integer): Maximum number of operation-specific evidence or result records to return.

### `filedproof.search_evidence` (~230 tokens)

Search filing evidence

Find relevant primary-source passages across a bounded set of SEC filings. Use this for open-ended filing research when you want evidence records with provenance but do not need a claim verdict or a curated answer bundle. Use filedproof.verify_claim for one explicit factual proposition, filedproof.build_evidence_pack for a compact answer-ready bundle, or filedproof.build_timeline when chronology is the main objective. Relevance is not a truth verdict.

Input parameters:

- `filings` (integer): Maximum number of filings to inspect for this invocation.
- `forms` (array): SEC forms to search. Defaults to 10-K and 10-Q.
- `history` (boolean): Whether to use bounded historical SEC submission archives when needed.
- `identifier` (string, required): Ticker, CIK, or exact SEC company name.
- `item` (string): Optional SEC filing item, such as 1A or 7.
- `limit` (integer): Maximum number of operation-specific evidence or result records to return.
- `q` (string, required): Research question or disclosure topic.
- `section` (string): Optional exact normalized section heading.

### `filedproof.build_evidence_pack` (~234 tokens)

Build answer-ready evidence pack

Package the strongest relevant SEC evidence for an upstream AI agent, preserving source URLs, locators, search scope, coverage, and explicit non-inference rules. Use this when the research question is already known and the caller wants a compact evidence bundle ready for downstream reasoning. Use filedproof.search_evidence for broader retrieval, filedproof.verify_claim for an explicit support-or-contradiction verdict, or filedproof.build_timeline for chronological organization.

Input parameters:

- `filings` (integer): Maximum number of filings to inspect for this invocation.
- `forms` (array): SEC forms to search. Defaults to 10-K and 10-Q.
- `history` (boolean): Whether to use bounded historical SEC submission archives when needed.
- `identifier` (string, required): Ticker, CIK, or exact SEC company name.
- `item` (string): Optional SEC filing item, such as 1A or 7.
- `limit` (integer): Maximum number of operation-specific evidence or result records to return.
- `q` (string, required): Research question or disclosure topic.
- `section` (string): Optional exact normalized section heading.

### `filedproof.build_timeline` (~231 tokens)

Build disclosure evidence timeline

Organize topic-relevant filing evidence chronologically across a bounded set of SEC filings. Use this when sequence over time is the primary need. Use filedproof.build_disclosure_lineage when you need persisted same-form evolution and reusable transition state, filedproof.compare_filings for exactly two known accessions, or filedproof.check_disclosure_changes for prioritized monitoring of newly filed changes. The timeline does not invent semantic change or materiality.

Input parameters:

- `filings` (integer): Maximum number of filings to inspect for this invocation.
- `forms` (array): SEC forms to search. Defaults to 10-K and 10-Q.
- `history` (boolean): Whether to use bounded historical SEC submission archives when needed.
- `identifier` (string, required): Ticker, CIK, or exact SEC company name.
- `item` (string): Optional SEC filing item, such as 1A or 7.
- `limit` (integer): Maximum number of operation-specific evidence or result records to return.
- `q` (string, required): Research question or disclosure topic.
- `section` (string): Optional exact normalized section heading.

### `filedproof.verify_claim` (~256 tokens)

Verify a claim against SEC filings

Conservatively assess one explicit factual claim against official SEC filing evidence and return support, contradiction, mixed, partial, or insufficient-evidence stance signals. Use this when the caller already has a proposition to test. Use filedproof.search_evidence for open-ended research, filedproof.reconcile_financial_fact for one supported standalone-quarter revenue, net-income, or operating-cash-flow value, or filedproof.check_disclosure_changes for new disclosure-change monitoring. A filing establishes what the company reported, not independent real-world truth.

Input parameters:

- `claim` (string, required): The factual claim to assess against the company's SEC filings.
- `filings` (integer): Maximum number of filings to inspect for this invocation.
- `forms` (array): SEC forms to search. Defaults to 10-K, 10-Q, and 8-K.
- `history` (boolean): Whether to use bounded historical SEC submission archives when needed.
- `identifier` (string, required): Ticker, CIK, or exact SEC company name.
- `item` (string): Optional SEC filing item such as 1A or 7.
- `limit` (integer): Maximum number of operation-specific evidence or result records to return.
- `section` (string): Optional exact normalized section heading.

### `filedproof.build_disclosure_lineage` (~312 tokens)

Build historical disclosure lineage

Build or reuse a persisted disclosure history for one issuer and topic, with deterministic per-filing fingerprints and same-form transition edges backed by exact SEC evidence. Use this when historical evolution or repeat reuse matters. Use filedproof.compare_filings for a one-off exact filing pair, filedproof.build_timeline for simple chronology without reusable transition state, or filedproof.build_disclosure_matrix when the objective is comparison across multiple companies. Structural change is not a materiality judgment.

Input parameters:

- `comparisonLimit` (integer): Maximum changed blocks inspected in each same-form structural comparison.
- `filings` (integer): Maximum filings to inspect in this invocation. Previously persisted lineage can contain more accumulated history.
- `fingerprintLimit` (integer): Maximum relevant evidence records used to fingerprint one filing.
- `forms` (array): SEC forms to include. Defaults to 10-K and 10-Q. Same-form transitions are linked independently.
- `history` (boolean): Use bounded historical SEC submission archives when the durable catalog does not already provide enough history.
- `identifier` (string, required): Ticker, CIK, or exact SEC company name.
- `item` (string): Optional SEC filing item such as 1A or 7.
- `limit` (integer): Maximum topic-relevant change evidence records retained per transition.
- `section` (string): Optional exact normalized section heading.
- `topic` (string, required): Public-company disclosure topic whose filing-to-filing history should be accumulated, such as AI regulation, cybersecurity, or supply-chain concentration.

### `filedproof.build_disclosure_matrix` (~377 tokens)

Build cross-company disclosure matrix

Align one disclosure topic across two to six public companies using each company's source-backed historical disclosure lineage. Use this when cross-company comparison is the objective and the caller needs current evidence plus latest same-form transition evidence on a common basis without independently retrieving, parsing, aligning, and re-comparing every filing history. Use filedproof.build_disclosure_lineage for one issuer, not this tool; use filedproof.check_disclosure_changes when monitoring newly filed changes for one issuer. The matrix is an evidence substrate, not a ranking or materiality judgment.

Input parameters:

- `comparisonLimit` (integer): Maximum number of changed blocks to inspect in each filing comparison.
- `currentEvidenceLimit` (integer): Maximum current-filing evidence records returned per company and form.
- `filings` (integer): Maximum filings per company used to build or reuse the underlying disclosure lineage.
- `fingerprintLimit` (integer): Maximum number of relevant evidence records used to fingerprint one filing.
- `forms` (array): SEC forms to align. Defaults to 10-K for stronger cross-company comparability.
- `history` (boolean): Whether to use bounded historical SEC submission archives when needed.
- `identifiers` (array, required): Two to six public-company identifiers to align on the same filing-grounded disclosure topic.
- `item` (string): Optional SEC filing item such as 1A or 7.
- `limit` (integer): Maximum topic-relevant change evidence retained in each underlying lineage transition.
- `maxArchiveFiles` (integer): Maximum number of historical SEC submission archive files to inspect when history is enabled.
- `section` (string): Optional exact normalized section heading.
- `topic` (string, required): Disclosure topic to align across companies, such as cybersecurity, AI infrastructure, or supply-chain concentration.
- `transitionEvidenceLimit` (integer): Maximum evidence records returned for each latest same-form transition.

### `filedproof.check_material_filing_changes` (~281 tokens)

Check meaningful changes between SEC filings

Configured 0.10 USD fast specialist operation when runtime commerce is active. Compare two same-form 10-K or 10-Q filings and return source-grounded meaningful changes, explainable decision-relevance triage, low-signal/no-change sections, confidence, limitations, and routing guidance when deeper disclosure verification is warranted. Supply both accessions for an exact pair, or omit both and choose form so FiledProof deterministically selects the latest comparable pair. This is not a legal materiality or investment-significance determination.

Input parameters:

- `earlierAccession` (string): Optional earlier SEC accession. Supply together with laterAccession for an exact pair.
- `focus` (string): Optional bounded decision-relevance focus. Defaults to all maintained change categories.
- `form` (string): Comparable SEC form. Defaults to 10-K and must match both explicit filings when accessions are supplied.
- `history` (boolean): Allow bounded historical SEC submission lookup when automatic pair resolution needs it.
- `identifier` (string, required): Ticker, CIK, or exact SEC company name.
- `item` (string): Optional SEC filing item such as 1A or 7.
- `laterAccession` (string): Optional later SEC accession. Supply together with earlierAccession for an exact pair.
- `limit` (integer): Maximum meaningful change objects to return.

Output parameters:

- `changes` (array)
- `confidence` (object)
- `earlierFiling` (object)
- `evidence` (array)
- `issuer` (object)
- `laterFiling` (object)
- `limitations` (array)
- `lowSignalChanges` (array)
- `operation`
- `recommendedNextStep`
- `schemaVersion`
- `sources` (array)
- `summary` (object)
- `unchangedOrLowSignalSections` (array)

### `filedproof.check_disclosure_changes` (~455 tokens)

Prioritize new SEC disclosure changes

Configured 1.00 USD specialist operation when runtime commerce is active. Use this for one issuer when the caller needs changes in newly filed disclosures prioritized against the prior filing of the same form, with compact before/after evidence from SEC filings and retry-safe checkpoint state. Supply a freeform topic, or profile=financial_risk for the bounded liquidity, debt, dilution/equity-issuance, and changed-risk report. The report separates documented filing changes from deterministic category/attention interpretation. Use filedproof.check_material_filing_changes for a fast low-cost same-form 10-K or 10-Q comparison, filedproof.compare_filings for a free raw structural diff between known accessions, or filedproof.list_filings first when coverage is uncertain. Attention is not a legal, accounting, economic, or investment materiality judgment, and pre-payment validation rejects invalid or non-comparable work before a charge.

Input parameters:

- `comparisonLimit` (integer): Maximum number of changed blocks to inspect in each filing comparison.
- `forms` (array): SEC forms to monitor. Defaults to 10-K and 10-Q.
- `history` (boolean): Whether to use bounded historical SEC submission archives when needed.
- `identifier` (string, required): Ticker, CIK, or exact SEC company name.
- `item` (string): Optional SEC filing item such as 1A or 7.
- `limit` (integer): Maximum topic-relevant change evidence records per filing comparison.
- `maxArchiveFiles` (integer): Maximum historical SEC submission archive files to inspect when history is enabled.
- `maxNewFilings` (integer): Maximum newly detected filings to process in one check.
- `profile` (string): Bounded report profile. financial_risk checks liquidity/capital resources, debt/borrowings/covenants/maturities, dilution/equity-issuance disclosures, and changed risk disclosures together. Provide p…
- `sinceAccession` (string): Checkpoint accession returned by the previous paid check. Omit for the first snapshot.
- `topic` (string): Disclosure topic to monitor, such as AI capital spending, China risk, or cybersecurity. Provide topic or profile, not both.

Output parameters:

- `agentGuidance` (object)
- `attentionCounts` (object)
- `changeCount` (integer)
- `changeDetected` (boolean)
- `checkpoint`
- `events` (array)
- `forms` (array)
- `haltedOnFailure` (boolean)
- `highPriorityChangeCount` (integer)
- `issuer` (object)
- `latestAvailable`
- `limitations` (array)
- `mode` (string)
- `newFilingsDetected` (integer)
- `overallAttention` (string)
- `priorCheckpoint`
- `purpose` (string)
- `remainingNewFilings` (integer)
- `reportProfile` (string|null)
- `schemaVersion`
- `scope` (object)
- `status` (string)
- `topic` (string)
- `truncated` (boolean)

### `filedproof.compare_filings` (~184 tokens)

Compare two SEC filings

Compare two known filings from the same issuer and return source-backed added and removed disclosure blocks. Use this low-level operation when you already know the exact left and right accessions and only need a structural diff. Use filedproof.build_disclosure_lineage for multi-filing historical evolution, filedproof.build_timeline for topical chronology, or filedproof.check_disclosure_changes when you need prioritized new-change triage and recurring checkpoint semantics. Structural change is not semantic interpretation or a materiality judgment.

Input parameters:

- `identifier` (string, required): Ticker, CIK, or exact SEC company name.
- `item` (string): Optional filing item such as 1A or 7.
- `left` (string, required): Left SEC accession number.
- `limit` (integer): Maximum number of operation-specific evidence or result records to return.
- `right` (string, required): Right SEC accession number.

### `filedproof.preflight_financial_fact` (~471 tokens)

Check financial fact applicability

Free eligibility check for filedproof.reconcile_financial_fact. Use this before the $1 specialist operation when issuer identity, filing selection, supported metric, fiscal-period dates, annual-versus-quarter context, required SEC Company Facts contexts, or an optional SEC-filed 8-K earnings-release number comparison may be uncertain. It validates applicability without revealing the filing value, comparison source value, later revision values, evidence, or arithmetic. For general filing lookup or narrative research, use filedproof.resolve_issuer, filedproof.list_filings, or filedproof.search_evidence instead.

Input parameters:

- `anchor_accession` (string): Optional 10-Q/10-K accession, including amendments. If omitted, FiledProof selects the earliest compatible filing for the requested period.
- `as_of_date` (string): Optional historical cutoff. The selected anchor filing must have been filed on or before this date; later values never replace the primary answer.
- `cik` (string): Legacy/direct SEC CIK input. Prefer identifier when starting from a ticker or company name.
- `comparison_accession` (string): Optional SEC 8-K/8-K/A accession containing an earnings-release exhibit to compare with the filing-anchored GAAP fact. Provide comparison_value with it.
- `comparison_exhibit` (string): Optional exact EX-99 exhibit filename or safe relative path when an 8-K contains multiple candidate earnings-release exhibits.
- `comparison_value` (string): Actual-unit integer value claimed from the SEC-filed earnings-release exhibit. FiledProof must find this value in metric context before the comparison is eligible.
- `identifier` (string): Issuer ticker, exact company name, CIK, or CIK-prefixed identifier. FiledProof resolves this to the durable SEC CIK before research and payment.
- `include_subsequent_revisions` (boolean): When true, report later different values for the same SEC concept, unit, and period separately from the primary anchored value.
- `metric` (string, required): Financial metric to reconcile: revenue, net income, or operating cash flow.
- `period_end` (string, required): Requested fiscal-period end date.
- `period_start` (string, required): Requested fiscal-period start date.
- `period_type` (string): Whether the requested value is one standalone fiscal quarter or the full fiscal year.

Output parameters:

- `canonicalRequest` (object)
- `checks` (object)
- `disclosureBoundary` (string)
- `eligible` (boolean)
- `operation`
- `paymentMethods` (array)
- `price` (object)
- `reason` (string)
- `schemaVersion`
- `status` (string)

### `filedproof.reconcile_financial_fact` (~492 tokens)

Reconcile one SEC financial fact

$1.00 USD specialist operation when commerce is active. Use this for one supported quarterly or fiscal-year revenue, net income, or operating cash flow fact. Optionally provide comparison_accession plus comparison_value to verify that number against an SEC-filed 8-K earnings-release exhibit and assess GAAP/non-GAAP, period, currency, and scope comparability. Arithmetic bridges are returned only when visible source rows reproduce exactly; otherwise the reason remains unresolved. Use filedproof.preflight_financial_fact first when eligibility is uncertain, filedproof.verify_claim for a narrative factual proposition, or filedproof.search_evidence for general filing research. Unsupported or ambiguous requests abstain before payment.

Input parameters:

- `anchor_accession` (string): Optional 10-Q/10-K accession, including amendments. If omitted, FiledProof selects the earliest compatible filing for the requested period.
- `as_of_date` (string): Optional historical cutoff. The selected anchor filing must have been filed on or before this date; later values never replace the primary answer.
- `cik` (string): Legacy/direct SEC CIK input. Prefer identifier when starting from a ticker or company name.
- `comparison_accession` (string): Optional SEC 8-K/8-K/A accession containing an earnings-release exhibit to compare with the filing-anchored GAAP fact. Provide comparison_value with it.
- `comparison_exhibit` (string): Optional exact EX-99 exhibit filename or safe relative path when an 8-K contains multiple candidate earnings-release exhibits.
- `comparison_value` (string): Actual-unit integer value claimed from the SEC-filed earnings-release exhibit. FiledProof must find this value in metric context before the comparison is eligible.
- `identifier` (string): Issuer ticker, exact company name, CIK, or CIK-prefixed identifier. FiledProof resolves this to the durable SEC CIK before research and payment.
- `include_subsequent_revisions` (boolean): When true, report later different values for the same SEC concept, unit, and period separately from the primary anchored value.
- `metric` (string, required): Financial metric to reconcile: revenue, net income, or operating cash flow.
- `period_end` (string, required): Requested fiscal-period end date.
- `period_start` (string, required): Requested fiscal-period start date.
- `period_type` (string): Whether the requested value is one standalone fiscal quarter or the full fiscal year.

Output parameters:

- `anchorFiling` (object)
- `asOf` (object)
- `canonicalRequest` (object)
- `currency` (string|null)
- `derivation` (object|null)
- `evidence` (array)
- `issuer` (object)
- `limitations` (array)
- `numberReconciliation` (object|null)
- `operation`
- `originalReported` (object|null)
- `period` (object)
- `resolvedMetric` (object)
- `resultBasis` (string|null)
- `resultId` (string)
- `revisionAssessment` (object)
- `scale` (integer|null)
- `schemaVersion`
- `scope` (object)
- `source` (object)
- `status`
- `subsequentReportedValues` (array)
- `units` (string|null)
- `unresolvedQuestions` (array)
- `validation` (object)
- `value` (string|null)

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/com-davisvillelabs-filedproof-filedproof/filedproof#diagnostics

## Score history

- 2026-09-27: 73
- 2026-09-26: 72
- 2026-09-25: 72
- 2026-09-24: 72
- 2026-09-23: 72
- 2026-09-22: 71
- 2026-09-21: 71
- 2026-09-20: 70
- 2026-09-19: 70
- 2026-09-18: 69
- 2026-09-17: 69
- 2026-09-16: 68
- 2026-09-15: 68

## Common questions

### What is the FiledProof MCP server?

FiledProof is an MCP server listed in the public MCP registry as com.davisvillelabs.filedproof/filedproof. Primary-source SEC filing intelligence and financial/disclosure reconciliation for AI agents. This page covers its hosted endpoint (https://filedproof.davisvillelabs.com/mcp).

### Is the FiledProof MCP server safe to use?

FiledProof 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 FiledProof MCP server expose?

FiledProof exposes 13 tools: filedproof.resolve_issuer, filedproof.list_filings, filedproof.search_evidence, filedproof.build_evidence_pack, filedproof.build_timeline, and 8 more. Their descriptions and schemas cost roughly 3,778 tokens of context every time the server is loaded.

### Does the FiledProof MCP server require authentication?

No. We connected to FiledProof without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

### Is the FiledProof MCP server still maintained?

FiledProof is still listed as active in the MCP registry. We last reached this channel on 27 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://filedproof.davisvillelabs.com/mcp
- Website: https://filedproof.davisvillelabs.com/
- Changelog RSS feed: https://verifymcp.io/servers/com-davisvillelabs-filedproof-filedproof/filedproof.xml
- Changelog JSON feed: https://verifymcp.io/servers/com-davisvillelabs-filedproof-filedproof/filedproof.json
- HTML version of this page: https://verifymcp.io/servers/com-davisvillelabs-filedproof-filedproof/filedproof