getticker: the Ticker door
io.github.allooloo/gettickerVersion 0.27.0The issuer behind a ticker: ISIN, LEI, listing and status, from the record: signed and receipted.
Status
Responds384 msAnswered our handshake without sign-in.- Last checked
- Nov 14, 2026, 14:44 UTC
- Latency
- 384 ms
- Remotes responding
- 1 of 1
- Sign-in
- No sign-in
- Hosting
- Hosted outside the EU (detected)
- Registry data as of
- Nov 14, 2026, 21:12 UTC
Data from the official MCP Registry, checked by run.zero. How we check
Connect
Streamable HTTP
https://mcp.getticker.ai/mcpResponds384 msNo sign-in
Claude Code
claude mcp add --transport http getticker https://mcp.getticker.ai/mcpClaude Desktop and claude.ai
Settings > Connectors > Add custom connector
Name: getticker
Remote MCP server URL: https://mcp.getticker.ai/mcpCursor
{
"mcpServers": {
"getticker": {
"url": "https://mcp.getticker.ai/mcp"
}
}
}VS Code
code --add-mcp '{"name":"getticker","type":"http","url":"https://mcp.getticker.ai/mcp"}'Built your own server? run.zero hosts MCP servers on European infrastructure.
Tools
3 tools
Read-only | Idempotent | Open world | ||
|---|---|---|---|---|
get_tickerget_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. | No | Yes | Yes | No |
list_nodesEvery market node on the roster (nodes.json, region on each), which are live, their regional doors and Agent Cards. | No | Yes | Yes | No |
resolve_issuerFind 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. | No | Yes | Yes | No |
Details
- Registry status
- Active
- Published
- Nov 13, 2026
- Updated
- Nov 13, 2026
- Categories
- Uncategorized
- GDPR
- Not declared