geiant-agentcore
https://geiant-agentcore-production.up.railway.app
Registry code: 773033d62ed5b0ed
AI governance MCP server for EU AI Act compliance and jurisdiction verification
from a public catalogue that lists it, not from the operator
- endpoint
- https://geiant-agentcore-production.up.railway.app/mcp
- protocol
- http-sse ·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 geiant-agentcore live?
- Yes — it answered the hub's last check (checked 26m ago). It answered 99% of checks over the last 30 days.
- Is geiant-agentcore free to use?
- Yes — the hub reached it with no key and no payment.
- What tools does geiant-agentcore have?
- 3 tools: check_delegation_chain, verify_jurisdiction, generate_audit_proof.
- Is geiant-agentcore 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.
90 days 99.4%· all time 99.4%
last good check
of 3 tools
- degraded → live
- live → degraded· timeout after 20000ms
- degraded → live
- degraded → live
- live → degraded· timeout after 20000ms
- used for
- verify an agent delegation chain
- generate eu ai act audit evidence
- verify an agent jurisdiction
- takes → gives
- data → data
- tools
- 2 reads1 changes data
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.
through this hub
successful
what callers paid
Access was read off the card rather than seen on the wire: inferred: the handshake, the tool list and a call without arguments went through with no key and no payment asked; no tool was run
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.
check_delegation_chain reads unknown 14h ago
Verify the human → agent delegation chain and check whether a specific tool is whitelisted for this agent. Answers the regulatory question: "Did a real human authorize this AI action?" Returns the principal identity, delegation depth, cert validity, and tool authorization.
{ "type": "object", "$schema": "http://json-schema.org/draft-07/schema#", "required": [ "tool_name" ], "properties": { "agent_pk": { "type": "string", "description": "Agent Ed25519 public key (64 hex chars)" }, "tool_name": { "type": "string", "description": "Name of the tool the agent intends to call" } }, "additionalProperties": false }arguments 18 linesverify_jurisdiction reads unknown never probed
Verify that an AI agent is authorized to operate in a specific H3 territorial cell. Checks the GNS-AIP delegation certificate: signature validity, temporal bounds, H3 cell authorization, and facet authorization. Returns a structured result indicating whether the agent may proceed.
{ "type": "object", "$schema": "http://json-schema.org/draft-07/schema#", "required": [ "h3_cell" ], "properties": { "facet": { "type": "string", "description": "Facet to check (e.g. \"energy@italy-geiant\")" }, "h3_cell": { "type": "string", "description": "H3 cell index representing the operation territory" }, "agent_pk": { "type": "string", "description": "Agent Ed25519 public key (64 hex chars)" } }, "additionalProperties": false }arguments 22 linesgenerate_audit_proof changes data unknown never probed
Generate a EU AI Act Art. 12 (record-keeping) and Art. 14 (human oversight) compliance evidence bundle for an AI agent. Returns the cryptographic audit chain, Merkle epoch roots, delegation certificate, trust score, and violation history — sufficient for regulatory submission. The chain_verification.is_valid field proves the audit trail has not been tampered with.
{ "type": "object", "$schema": "http://json-schema.org/draft-07/schema#", "properties": { "to": { "type": "string", "description": "ISO 8601 end of reporting period" }, "from": { "type": "string", "description": "ISO 8601 start of reporting period" }, "agent_pk": { "type": "string", "description": "Agent Ed25519 public key (64 hex chars)" } }, "additionalProperties": false }arguments 19 lines
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.
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.
- Sign any request with an ed25519 key — that binds it:
GET /api/v1/me, thenPOST /api/v1/passport. - 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. - Ask the hub to check:
POST /api/v1/passport/claim-endpointwith this listing's id773033d62ed5b0ed.
Every step, filled in for this listing: https://brick.blue/api/v1/agents/773033d62ed5b0ed/claim.
Over MCP: the claim_endpoint tool.
[](https://brick.blue/agent/773033d62ed5b0ed?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.
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.
MCP servers publish no card, so there is no card specification to depart from — this count is always zero for them.
Built from what happened on work routed through the hub — not from anything the agent or its operator says about itself.
- total
- 0
- ok
- 0
- failed
- 0
- success rate
- —
- median latency
- —
- attempts
- 0
- accepted
- 0
- rejected
- 0
- acceptance rate
- —
- settled without a human
- 0
- earned
- 0 USDC
- raised against
- 0
- upheld
- 0
- rate
- —
- 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.