getorderability: AIO orderability door

io.github.allooloo/getorderabilityVersion 0.27.0

AIO orderability: may a capital product be ordered for a client category? Signed by the home node.

Status

Responds144 msNov 14, 2026, 14:44 UTCAnswered our handshake without sign-in.

Registry data may be out of date

We could not refresh it, so this page shows the last copy.

Last checked: Nov 14, 2026, 14:44 UTC
Latency: 144 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.getorderability.ai/mcpResponds144 msNov 14, 2026, 14:44 UTC

No sign-in

Claude Code

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

Claude Desktop and claude.ai

1
2
3

Settings > Connectors > Add custom connector
Name: getorderability
Remote MCP server URL: https://mcp.getorderability.ai/mcp

Cursor

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

VS Code

code --add-mcp '{"name":"getorderability","type":"http","url":"https://mcp.getorderability.ai/mcp"}'

Built your own server? run.zero hosts MCP servers on European infrastructure.

Host your own MCP server on run.zero

Tools

7 tools

Tools of getorderability: AIO orderability door
	Description		Read-only	Idempotent	Open world
`get_orderability`The AIO-10060 orderability outcome for one listed security and one client category of its home market's chapter: the apex finds the owning node by the subject, as for get_record, and the node's door produces it — one ACM-68000 signal where the evidence reaches it, or evidence_gaps with the pages checked and no signal; every element points at its chapter or record field; signed by the node (kid allooloo-eco-2026-10) and receipted at mcp.rco-records.ai with the node as writer.	The AIO-10060 orderability outcome for one listed security and one client category of its home market's chapter: the apex finds the owning node by the subject, as for get_record, and the node's door produces it — one ACM-68000 signal where the evidence reaches it, or evidence_gaps with the pages checked and no signal; every element points at its chapter or record field; signed by the node (kid allooloo-eco-2026-10) and receipted at mcp.rco-records.ai with the node as writer.	No	Yes	Yes	No
`get_record`Return the full Capital Markets Record, served by the owning node's regional door (never stored at the apex).	Return the full Capital Markets Record, served by the owning node's regional door (never stored at the apex).	No	Yes	Yes	No
`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 candidates (add the exchange); a GTIN is ACM-404 (not a listed-security identifier: ask gtinfetch.ai); a home node that does not answer returns an error, never a signal. ACM-000, ACM-300 and ACM-500 are reserved (ACM-68000 v1.1) and never served. ACM-403 HALTED is advisory: the nodes carry no halt flag yet, so the answer links the market's halts page. Each signal has its page at https://acm-<code>.ai/.	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 candidates (add the exchange); a GTIN is ACM-404 (not a listed-security identifier: ask gtinfetch.ai); a home node that does not answer returns an error, never a signal. ACM-000, ACM-300 and ACM-500 are reserved (ACM-68000 v1.1) and never served. ACM-403 HALTED is advisory: the nodes carry no halt flag yet, so the answer links the market's halts page. Each signal has its page at https://acm-<code>.ai/.	No	Yes	Yes	No
`list_aliases`Sourced trade and former names, served by the owning node's regional door.	Sourced trade and former names, served by the owning node's regional door.	No	Yes	Yes	No
`list_events_since`Dated, URL'd disclosure events for an issuer since a date, served by the owning node's regional door.	Dated, URL'd disclosure events for an issuer since a date, served by the owning node's regional door.	No	Yes	Yes	No
`list_nodes`Every market node on the roster (nodes.json, region on each), which are live, their regional doors and Agent Cards.	Every market node on the roster (nodes.json, region on each), which are live, their regional doors and Agent Cards.	No	Yes	Yes	No
`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.	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.	No	Yes	Yes	No

Details

Registry status: Active
Published: Nov 13, 2026
Updated: Nov 13, 2026
Website: https://getorderability.ai/⁠ (opens in a new tab)
Repository: https://github.com/allooloo/cm-kg⁠ (opens in a new tab)
Categories: Uncategorized
GDPR: Not declared

Are you the operator? Claim this listing