getorderability: AIO orderability door

io.github.alloolooPublished by GitHub account allooloov0.1.0Updated Nov 1, 2026

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

VerifiedStreamable HTTPWeb executableFinanceBusiness & Commerce

Overview

AI-generated overview

Remote MCP router that answers whether a listed security may be ordered for a given client category in its home market, plus issuer records and signals.

What you can do
  • Check orderability of a listed security for a client category in its home market, with evidence gaps when the rules do not reach it
  • Resolve a listed company by ticker, ISIN or LEI and get its Capital Markets Record
  • Get the ACM-68000 signal for a security in its home market, such as on the register, not on the register, or read the filing
  • List sourced trade and former names, and dated disclosure events since a given date
  • List every market node on the roster, which are live, and their regional doors
When to use it
Useful when an assistant supports product governance, distribution or sales checks and needs a market's own rule-based answer on whether a product may be ordered for a client category, or needs issuer records, signals and disclosure events for listed securities.
Requirements
A remote streamable HTTP endpoint; no installation, authentication, API keys or environment variables are declared. Network access to the endpoint is needed.
Before you install
The server describes itself as an index-only router that forwards requests to regional market nodes, which produce and sign the results; the answers reflect each market's rules and are not a substitute for the firm's own compliance judgment. It states it is read-only and returns no prices, but results are served by third-party nodes.

Installation

In SourceWeft

  1. Open getorderability: AIO orderability door in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/io.github.allooloo%2Fgetorderability/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config.

{
  "mcpServers": {
    "getorderability-aio-orderability-door": {
      "type": "http",
      "url": "https://mcp.getorderability.ai/mcp"
    }
  }
}

README

This repository has no README.

Tools

7

get_orderability

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.

Parameterssubjectrequiredclient_categoryrequired

resolve_issuer

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.

Parametersidentifierrequired

get_record

Get Capital Markets Record

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

Parametersversionidentifierrequired

get_signal

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

Parametersidentifierrequired

list_aliases

List sourced aliases

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

Parametersidentifierrequired

list_events_since

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.

Parameterslimitsincecursoridentifierrequired

list_nodes

List market nodes

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

Takes no parameters.

Version history

1
  1. v0.1.0LatestNov 1, 2026

Score

75% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 daysRequired25 pts
  • Auth declaredRequired10 pts
  • Tools listedRequired15 pts
  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts

    Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.

  • License10 pts

    Declare a license in the repository or the registry entry.