getticker: the Ticker door MCP Server

by allooloo Your server? Claim it

answering

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

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

Uptime history 56 hours of history

56 hours agonow

100.0%

Uptime 24h

91 of 91 checks

Tools

read from the server

181 ms

Response time

average over 24h

Stars

last commit 5 Nov 2026

Nothing serious here today

Today is the operative word: we check getticker: the Ticker 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 4 min ago.

Claude Code Claude Desktop Codex Cursor VS Code

run in your terminal

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

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

https://mcp.getticker.ai/mcp

~/.codex/config.toml

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

.cursor/mcp.json

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

.vscode/mcp.json

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

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.

ticker

get_ticker

get_ticker is the issuer behind a ticker: a ticker and its exchange, or an ISIN or LEI, returns the issuer, its ISIN, its LEI, its listing and its status — every value with its source page and read date, signed by the node of the listing's market and receipted. Served from the record as read; a value the market's record does not carry says not_on_record. Typed errors: unknown_issuer, ambiguous, not_on_record (per field, per market), invalid_request. Door: https://mcp.getticker.ai/mcp (routes to the owning node); every node door answers it for its own market.

Endpoints

URL	Transport	State	Latency	Checked
https://mcp.getticker.ai/mcp	streamable-http	answering	133 ms	4 min ago

Alternatives to getticker: the Ticker door

same job, measured the same way

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

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

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

PERM Tracker

by permtracker

PERM, prevailing wage and H-1B case status, DOL's queue and the visa bulletin, from federal records

7 tools answering

Lodestar Stamp

by banjo-ventures

Lodestar issues signed, dated business records. Reads are free.

86 installs/wk 7 tools answering

Tersign Evidence

by tersignhq

The record layer for the machine age: counter-signed receipts and agent action records.

106 installs/wk local only

ScreenVerity

by williamblakecunningham-max

Free U.S. exclusion, debarment and licence screening with a signed receipt of the lists checked.

71 installs/wk local only

getticker: the Ticker door — questions

Answers built from our own checks of this server.

What can getticker: the Ticker door do?

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

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

No. getticker: the Ticker 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 getticker: the Ticker door?

It answers our handshake in 181 ms on average, which is faster than 75% 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 getticker: the Ticker 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.