getorderability: AIO orderability door

io.github.allooloo/getorderability · v0.1.0 · security

getorderability: AIO orderability door is healthy: it completed an MCP handshake in 635 ms and exposes 7 tools.

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

Endpoint: https://mcp.getorderability.ai/mcp (streamable-http)

Repository · Website · JSON · Add to my inventory

Facts

Users (last 30 days)0
HandshakeHealthy
Auth neededNone
Tool count7
Latency635 ms
Last checked (UTC)2026-11-01T07:40:22.893Z

Health history

Checked (UTC)StatusLatencyError
2026-11-01T07:40:22.893ZHealthy635

Tools (7)

get_orderabilityThe 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 che
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.
get_recordReturn the full Capital Markets Record, served by the owning node's regional door (never stored at the apex).
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 candidates (add the exchange
list_aliasesSourced trade and former names, served by the owning node's regional door.
list_events_sinceDated, URL'd disclosure events for an issuer since a date, served by the owning node's regional door.
list_nodesEvery market node on the roster (nodes.json, region on each), which are live, their regional doors and Agent Cards.