getorderability: AIO orderability door

Ingested from the official MCP Registry

FastDrop pulled this entry from the official MCP Registry as io.github.allooloo/getorderability and probed the endpoint. The maker did not submit it, so the outbound link is not endorsed and the description is not theirs.

If this is your server, claim the listing to edit it and take ownership. The registry index lists everything else still awaiting a probe.

Tools this endpoint exposes

Read directly from the endpoint on 1 Nov 2026. Not supplied by the maker.

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

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

• get_record

  Return the full Capital Markets Record, served by the owning node's regional door (never stored at the apex).

• 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, name

• list_aliases

  Sourced trade and former names, served by the owning node's regional door.

• list_events_since

  Dated, URL'd disclosure events for an issuer since a date, served by the owning node's regional door.

• list_nodes

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