mcpbeat Sign in

FiledProof MCP Server

by davisvillelabs-filedproof Your server? Claim it
answering

FiledProof is answering right now. Last checked 6 min ago. It exposes 12 tools.

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

Uptime history 66 hours of history
66 hours agonow
100.0%
Uptime 24h
92 of 92 checks
12
Tools
read from the server
565 ms
Response time
average over 24h
open, no key
Access
streamable-http

Nothing serious here today

Today is the operative word: we check FiledProof every 15 minutes and re-read its code on every release. Watch it and you find out the day that stops being true.

Three servers free · no card

Connect this server

Endpoint below is the one we actually reach during checks — not the one copied from a README. Last verified 6 min ago.

run in your terminal
claude mcp add filedproof --transport http https://filedproof.davisvillelabs.com/mcp
~/Library/Application Support/Claude/claude_desktop_config.json
{
  "mcpServers": {
    "filedproof": {
      "url": "https://filedproof.davisvillelabs.com/mcp"
    }
  }
}
~/.codex/config.toml
[mcp_servers.filedproof]
url = "https://filedproof.davisvillelabs.com/mcp"
.cursor/mcp.json
{
  "mcpServers": {
    "filedproof": {
      "url": "https://filedproof.davisvillelabs.com/mcp"
    }
  }
}
.vscode/mcp.json
{
  "mcpServers": {
    "filedproof": {
      "url": "https://filedproof.davisvillelabs.com/mcp"
    }
  }
}

Available tools 12

Read directly from the server with tools/list, grouped by what they act on. If a tool disappears, we record the date.

filedproof
filedproof.build_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.
filedproof.build_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.
filedproof.build_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.
filedproof.build_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.
filedproof.check_disclosure_changes
Configured $15.00 USD specialist operation when runtime commerce is active. Use this for one issuer when the caller needs topic-relevant changes in newly filed disclosures prioritized against the prior filing of the same form, with explainable attention signals, compact before/after evidence, exact SEC provenance, uncertainty, follow-up guidance, and retry-safe checkpoint state. Use filedproof.compare_filings for a free one-off structural diff between two known accessions, filedproof.build_disclosure_lineage for historical evolution, or filedproof.list_filings first when forms, accessions, or coverage are 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.
filedproof.compare_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.
filedproof.list_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.
filedproof.preflight_financial_fact
Free eligibility check only for filedproof.reconcile_financial_fact. Use this before the $1 specialist operation when the issuer CIK, anchor accession, supported metric, fiscal-quarter dates, or required SEC Company Facts contexts may be uncertain. It validates applicability without revealing the reconciled value, source values, or derivation arithmetic. For issuer lookup, filing inventory, or general disclosure research, use filedproof.resolve_issuer, filedproof.list_filings, or filedproof.search_evidence instead.
filedproof.reconcile_financial_fact
$1.00 USD specialist operation when commerce is active. Use this for exactly one supported standalone-quarter revenue, net income, or operating cash flow value anchored to a non-amended 10-Q or 10-K. It returns exact reporting context, a direct value or reproducible cumulative-period subtraction, validation checks, and SEC provenance only when deterministic context compatibility is established. 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. If the requested fact is not safely resolvable, the operation abstains before payment.
filedproof.resolve_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.
filedproof.search_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.
filedproof.verify_claim
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.

Endpoints

URLTransportStateLatencyChecked
https://filedproof.davisvillelabs.com/mcp streamable-http answering 1091 ms 6 min ago

Alternatives to FiledProof

same job, measured the same way
HelloBooks AI Agents MCP Server
by hellobooksaiagents

AI agents for bookkeeping, reconciliation, and financial close for SMBs.

29 tools answering
Arkolith
by wikatar

Evidence-backed capital-change intelligence and sourced financial data for AI agents

answering
I
Agentic AI
by anthonywlicausi

Deal intelligence for agents: SEC-verified financials, validation, institutional deal scoring.

4 tools answering
Fintel Discovery — Financial Intelligence for AI Agents
by findimitrov

Delivers public regulatory and market data from 11 key sources such as FINRA, SEC, Census, FRED

32 tools answering
Stocksense
by mikejj-creation

Financial data for AI agents: SEC filings, price history, insider trades, and more.

34 installs/wk local only
Toolstem MCP Server
by toolstem

Financial intelligence MCP for AI agents — DCF, ratios, comparisons. Pre-computed signals.

69 installs/wk local only
MetricDuck — Financial Analysis
by metricduck

SEC filing intelligence for AI agents. Financials, screening, peer comparison for 5,000+ companies.

22 tools answering
I
Fintel Discovery — Financial Intelligence for AI Agents
by nikolayds

DEPRECATED — this server is no longer maintained.

local only

FiledProof — questions

Answers built from our own checks of this server.

What can FiledProof do?
It exposes 12 tools, read directly from the server on our last check. Among them: filedproof.build_disclosure_lineage, filedproof.build_disclosure_matrix, filedproof.build_evidence_pack, filedproof.build_timeline, filedproof.check_disclosure_changes, filedproof.compare_filings and 6 more. The full list with descriptions is on this page — we take it from the server itself via tools/list, not from a README. How MCP servers expose tools in the first place →
Is FiledProof working right now?
We send a real MCP handshake every 15 minutes. Over the last 24 hours 92 of 92 checks got a reply (100.0%), average response time 565 ms. The bar chart above shows every period we have measured.
How do I connect FiledProof?
Copy the ready config from this page — we generate it for Claude Code, Claude Desktop, Codex, Cursor and VS Code, each with the file path that client actually reads. It is a remote server, so there is nothing to install — the client connects to the address.
Does FiledProof need an API key?
No. FiledProof completed a full MCP handshake with us as an anonymous client and listed its tools without asking for anything. All 12 of them are readable on this page. This is what we observed, not what the docs claim.
How fast is FiledProof?
It answers our handshake in 565 ms on average, which is faster than 23% of all working MCP servers we measure. That is on the slow side — worth knowing if the tool sits inside an interactive loop. The comparison comes from our own checks across the whole registry, every 15 minutes.