_ registry / a2a + mcp streamable-http · checked 45d ago

Agentic Registries for AI agents — who may call, and what they did

https://agentic-registries.ai

Registry code: b4ce3d0d90f55946

api record

Registries is the security and confirms layer: which agents are known to the estate — identity, the Agent Card they present, what they are licensed to read, which nodes, until when, revoked or not — and the signed record of what they did: CMR signing, attestations, receipts. Twelve doors, one list. Registered once, known in every market.

endpoint
https://mcp.getissuer.ai/mcp
door code
075efa6289f81b0a
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 it live, free and safe measured by this hub
Is Agentic Registries for AI agents — who may call, and what they did live?
Yes — it answered the hub's last check (checked 45d ago). It answered 100% of checks over the last 30 days.
Is Agentic Registries for AI agents — who may call, and what they did free to use?
Yes — the hub reached it with no key and no payment.
What tools does Agentic Registries for AI agents — who may call, and what they did have?
6 tools: resolve_issuer, list_aliases, get_signal, list_events_since, get_record, list_nodes.
Is Agentic Registries for AI agents — who may call, and what they did 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.
reachable
live
uptime, 30 days
99.6%

90 days 99.8%· all time 100%

latency
42ms

last good check

priced tools
0

of 6 tools

_ answered our checks, 90 days 599 checks · signed record
  • degraded → live
  • live → degraded· timeout after 20000ms
  • degraded → live
_ what it is for
topic
finance & markets company & filings
used for
  • resolve a listed company by ticker or isin
  • get a company's capital markets record
  • list disclosure events for an issuer
  • list former names of a company
takes → gives
text → data
_ usage and payments 30 days

Calls placed through this hub's router, from its own receipts. Every caller and every payer counts the same; the chain total is counted from three payers.

accounts
0

through this hub

calls served
0

successful

paid through this hub
0 USDC

what callers paid

_ what it can do 6 tools
1 open 5 never probed 1 of 6 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 45d ago

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

    mcp-tool

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

    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

    {
  "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
  • list_aliases unknown never probed

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

    mcp-tool

    {
  "type": "object",
  "required": [
    "identifier"
  ],
  "properties": {
    "identifier": {
      "type": "string"
    }
  }
}
    arguments 11 lines
  • 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), ACM-300 CONDITIONAL (a bare ticker names more than one issuer: add the exchange), ACM-000 NOT APPLICABLE (a GTIN: ask gtinfetch.ai), ACM-500 SYSTEM ERROR (the home node did not answer). 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

    {
  "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
  • list_events_since unknown never probed

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

    mcp-tool

    {
  "type": "object",
  "required": [
    "identifier"
  ],
  "properties": {
    "limit": {
      "type": "integer"
    },
    "since": {
      "type": "string"
    },
    "cursor": {
      "type": "integer"
    },
    "identifier": {
      "type": "string"
    }
  }
}
    arguments 20 lines
  • get_record unknown never probed

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

    mcp-tool

    {
  "type": "object",
  "required": [
    "identifier"
  ],
  "properties": {
    "version": {
      "type": "integer"
    },
    "identifier": {
      "type": "string"
    }
  }
}
    arguments 14 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 agent card — 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 b4ce3d0d90f55946.

Every step, filled in for this listing: https://brick.blue/api/v1/agents/b4ce3d0d90f55946/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/b4ce3d0d90f55946/badge.svg)](https://brick.blue/agent/b4ce3d0d90f55946?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 a2a door
card completeness
87%

How much of the published card is filled in. Not a judgement of the agent — a measure of what it told the world about itself.

spec deviations
1

Places where the published card departs from the specification. Recorded rather than hidden, and counted against every agent the same way.

  • supportedInterfaces[0].protocolBinding missing
_ 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.