getauditor: the Auditor door MCP Server

by allooloo Your server? Claim it

answering

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

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

Uptime history 55 hours of history

55 hours agonow

100.0%

Uptime 24h

92 of 92 checks

Tools

read from the server

155 ms

Response time

average over 24h

Stars

last commit 5 Nov 2026

Nothing serious here today

Today is the operative word: we check getauditor: the Auditor 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 5 min ago.

Claude Code Claude Desktop Codex Cursor VS Code

run in your terminal

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

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

https://mcp.getauditor.ai/mcp

~/.codex/config.toml

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

.cursor/mcp.json

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

.vscode/mcp.json

{
  "servers": {
    "getauditor": {
      "type": "http",
      "url": "https://mcp.getauditor.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.

auditor

get_auditor

get_auditor is the auditor of an issuer: an issuer by ticker, ISIN or LEI returns its auditor of record and every auditor change on the record, dated — each with its source page and read date, signed by the node of the issuer's market and receipted. Where a market's record does not carry the auditor, the answer says not_on_record for that market; nothing is inferred. Typed errors: unknown_issuer, ambiguous, not_on_record (per field, per market), invalid_request. Door: https://mcp.getauditor.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.getauditor.ai/mcp	streamable-http	answering	117 ms	5 min ago

Alternatives to getauditor: the Auditor 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

getfilings: the Filings door

by allooloo

The disclosures of an issuer in a date range, from the record: 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

Postcept

by postcept

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

52 installs/wk local only

RCO Records - Record of Cleared Orders

by allooloo

The record of what the agent relied on: a signed, chained receipt per cleared read. Verify by id.

5 tools answering

QueryScope

by queryscope

Search Console in your AI IDE: the plan, stored history, and a measured record of every change.

answering

Kryptheon

by jhashantanu987-beep

Record a flow through your app, check it after every change, and attack a copy of your database.

79 installs/wk local only

getauditor: the Auditor door — questions

Answers built from our own checks of this server.

What can getauditor: the Auditor door do?

It exposes 3 tools, read directly from the server on our last check. Among them: get_auditor, 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 getauditor: the Auditor door 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 155 ms. The bar chart above shows every period we have measured.

How do I connect getauditor: the Auditor 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 getauditor: the Auditor door need an API key?

No. getauditor: the Auditor 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 getauditor: the Auditor door?

It answers our handshake in 155 ms on average, which is faster than 81% 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 getauditor: the Auditor 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.