Davisville Labs MCP server

Which servers in the official MCP registry are Davisville Labs's own, whether they answer, and what they offer. A program checked each of these, nobody copied them from a product page.

read 2026-10-19

← Back to Davisville Labs

Whose server it is

Registry namecom.davisvillelabs.filedproof/filedproofverified in the MCP registry

The registry name sits under davisvillelabs.com. The registry only lets a publisher use that namespace after proving control of the domain through DNS or HTTP.

When we asked itchecked 2026-10-19

Stateanswerschecked 2026-10-19
Tools13
Server calls itselfFiledProof
Server version0.9.0
Protocol version2025-06-18

On 2026-10-19 the server answered initialize and tools/list without a sign-in. First answer in 445 ms.

Measured dailydaily checks: 1, the first on 2026-10-19

Answeredmeasuring1 of the 7 daily checks it takes to print a share
Median first answer553 ms
Space in an agent's context≈ 6,440 tokensthe definitions of all its tools (13), which an agent carries on every turn
Tool definitionsA · 100 of 100

Every tool passes all six checks.

Worth a look

None of the five warning signs in these definitions.

A program checks the server once a day: initialize and tools/list, no model. Tokens are the definitions' length at about four characters a token. The grade averages six checks of every tool's name, description, schema and annotations; it says how well the tools are described, not whether they work.

Tools it offers13 tools · read 2026-10-19

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…
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…
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.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…
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…
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…
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…
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…
filedproof.check_material_filing_changes
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…
filedproof.check_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…
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.preflight_financial_fact
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…
filedproof.reconcile_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…

How to connect

Add the server to your MCP client config. Claude Desktop, Cursor and most other clients read this shape:

{
  "mcpServers": {
    "filedproof": {
      "type": "http",
      "url": "https://filedproof.davisvillelabs.com/mcp"
    }
  }
}

Other servers listed as Davisville Labs's

com.davisvillelabs.filmrights/filmrightsproofanswers, 2 toolsverified in the MCP registry
com.davisvillelabs/exitproofanswers, 6 toolsverified in the MCP registry
com.davisvillelabs/facilityproofnot asked yetverified in the MCP registry
io.github.davisvillelabs/ai-agent-analyticsnot asked yetendpoint on the vendor's domain
io.github.davisvillelabs/localproofnot asked yetendpoint on the vendor's domain
io.github.davisvillelabs/payeeproofnot asked yetendpoint on the vendor's domain
io.github.davisvillelabs/scopeproofnot asked yetendpoint on the vendor's domain

Each line is something a program found when it went looking: the registry entry, the server's own answer, a spec that parses. A missing line means we did not find it, not that it does not exist.