getfilings: the Filings door MCP Server

by allooloo Your server? Claim it

answering

getfilings: the Filings door is answering right now. Last checked 6 min ago. It exposes 3 tools. Last commit 5 Nov 2026.

The disclosures of an issuer in a date range, from the record: signed and receipted (RCO-10060).

Uptime history 56 hours of history

56 hours agonow

100.0%

Uptime 24h

91 of 91 checks

Tools

read from the server

174 ms

Response time

average over 24h

Stars

last commit 5 Nov 2026

Nothing serious here today

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

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.

Claude Code Claude Desktop Codex Cursor VS Code

run in your terminal

claude mcp add getfilings --transport http https://mcp.getfilings.ai/mcp

Settings → Connectors → Add custom connector, then paste this address

https://mcp.getfilings.ai/mcp

~/.codex/config.toml

[mcp_servers.getfilings]
url = "https://mcp.getfilings.ai/mcp"

.cursor/mcp.json

{
  "mcpServers": {
    "getfilings": {
      "url": "https://mcp.getfilings.ai/mcp"
    }
  }
}

.vscode/mcp.json

{
  "servers": {
    "getfilings": {
      "type": "http",
      "url": "https://mcp.getfilings.ai/mcp"
    }
  }
}

Available tools 3

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

filings

get_filings

get_filings is the disclosures of an issuer in a date range: an issuer by ticker, ISIN or LEI plus a date range returns every filing and release on the record for that issuer in that range, each with its type, its date, its source page and its read date — signed by the node of the issuer's market and receipted. Served from the record as read; nothing new is collected and nothing is inferred. Typed errors: unknown_issuer, ambiguous, not_on_record (per field, per market), invalid_request. Door: https://mcp.getfilings.ai/mcp (routes to the owning node); every node door answers it for its own market.

nodes

list_nodes

Every market node on the roster (nodes.json, region on each), which are live, their regional doors and Agent Cards.

resolve

resolve_issuer

Find a listed company by ticker, ISIN or LEI: the apex names the owning node and forwards to that node's regional door for the record summary.

Endpoints

URL	Transport	State	Latency	Checked
https://mcp.getfilings.ai/mcp	streamable-http	answering	138 ms	6 min ago

Alternatives to getfilings: the Filings door

same job, measured the same way

getasof: the As Of door

by allooloo

The issuer record as of any date, from the sealed vintage: signed and receipted (RCO-10060).

4 tools answering

getauditor: the Auditor door

by allooloo

The auditor of an issuer and every change on the record, dated: signed and receipted (RCO-10060).

3 tools answering

getticker: the Ticker door

by allooloo

The issuer behind a ticker: ISIN, LEI, listing and status, from the record: signed and receipted.

3 tools answering

gettargetmarket: the Target Market door

by allooloo

Target market statements by ISIN: filed by the manufacturer, signed, receipted (AIO-10060 v1.2).

8 tools answering

datastandard

by datastandard

The filed record of India's listed companies, every figure tied to the filing it came from.

answering

Postcept

by postcept

Verify agent actions against the system of record and get signed completion receipts.

52 installs/wk local only

SEV — Company Discovery from SEC Filings

by etsquareai

Ask a research question; in seconds get ranked companies, vetted 10-K/10-Q passages and financials.

327 installs/wk local only

leaks.md and confession.md

by thechristianaicompany

Anonymous, encrypted disclosure of AI alignment and safety failures, with signed receipts.

11 tools answering

getfilings: the Filings door — questions

Answers built from our own checks of this server.

What can getfilings: the Filings door do?

It exposes 3 tools, read directly from the server on our last check. Among them: get_filings, list_nodes, resolve_issuer. 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 getfilings: the Filings door working right now?

We send a real MCP handshake every 15 minutes. Over the last 24 hours 91 of 91 checks got a reply (100.0%), average response time 174 ms. The bar chart above shows every period we have measured.

How do I connect getfilings: the Filings door?

Copy the ready config from this page. We generate it for Claude Code, Claude Desktop, Codex, Cursor and VS Code, each in the form that client actually reads. It is a remote server, so there is nothing to install — the client connects to the address.

Does getfilings: the Filings door need an API key?

No. getfilings: the Filings door completed a full MCP handshake with us as an anonymous client and listed its tools without asking for anything. All 3 of them are readable on this page. This is what we observed, not what the docs claim.

How fast is getfilings: the Filings door?

It answers our handshake in 174 ms on average, which is faster than 77% of all working MCP servers we measure. That puts it in the quick quarter of the ecosystem. The comparison comes from our own checks across the whole registry, every 15 minutes.

Is getfilings: the Filings door open source?

We cannot say either way: written in Python and 0 stars on GitHub, but we could not determine the licence, and without one the code is not open source by default.