getorderability: AIO orderability door
AIO orderability: may a capital product be ordered for a client category? Signed by the home node.
Should I use this
Quality & Safety
Findings (3)
- LOWTool 'list_aliases' description lacks action verbin list_aliases
- LOWTool 'list_events_since' description lacks action verbin list_events_since
- LOWTool 'list_nodes' description lacks action verbin list_nodes
Based on automated analysis of tool definitions and protocol compliance.
Context Cost
This is the approximate number of tokens consumed each time the server's tools are loaded into a model's context. Higher counts reduce the attention available for other tasks.
Install
One-Click Install
Add this to your `claude_desktop_config.json` file:
{
"mcpServers": {
"getorderability": {
"url": "https://mcp.getorderability.ai/mcp"
}
}
}Remote endpoints
https://mcp.getorderability.ai/mcpstreamable-httpWhat it can do
Tool inventory
Tools (7)
🟢get_orderability(subject, client_category)
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.
Input Schema
{
"type": "object",
"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)."
}
},
"required": [
"subject",
"client_category"
]
}🟢resolve_issuer(identifier)
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.
Input Schema
{
"type": "object",
"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."
}
},
"required": [
"identifier"
]
}🟢get_record(identifier, version)
Return the full Capital Markets Record, served by the owning node's regional door (never stored at the apex).
Input Schema
{
"type": "object",
"properties": {
"identifier": {
"type": "string"
},
"version": {
"type": "integer"
}
},
"required": [
"identifier"
]
}🟢get_signal(identifier)
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/.
Input Schema
{
"type": "object",
"properties": {
"identifier": {
"type": "string",
"description": "ISIN (best), ticker with exchange (TSX:SHOP, SHEL.L), LEI or CMR key."
}
},
"required": [
"identifier"
]
}🟢list_aliases(identifier)
Sourced trade and former names, served by the owning node's regional door.
Input Schema
{
"type": "object",
"properties": {
"identifier": {
"type": "string"
}
},
"required": [
"identifier"
]
}🟢list_events_since(identifier, since, cursor, limit)
Dated, URL'd disclosure events for an issuer since a date, served by the owning node's regional door.
Input Schema
{
"type": "object",
"properties": {
"identifier": {
"type": "string"
},
"since": {
"type": "string"
},
"cursor": {
"type": "integer"
},
"limit": {
"type": "integer"
}
},
"required": [
"identifier"
]
}🟢list_nodes
Every market node on the roster (nodes.json, region on each), which are live, their regional doors and Agent Cards.
Input Schema
{
"type": "object",
"properties": {}
}Community
Evidence