Each market's disclosure regime as one sourced, signed object, with the issuer's ACM-68000 signal.
Connect Remote server
claude mcp add --transport http eco https://mcp.getissuer.ai/eco/mcp
{
"mcpServers": {
"eco": {
"url": "https://mcp.getissuer.ai/eco/mcp"
}
}
}
{
"servers": {
"eco": {
"type": "http",
"url": "https://mcp.getissuer.ai/eco/mcp"
}
}
}
Settings > Connectors > Add custom connector
URL: https://mcp.getissuer.ai/eco/mcp
Tools 4 found in our last check
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.
list_nodesEvery market node on the roster (nodes.json, region on each), which are live, their regional doors and Agent Cards.
get_signalThe ACM-68000 signal for a listed security in its home market: ACM-200 TRADING (on the register), ACM-404 NOT ON THE REGISTER, ACM-451 READ THE FILING (a regulatory filing in the last three days, named), A bare ticker naming more than one issuer returns no signal but its candida…
get_ecoThe Electronic Compliance Object of one market (49): regulator, exchanges and listings page, regulated-information store, disclosure deadlines, ad hoc regime, filing format, ISIN prefix, LEI, calendar, languages, halts page — each field with its source page, signed (kid allooloo…
Details
| Endpoint | https://mcp.getissuer.ai/eco/mcp (Streamable HTTP) |
| First published | 13 Nov 2026 |
| Last updated | 13 Nov 2026 |
| Registry name | io.github.allooloo/eco |
More other servers See all
Listing data from the official MCP registry. Status and tools from NestDaddy's daily check. Browse all MCP servers.
