mcp-registry/com.davisvillelabs.filedproof/filedproof · v0.9.0
As of 2026-10-26 04:13 UTC, the Davisvillelabs Filedproof Filedproof MCP server is unknown with a Glimind reliability score of 89/100 (grade B). Over the last 30 days it answered 99.9% of Glimind's liveness checks. It had 1 outage in 90 days, with a median recovery of 6 minutes.
Primary-source SEC filing intelligence and financial/disclosure reconciliation for AI agents.
Point your MCP client at this streamable-http endpoint: https://filedproof.davisvillelabs.com/mcp
The endpoint did not complete an MCP handshake.
Check the URL, TLS certificate and that the server answers a JSON-RPC "initialize" POST. How to fix →
13 tool name(s) contain "." or exceed 64 characters, which OpenAI-compatible function calling rejects (^[a-zA-Z0-9_-]{1,64}$).
Use "_" or "-" instead of "." and keep names to 64 characters, so clients built on OpenAI-style tool calling don't have to rename (or drop) them. How to fix →
Paste-ready definitions with the problems above fixed. Changes marked verify need a human look. All of them as JSON: /v1/readiness/mcp-registry%2Fcom.davisvillelabs.filedproof%2Ffiledproof/fixes
{
"name": "filedproof_build_disclosure_lineage",
"description": "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 i",
"inputSchema": {
"type": "object",
"required": [
"identifier",
"topic"
],
"properties": {
"item": {
"type": "string",
"description": "Optional SEC filing item such as 1A or 7."
},
"forms": {
"type": "array",
"items": {
"type": "string"
},
"maxItems": 8,
"description": "SEC forms to include. Defaults to 10-K and 10-Q. Same-form transitions are linked independently."
},
"limit": {
"type": "integer",
"default": 30,
"maximum": 100,
"minimum": 1,
"description": "Maximum topic-relevant change evidence records retained per transition."
},
"topic": {
"type": "string",
"maxLength": 256,
"minLength": 1,
"description": "Public-company disclosure topic whose filing-to-filing history should be accumulated, such as AI regulation, cybersecurity, or supply-chain concentration."
},
"filings": {
"type": "integer",
"default": 6,
"maximum": 6,
"minimum": 2,
"description": "Maximum filings to inspect in this invocation. Previously persisted lineage can contain more accumulated history."
},
"history": {
"type": "boolean",
"default": true,
"description": "Use bounded historical SEC submission archives when the durable catalog does not already provide enough history."
},
"section": {
"type": "string",
"description": "Optional exact normalized section heading."
},
"identifier": {
"type": "string",
"minLength": 1,
"description": "Ticker, CIK, or exact SEC company name."
},
"comparisonLimit": {
"type": "integer",
"default": 250,
"maximum": 500,
"minimum": 1,
"description": "Maximum changed blocks inspected in each same-form structural comparison."
},
"fingerprintLimit": {
"type": "integer",
"default": 50,
"maximum": 50,
"minimum": 1,
"description": "Maximum relevant evidence records used to fingerprint one filing."
}
},
"additionalProperties": false
},
"annotations": {
"readOnlyHint": true,
"openWorldHint": true,
"idempotentHint": true,
"destructiveHint": false
},
"title": "Build historical disclosure lineage"
}{
"name": "filedproof_build_disclosure_matrix",
"description": "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",
"inputSchema": {
"type": "object",
"required": [
"identifiers",
"topic"
],
"properties": {
"item": {
"type": "string",
"description": "Optional SEC filing item such as 1A or 7."
},
"forms": {
"type": "array",
"items": {
"type": "string"
},
"default": [
"10-K"
],
"maxItems": 4,
"minItems": 1,
"description": "SEC forms to align. Defaults to 10-K for stronger cross-company comparability."
},
"limit": {
"type": "integer",
"default": 24,
"maximum": 100,
"minimum": 1,
"description": "Maximum topic-relevant change evidence retained in each underlying lineage transition."
},
"topic": {
"type": "string",
"maxLength": 256,
"minLength": 1,
"description": "Disclosure topic to align across companies, such as cybersecurity, AI infrastructure, or supply-chain concentration."
},
"filings": {
"type": "integer",
"default": 4,
"maximum": 6,
"minimum": 2,
"description": "Maximum filings per company used to build or reuse the underlying disclosure lineage."
},
"history": {
"type": "boolean",
"default": true,
"description": "Whether to use bounded historical SEC submission archives when needed."
},
"section": {
"type": "string",
"description": "Optional exact normalized section heading."
},
"identifiers": {
"type": "array",
"items": {
"type": "string",
"minLength": 1
},
"maxItems": 6,
"minItems": 2,
"description": "Two to six public-company identifiers to align on the same filing-grounded disclosure topic."
},
"comparisonLimit": {
"type": "integer",
"default": 200,
"maximum": 500,
"minimum": 1,
"description": "Maximum number of changed blocks to inspect in each filing comparison."
},
"maxArchiveFiles": {
"type": "integer",
"maximum": 20,
"minimum": 1,
"description": "Maximum number of historical SEC submission archive files to inspect when history is enabled."
},
"fingerprintLimit": {
"type": "integer",
"default": 30,
"maximum": 50,
"minimum": 1,
"description": "Maximum number of relevant evidence records used to fingerprint one filing."
},
"currentEvidenceLimit": {
"type": "integer",
"default": 6,
"maximum": 12,
"minimum": 1,
"description": "Maximum current-filing evidence records returned per company and form."
},
"transitionEvidenceLimit": {
"type": "integer",
"default": 6,
"maximum": 12,
"minimum": 1,
"description": "Maximum evidence records returned for each latest same-form transition."
}
},
"additionalProperties": false
},
"annotations": {
"readOnlyHint": true,
"openWorldHint": true,
"idempotentHint": true,
"destructiveHint": false
},
"title": "Build cross-company disclosure matrix"
}{
"name": "filedproof_build_evidence_pack",
"description": "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.",
"inputSchema": {
"type": "object",
"required": [
"identifier",
"q"
],
"properties": {
"q": {
"type": "string",
"maxLength": 256,
"minLength": 1,
"description": "Research question or disclosure topic."
},
"item": {
"type": "string",
"description": "Optional SEC filing item, such as 1A or 7."
},
"forms": {
"type": "array",
"items": {
"type": "string"
},
"maxItems": 8,
"description": "SEC forms to search. Defaults to 10-K and 10-Q."
},
"limit": {
"type": "integer",
"default": 12,
"maximum": 30,
"minimum": 1,
"description": "Maximum number of operation-specific evidence or result records to return."
},
"filings": {
"type": "integer",
"default": 3,
"maximum": 6,
"minimum": 1,
"description": "Maximum number of filings to inspect for this invocation."
},
"history": {
"type": "boolean",
"default": false,
"description": "Whether to use bounded historical SEC submission archives when needed."
},
"section": {
"type": "string",
"description": "Optional exact normalized section heading."
},
"identifier": {
"type": "string",
"minLength": 1,
"description": "Ticker, CIK, or exact SEC company name."
}
},
"additionalProperties": false
},
"annotations": {
"readOnlyHint": true,
"openWorldHint": true,
"idempotentHint": true,
"destructiveHint": false
},
"title": "Build answer-ready evidence pack"
}Get an email or webhook when this server's readiness drops by 10+ points, tool-poisoning text appears, or a tool breaks:
curl -X POST https://glimind.com/v1/subscriptions -H 'content-type: application/json' -d '{"tools":["mcp-registry/com.davisvillelabs.filedproof/filedproof"],"email":"[email protected]"}'Agents: watch_tool({"toolId": "mcp-registry/com.davisvillelabs.filedproof/filedproof"}) over MCP.
filedproof.preflight_financial_fact ~854 tokensfiledproof.reconcile_financial_fact ~854 tokensfiledproof.build_disclosure_matrix ~760 tokensfiledproof.check_disclosure_changes ~672 tokensfiledproof.build_disclosure_lineage ~610 tokensStatic checks of the advertised tools/list (schema, descriptions, annotations, tool-poisoning patterns, names, size) plus observed protocol, uptime, latency and contract changes. Read-only: no tool is ever called. Weights: schema 15, docs 20, safety 15, efficiency 15, compatibility 15, protocol 5, reliability 10, stability 5. Token counts are estimates (~3.6 characters per token).
Operator? Fix these, then re-check live. Embed the readiness badge:
[](https://glimind.com/server/mcp-registry%2Fcom.davisvillelabs.filedproof%2Ffiledproof?ref=badge)
<a href="https://glimind.com/server/mcp-registry%2Fcom.davisvillelabs.filedproof%2Ffiledproof?ref=badge"><img src="https://glimind.com/v1/readiness/badge/mcp-registry%2Fcom.davisvillelabs.filedproof%2Ffiledproof.svg" alt="MCP agent-readiness"></a>
.. image:: https://glimind.com/v1/readiness/badge/mcp-registry%2Fcom.davisvillelabs.filedproof%2Ffiledproof.svg :target: https://glimind.com/server/mcp-registry%2Fcom.davisvillelabs.filedproof%2Ffiledproof?ref=badge :alt: MCP agent-readiness
Glimind records every version of this server's tool definitions in a signed, append-only transparency log. Current manifest sha256:2fba616d566742df…, first seen 2026-10-17, included at leaf 4761 of 76,056. Version history · verify what your client received.
Compare: most reliable knowledge servers · most reliable data servers · most reliable retrieval servers · most reliable finance servers · most reliable search servers
Glimind tells agents whether a server is up right now and how to call it, then fails over to a live alternative when it isn't.
Claude Code
claude mcp add --transport http glimind https://glimind.com/mcp
Claude Desktop · Windsurf · Cline (mcpServers JSON)
{
"mcpServers": {
"glimind": {
"type": "http",
"url": "https://glimind.com/mcp"
}
}
}
As of 2026-10-26 04:13 UTC, the Davisvillelabs Filedproof Filedproof MCP server is unknown with a Glimind reliability score of 89/100 (grade B). Over the last 30 days it answered 99.9% of Glimind's liveness checks. It had 1 outage in 90 days, with a median recovery of 6 minutes.
Davisvillelabs Filedproof Filedproof MCP server advertises 13 tools, including filedproof.build_disclosure_lineage, filedproof.build_disclosure_matrix, filedproof.build_evidence_pack, filedproof.build_timeline, filedproof.check_disclosure_changes.
Point your MCP client at this streamable-http endpoint: https://filedproof.davisvillelabs.com/mcp
Glimind scanned all 13 tool definitions for tool-poisoning patterns — hidden or invisible characters, instructions that override the model, concealment from the user, requests to read credential or MCP config files, conversation exfiltration and cross-tool shadowing — and found none. This checks what the server tells the model, not what its code does; review the source before granting access to sensitive data.
Status page: 90-day uptime, every outage and how long it lasted.
Claim this listing to get the Verified operator marker, a remediation checklist and owner analytics, or embed the live badge from any of the tool pages above. Maintainers: alerts, deploy attestation and monthly reports.
Status is an automated estimate from Glimind's liveness checks (handshake and tool listing only; no tool is ever called) and may lag or differ from your network. Glimind is not affiliated with this server or its operator. Operator? Request a correction or opt out at https://glimind.com/opt-out.