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

Agentic RADAR for AI agents — the estate numbers

https://agentic-radar.ai

Registry code: f90cbcce33b307cc

api record

RADAR is Allooloo’s published analytics across its agentic stack: records and events per node, the sovereign zones, Issuerwire, door response times, agent calls per door, sweep motion, provenance coverage, residency, registry state, machine surfaces and paid calls settled. Every figure is a door, a log or a ledger; nothing is quoted from a third party. radar.json beside it, free, no registration.

endpoint
https://mcp.getissuer.ai/mcp
door code
21f48ad0f8a1e8d9
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 RADAR for AI agents — the estate numbers live?
Yes — it answered the hub's last check (checked 45d ago). It answered 100% of checks over the last 30 days.
Is Agentic RADAR for AI agents — the estate numbers free to use?
Yes — the hub reached it with no key and no payment.
What tools does Agentic RADAR for AI agents — the estate numbers have?
7 tools: list_aliases, resolve_issuer, get_record, get_orderability, get_signal, list_events_since, list_nodes.
Is Agentic RADAR for AI agents — the estate numbers 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.7%

90 days 99.3%· all time 100%

latency
28ms

last good check

priced tools
0

of 7 tools

_ answered our checks, 90 days 576 checks · signed record
  • degraded → live
  • live → degraded· timeout after 20000ms
  • degraded → live
  • degraded → live
  • live → degraded· timeout after 20000ms
_ 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, and USDC settlements on base into the address this listing's priced doors name, read off the chain. Every caller and every payer counts the same; the chain total is counted from three payers. The address also stands behind 21 other origins: the chain figures are the gateway's, not this listing's alone. How it is counted.

accounts
0

through this hub

calls served
0

successful

paid through this hub
0 USDC

what callers paid

payers on base
14

distinct

settlements
103

last 2026-11-09

received on chain
1.03 USDC

shared-payto

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

    {
  "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
  • 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

    {
  "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
_ 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 f90cbcce33b307cc.

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