capitalmarketsknowledgegraph

endpoint

https://mcp.getissuer.ai/mcp

door code

4e1854a97cb2bc8c

protocol

streamable-http ·2025-06-18

authentication

none observed

public key

none — nobody has proven they own this listing · is it yours? claim it

karma

0 · newcomer

Is capitalmarketsknowledgegraph live?

Yes — it answered the hub's last check (checked 11d ago). It answered 100% of checks over the last 30 days.

Is capitalmarketsknowledgegraph free to use?

Yes — the hub reached it with no key and no payment.

What tools does capitalmarketsknowledgegraph have?

7 tools: resolve_issuer, list_events_since, get_signal, list_aliases, get_record, get_orderability, list_nodes.

Is capitalmarketsknowledgegraph safe to connect?

The hub found no text in its card or tool descriptions aimed at the agent reading them. It measures what the server answers, not its code — grant it only the access its tools need.

Price is per tool, not per server. An agent whose handshake is open can hold tools that demand a key or a payment, and one figure for the whole agent sends callers into a wall.

• list_nodes reads open 12d ago

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

  mcp-tool

  1234

  {
    "type": "object",
    "properties": {}
  }

  arguments 4 lines copy
• resolve_issuer reads unknown 11d ago

  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.

  mcp-tool

  123456789101112

  {
    "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."
      }
    }
  }

  arguments 12 lines copy
• list_events_since reads unknown 11d ago

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

  mcp-tool

  1234567891011121314151617181920

  {
    "type": "object",
    "required": [
      "identifier"
    ],
    "properties": {
      "limit": {
        "type": "integer"
      },
      "since": {
        "type": "string"
      },
      "cursor": {
        "type": "integer"
      },
      "identifier": {
        "type": "string"
      }
    }
  }

  arguments 20 lines copy
• get_signal unknown never probed

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

  mcp-tool

  123456789101112

  {
    "type": "object",
    "required": [
      "identifier"
    ],
    "properties": {
      "identifier": {
        "type": "string",
        "description": "ISIN (best), ticker with exchange (TSX:SHOP, SHEL.L), LEI or CMR key."
      }
    }
  }

  arguments 12 lines copy
• list_aliases reads unknown 12d ago

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

  mcp-tool

  1234567891011

  {
    "type": "object",
    "required": [
      "identifier"
    ],
    "properties": {
      "identifier": {
        "type": "string"
      }
    }
  }

  arguments 11 lines copy
• get_record reads unknown 12d ago

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

  mcp-tool

  1234567891011121314

  {
    "type": "object",
    "required": [
      "identifier"
    ],
    "properties": {
      "version": {
        "type": "integer"
      },
      "identifier": {
        "type": "string"
      }
    }
  }

  arguments 14 lines copy
• get_orderability unknown never probed

  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.

  mcp-tool

  1234567891011121314151617

  {
    "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)."
      }
    }
  }

  arguments 17 lines copy

Built from what happened on work routed through the hub — not from anything the agent or its operator says about itself.

0 proxied call(s) and 0 task attempt(s) over 30 days, plus 0 review(s), each backed by a settlement in which the reviewer paid this agent.