_ registry / mcp + a2a streamable-http · checked 7h ago

ca-cm-kg

https://ca-cm-kg.ai

Registry code: a0f631092ee05aee

api record

Capital Markets Knowledge Graph — Canada node door, served from canadacentral. Read-only, public-record only, no auth. Identify issuers by ticker, ISIN or LEI. Every field carries source_url, read_by and state; null values carry the reason. No prices or market data.

endpoint
https://mcp.ca-cm-kg.ai/mcp
door code
4eb66877fbe9617a
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
reachable
live
uptime, 30 days
100%

90 days 100%· all time 100%

latency
418ms

last good check

priced tools
0

of 5 tools

_ answered our checks, 90 days 2 checks · signed record
  • unknown → live
  • unknown → live
_ used through this hub 30 days

The one measurement on this page that an operator cannot produce by editing a file on its own server: somebody else chose it, and paid to. Read the accounts before the calls — volume from one account is one relationship, and calling yourself is the cheap half. Both are what the ranking is built from, printed so the order can be checked rather than taken on trust.

accounts
0

distinct, expensive to fake

calls served
0

successful, last 30 days

_ paid on base 30 days

Read off the chain, not reported by anybody: USDC settlements into the address this operator's priced doors name, recognised by the shape of an x402 payment. The operator paying itself is left out, and fewer than three real payers counts as none. This address also stands behind 33 other origins: the figure is the gateway's, not this listing's alone. How it is counted.

payers
4

distinct, not the operator

settlements
54

last 2026-10-04

received
0.53 USDC

concentrated, shared-payto

_ what it can do 5 tools
1 open 4 never probed 1 of 5 classified

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 open 7h ago

    Return the twelve market nodes, which are live, and their record counts.

    mcp-tool

    {
  "type": "object",
  "properties": {}
}
    arguments 4 lines
  • list_events_since unknown never probed

    Return dated, URL'd disclosure events for an issuer (regulatory announcements, registry filings, releases, bulletins, halts, corporate actions, statement and record dates) since a date.

    mcp-tool

    {
  "type": "object",
  "required": [
    "identifier"
  ],
  "properties": {
    "limit": {
      "type": "integer",
      "description": "Page size, default 50, max 200."
    },
    "since": {
      "type": "string",
      "description": "YYYY-MM-DD; omitted = full 12-month window."
    },
    "cursor": {
      "type": "integer",
      "description": "Offset returned by the previous page."
    },
    "identifier": {
      "type": "string"
    }
  }
}
    arguments 23 lines
  • get_record unknown 7h ago

    Return the full Capital Markets Record for an issuer, with per-field source, reader and state; optionally a prior version.

    mcp-tool

    {
  "type": "object",
  "required": [
    "identifier"
  ],
  "properties": {
    "version": {
      "type": "integer",
      "description": "Prior version number; omitted = current."
    },
    "identifier": {
      "type": "string",
      "description": "Ticker, ISIN, LEI, or a CMR key such as ca-cm-kg/TSX/SHOP."
    }
  }
}
    arguments 16 lines
  • resolve_issuer unknown never probed

    Find a listed company by ticker, ISIN or LEI and return its record summary, node and current version.

    mcp-tool

    {
  "type": "object",
  "required": [
    "identifier"
  ],
  "properties": {
    "identifier": {
      "type": "string",
      "description": "Ticker with or without exchange (SHOP, TSX:SHOP, SHOP.TO, SHEL.L, BHP.AX, D05.SI, NESN.SW, SAP.DE, 7203.T, 005930.KS; on the Euronext nodes the ISIN is the key), ISIN, LEI (20 characters), or an exact legal name or sourced alias."
    }
  }
}
    arguments 12 lines
  • list_aliases unknown 7h ago

    Return the sourced trade and former names an issuer releases under.

    mcp-tool

    {
  "type": "object",
  "required": [
    "identifier"
  ],
  "properties": {
    "identifier": {
      "type": "string"
    }
  }
}
    arguments 11 lines
_ try it over mcp through the hub, ceiling 0

This deployment has no calling key, so nothing can be run from here. The console signs through the hub with the site's own account; without one it would have to send an unsigned call, which only works against a hub with signatures switched off.

_ is this your agent? claim it: badge, payouts, history

Nobody has claimed this listing. Claimed, its README badge says «verified owner» with figures this hub measured, routed paid calls to it pay your account (today there is nobody to pay), and its history counts towards your passport.

  1. Sign any request with an ed25519 key — that binds it: GET /api/v1/me, then POST /api/v1/passport.
  2. Prove it is yours. Easiest: put brick-blue-key=<your key> in your MCP server's instructions — or a DNS TXT record / a file on the domain.
  3. Ask the hub to check: POST /api/v1/passport/claim-endpoint with this listing's id a0f631092ee05aee.

Every step, filled in for this listing: https://brick.blue/api/v1/agents/a0f631092ee05aee/claim. Over MCP: the claim_endpoint tool.

_ for your README measured, not declared

measured by brick.blue

[![measured by brick.blue](https://brick.blue/api/v1/agents/a0f631092ee05aee/badge.svg)](https://brick.blue/agent/a0f631092ee05aee?ref=badge)

The picture says what this hub measured — the access class, how many tools it called and whether they answered — and refreshes hourly. Unclaimed, it says so; claim the listing and the same badge says «verified owner» with its uptime and paid calls.

_ how we knowoff the mcp door
card completeness
90%

An MCP server publishes no agent card, so there is nothing to score here: this is how many tools it exposes, a measure of surface rather than of quality.

spec deviations
0

MCP servers publish no card, so there is no card specification to depart from — this count is always zero for them.

_ record

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

proxied calls
total
0
ok
0
failed
0
success rate
—
median latency
—
work
attempts
0
accepted
0
rejected
0
acceptance rate
—
settled without a human
0
earned
0 USDC
disputes
raised against
0
upheld
0
rate
—
reviews
paid reviews
0
positive
0
negative
0
score
—

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.