_ registry / a2a + mcp JSONRPC · checked 1h ago

Germany node — Capital Markets Knowledge Graph

https://mcp.de-cm-kg.ai

Registry code: e41b634524c164ee

api record

Read-only door over the Germany node of the Capital Markets Knowledge Graph: Xetra common shares in the German product groups, plus Eurex derivatives reference data as EUREX records linked to their Xetra underlying. 3436 records, 36287 dated, URL-carrying disclosure events over 12 months. Public-record only; no prices, quotes or licensed market data. Records and events are served from germanywestcentral and never leave the jurisdiction.

endpoint
https://mcp.de-cm-kg.ai/mcp
door code
63e6c9285d58a683
protocol
JSONRPC ·0.3
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 Germany node — Capital Markets Knowledge Graph live?
Yes — it answered the hub's last check (checked 1h ago). It answered 100% of checks over the last 30 days.
Is Germany node — Capital Markets Knowledge Graph free to use?
Yes — the hub reached it with no key and no payment.
What tools does Germany node — Capital Markets Knowledge Graph have?
5 tools: Get Capital Markets Record, List disclosure events since a date, Resolve issuer, List sourced aliases, List market nodes.
Is Germany node — Capital Markets Knowledge Graph 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
100%

90 days 100%· all time 100%

latency
110ms

last good check

priced tools
0

of 5 tools

_ answered our checks, 90 days 2 checks · signed record
  • unknown → live
  • unknown → live
_ 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 5 tools
5 never probed 0 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.

  • get_record unknown never probed

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

    capital-marketspublic-recorddemcp

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

    capital-marketspublic-recorddemcp

  • resolve_issuer unknown never probed

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

    capital-marketspublic-recorddemcp

  • list_aliases unknown never probed

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

    capital-marketspublic-recorddemcp

  • list_nodes unknown never probed

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

    capital-marketspublic-recorddemcp

_ try it over a2a 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 e41b634524c164ee.

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

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
0

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

_ 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
2
ok
0
failed
2
success rate
0%
median latency
140ms
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
—

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

_ also on de-cm-kg.ai 1 entry

Served from the same domain, which is what was measured. Not a claim that one owner runs them: ownership is what a passport proves, and each of these says for itself.