NestDaddy

Electronic Compliance Objects (49 markets)

io.github.allooloo/eco · v0.27.0

Each market's disclosure regime as one sourced, signed object, with the issuer's ACM-68000 signal.

Connect Remote server

Terminal
claude mcp add --transport http eco https://mcp.getissuer.ai/eco/mcp
~/.cursor/mcp.json
{
  "mcpServers": {
    "eco": {
      "url": "https://mcp.getissuer.ai/eco/mcp"
    }
  }
}
.vscode/mcp.json
{
  "servers": {
    "eco": {
      "type": "http",
      "url": "https://mcp.getissuer.ai/eco/mcp"
    }
  }
}
Claude Desktop
Settings > Connectors > Add custom connector
URL: https://mcp.getissuer.ai/eco/mcp

Tools 4 found in our last check

  • 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.

  • list_nodes

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

  • get_signal

    The 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_eco

    The 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

Endpointhttps://mcp.getissuer.ai/eco/mcp (Streamable HTTP)
First published13 Nov 2026
Last updated13 Nov 2026
Registry nameio.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.