# getorderability: AIO orderability door (remote · mcp.getorderability.ai)

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

- Trust score: 66/100 (medium)
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-04

## Components

- remote · `mcp.getorderability.ai`: 66/100 (this document), [markdown](https://verifymcp.io/servers/allooloo-getorderability/mcp.md), [page](https://verifymcp.io/servers/allooloo-getorderability/mcp)

## Channel facts

- Endpoint: `https://mcp.getorderability.ai/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `0.1.0`

## Trust breakdown

How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-11-04.

- **Endpoint Security**: 69/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one.
  - HTTPS enforcement could not be verified: the plaintext port answered with HTTP 405, which proves neither a plaintext path nor enforcement.
  - The HSTS (Strict-Transport-Security) header is present.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 58/100
  - AI-judged instruction clarity (fair).
  - Context-footprint check failed: tool/resource definitions use about 919 tokens (~131/item across 7 items; 7 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 10/100
  - Stability observed for 3 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 79/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 36% of tool parameters carry a description.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 7 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 8 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

## Install

### How do I install the getorderability: AIO orderability door MCP server?

getorderability: AIO orderability door is a hosted endpoint at https://mcp.getorderability.ai/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

### Claude

```bash
claude mcp add --transport http allooloo-getorderability 'https://mcp.getorderability.ai/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "allooloo-getorderability": {
      "url": "https://mcp.getorderability.ai/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "allooloo-getorderability": {
      "type": "http",
      "url": "https://mcp.getorderability.ai/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.allooloo-getorderability]
url = "https://mcp.getorderability.ai/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "allooloo-getorderability": {
      "type": "remote",
      "url": "https://mcp.getorderability.ai/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add allooloo-getorderability --url 'https://mcp.getorderability.ai/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  allooloo-getorderability:
    url: "https://mcp.getorderability.ai/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "allooloo-getorderability": {
      "Transport": "http",
      "Url": "https://mcp.getorderability.ai/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add allooloo-getorderability -t streamable-http -u 'https://mcp.getorderability.ai/mcp'
```

### Other

```json
{
  "mcpServers": {
    "allooloo-getorderability": {
      "type": "http",
      "url": "https://mcp.getorderability.ai/mcp"
    }
  }
}
```

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-11-04 (score 66, +1)

No change was recorded against any check on this day. Stability & Change Management went from 7 to 10. That category is still filling its 30-day observation window: 2 days of observed history at the previous scan, 3 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-11-03 (score 65, 0)

- [functional] Server version: 0.21.0 → 0.23.0

### 2026-11-02 (score 65, +1)

- [functional improvement] Stability: unverified → 0.03
- [functional] Server version: 0.20.0 → 0.21.0

### 2026-11-01 (score 64)

First indexed and scored.

## MCP tools (7)

### `get_orderability` (~188 tokens)

Get orderability outcome (AIO-10060)

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 parameters:

- `client_category` (string, required): One client category exactly as the market's chapter names it (the node door's /book/aio.json, client_categories).
- `subject` (string, required): ISIN (best), ticker with exchange (TSX:SHOP, SHEL.L), LEI or CMR key.

### `resolve_issuer` (~109 tokens)

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.

Input parameters:

- `identifier` (string, required): 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.

### `get_record` (~44 tokens)

Get Capital Markets Record

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

Input parameters:

- `identifier` (string, required)
- `version` (integer)

### `get_signal` (~216 tokens)

Get ACM-68000 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, 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 parameters:

- `identifier` (string, required): ISIN (best), ticker with exchange (TSX:SHOP, SHEL.L), LEI or CMR key.

### `list_aliases` (~32 tokens)

List sourced aliases

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

Input parameters:

- `identifier` (string, required)

### `list_events_since` (~60 tokens)

List disclosure events since a date

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

Input parameters:

- `cursor` (integer)
- `identifier` (string, required)
- `limit` (integer)
- `since` (string)

### `list_nodes` (~33 tokens)

List market nodes

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

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/allooloo-getorderability/mcp#diagnostics

## Score history

- 2026-11-04: 66
- 2026-11-03: 65
- 2026-11-02: 65
- 2026-11-01: 64

## Common questions

### What is the getorderability: AIO orderability door MCP server?

getorderability: AIO orderability door is an MCP server listed in the public MCP registry as io.github.allooloo/getorderability. AIO orderability: may a capital product be ordered for a client category? Signed by the home node. This page covers its hosted endpoint (https://mcp.getorderability.ai/mcp).

### Is the getorderability: AIO orderability door MCP server safe to use?

getorderability: AIO orderability door scores 66 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

### What tools does the getorderability: AIO orderability door MCP server expose?

getorderability: AIO orderability door exposes 7 tools: get_orderability, resolve_issuer, get_record, get_signal, list_aliases, and 2 more. Their descriptions and schemas cost roughly 682 tokens of context every time the server is loaded.

### Does the getorderability: AIO orderability door MCP server require authentication?

No. We connected to getorderability: AIO orderability door without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

### Is the getorderability: AIO orderability door MCP server still maintained?

getorderability: AIO orderability door is still listed as active in the MCP registry. We last reached this channel on 4 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

## Links

- Remote endpoint: https://mcp.getorderability.ai/mcp
- Repository: https://github.com/allooloo/cm-kg
- Website: https://getorderability.ai/
- Changelog RSS feed: https://verifymcp.io/servers/allooloo-getorderability/mcp.xml
- Changelog JSON feed: https://verifymcp.io/servers/allooloo-getorderability/mcp.json
- HTML version of this page: https://verifymcp.io/servers/allooloo-getorderability/mcp