io.github.allooloo/getorderability

getorderability: AIO orderability door

Is the getorderability MCP server down? No. It answered initialize and tools/list in the probe of 2026-11-01.

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

alive probed 2026-11-01 · HTTP 200

7tools

1.3ktokens in Claude Opus 5.5

0.7 %of Claude's 200k window

0.5×the median server

498 msto initialize

332 msto list tools

Endpoint: https://mcp.getorderability.ai/mcp (streamable-http)
Host: mcp.getorderability.ai
Protocol: 2025-11-25
Reports itself as: getorderability 0.20.0
Capabilities: tools
Instructions: 1 097 characters
Of a 1M window: 0.1 % of a 1M context window
Count: 1.3k tokens in Claude Opus 5.5, exact, measured 2026-11-01. With the Claude Code prefix mcp__…__ on each tool name: 1.4k. The o200k_base estimate is 797. Counted again when the tool definitions change. Method.
Repository: https://github.com/allooloo/cm-kg
Website: https://getorderability.ai
Registry: active, updated 2026-11-01 · registry entry

Most expensive tools

The Claude column scales the o200k estimate of each tool by this server's ratio of exact to estimate, 1.68×.

Tool	≈ Claude tokens	o200k estimate	Share of this server
get_signal	394	235	29 %
get_orderability	355	212	27 %
resolve_issuer	211	126	16 %
list_events_since	124	74	9 %
get_record	99	59	7 %

These registry entries have the same tool names and the same schema sizes.

The result of the latest probe, the tool count and the token cost. The feed has an entry for every probe that changed them.

Stops answering, comes back, tool set or cost changes. One confirmation mail first, a stop link in every mail.

Fixed something? Probe it now, with the same steps as the daily run. This page updates with the next daily run.