AIO orderability: may a capital product be ordered for a client category? Signed by the home node.
Maintain this server? Claim it
Call this server's tools from your browser. Nothing to install.
Requests go through mcptry because browsers can't call most MCP servers directly. Header values are sent to the server for that request only and are never stored or logged.
Tool list from our last check. Connect live to refresh it.
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.
ISIN (best), ticker with exchange (TSX:SHOP, SHEL.L), LEI or CMR key.
One client category exactly as the market's chapter names it (the node door's /book/aio.json, client_categories).
Pick your client. Values in capitals, like YOUR_TOKEN, are yours to fill in.
claude mcp add --transport http getorderability https://mcp.getorderability.ai/mcp
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.
| Argument | Type | Description |
|---|---|---|
| subject* | string | ISIN (best), ticker with exchange (TSX:SHOP, SHEL.L), LEI or CMR key. |
| client_category* | string | One client category exactly as the market's chapter names it (the node door's /book/aio.json, client_categories). |
{
"type": "object",
"required": [
"subject",
"client_category"
],
"properties": {
"subject": {
"type": "string",
"description": "ISIN (best), ticker with exchange (TSX:SHOP, SHEL.L), LEI or CMR key."
},
"client_category": {
"type": "string",
"description": "One client category exactly as the market's chapter names it (the node door's /book/aio.json, client_categories)."
}
}
}Return the full Capital Markets Record, served by the owning node's regional door (never stored at the apex).
| Argument | Type | Description |
|---|---|---|
| version | integer | |
| identifier* | string |
{
"type": "object",
"required": [
"identifier"
],
"properties": {
"version": {
"type": "integer"
},
"identifier": {
"type": "string"
}
}
}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/.
| Argument | Type | Description |
|---|---|---|
| identifier* | string | ISIN (best), ticker with exchange (TSX:SHOP, SHEL.L), LEI or CMR key. |
{
"type": "object",
"required": [
"identifier"
],
"properties": {
"identifier": {
"type": "string",
"description": "ISIN (best), ticker with exchange (TSX:SHOP, SHEL.L), LEI or CMR key."
}
}
}Sourced trade and former names, served by the owning node's regional door.
| Argument | Type | Description |
|---|---|---|
| identifier* | string |
{
"type": "object",
"required": [
"identifier"
],
"properties": {
"identifier": {
"type": "string"
}
}
}Dated, URL'd disclosure events for an issuer since a date, served by the owning node's regional door.
| Argument | Type | Description |
|---|---|---|
| limit | integer | |
| since | string | |
| cursor | integer | |
| identifier* | string |
{
"type": "object",
"required": [
"identifier"
],
"properties": {
"limit": {
"type": "integer"
},
"since": {
"type": "string"
},
"cursor": {
"type": "integer"
},
"identifier": {
"type": "string"
}
}
}Every market node on the roster (nodes.json, region on each), which are live, their regional doors and Agent Cards.
No arguments.
{
"type": "object",
"properties": {}
}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.
| Argument | Type | Description |
|---|---|---|
| identifier* | string | Ticker with or without exchange (SHOP, TSX:SHOP, SHEL.L, BHP.AX, D05.SI, NESN.SW, SAP.DE, 7203.T, 005930.KS), ISIN, LEI, an exact legal name or a sourced alias. |
{
"type": "object",
"required": [
"identifier"
],
"properties": {
"identifier": {
"type": "string",
"description": "Ticker with or without exchange (SHOP, TSX:SHOP, SHEL.L, BHP.AX, D05.SI, NESN.SW, SAP.DE, 7203.T, 005930.KS), ISIN, LEI, an exact legal name or a sourced alias."
}
}
}We read every tool's name, description and inputs the way the model will, looking for instructions hidden from you. A clean result means no warning signs, not a guarantee. Scanned Nov 1, 2026.