FiledProof
com.davisvillelabs.filedproof/filedproof · 0.9.0
Primary-source SEC filing intelligence and financial/disclosure reconciliation for AI agents.
Nobody here has read this server's code, because it publishes none. The description above is the maker's own, from the registry. A connection test shows whether it answers and what tools it says it has; it never calls a tool, so it cannot show what one does with your data.
Where it sits in the directory's order
What can be seen from outside, weighed as the directory publishes.
Observable signals: 45 of 100 points (at most 60 here)
| Input | Points | What was seen |
|---|---|---|
| Source published | held at 0 | No entry here publishes source: that is what puts it in this directory. |
| Licence stated | held at 0 | With no files, there is nothing for a licence to be stated in or held against. |
| Advisory state | held at 0 | Advisory databases index packages, and these entries publish none, so there is nothing to look up. |
| Auth declared | 0 of 15 | The registry entry declares no key. That is what it declares, not a finding that it has no protection. |
| Latest connection test reached it | 20 of 20 |
Where it answers
https://filedproof.davisvillelabs.com/mcpstreamable-http
Connection test
The MCP handshake, then a request for the tool list, with no key and no data of yours. Run nightly, and by anyone, at most once every ten minutes per server.
It completed the handshake and listed 13 tools.
- Protocol
- 2025-06-18
- Calls itself
- FiledProof 0.9.0
- Handshake time
- 362 ms
- HTTP status
- 200
The tools it lists (13, as of 4 days ago)
The tool-description rules found nothing in these descriptions. They look for instructions aimed at a model and for hidden characters; they cannot see what a tool does when it runs.
filedproof.resolve_issuerResolve 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.list_filingsList 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.search_evidenceFind 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.build_evidence_packPackage 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_timelineOrganize 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.
How this entry becomes a listing
For the maker. The catalogue lists what it can read, and this server publishes nothing to read yet. There are two routes, and only the first is open today.
Publish the source Open today
- Put the server's source in a public repository on github.com, with a licence.
- Keep a server.json in that repository naming this server,
com.davisvillelabs.filedproof/filedproof, and declare the repository in it:"repository": { "url": "https://github.com/owner/repo", "source": "github" }, adding"subfolder"when the server lives in a folder. - Publish that version to the official MCP registry.
- The nightly registry sweep records the declaration. This page stays, dated, and says the source is declared but not yet read.
- The catalogue reads declared repositories at a pinned commit, in batches run by hand, and lists the servers that meet the batch's rules (among them a server.json at that commit naming the server, an https endpoint and a licence). When it lists this server, this page links to the listing. There is no schedule, so no date can be promised.
List it through the maker studio Not open yet
From the official MCP registry, last updated there 22 days ago. The registry entry · filedproof.davisvillelabs.com