AI governance MCP server for EU AI Act compliance and jurisdiction verification
Securityv0.1.0streamable-httpgeiant-agentcore-production.up.railway.app repository
| Criterion | Points | Observed |
|---|---|---|
| reachability | 25 / 25 | HTTP 200, initialize accepted in 269ms |
| protocol | 15 / 15 | valid JSON-RPC initialize result, protocolVersion 2025-06-18, serverInfo geiant-agentcore@0.1.0 |
| tooling | 35 / 35 | tools/list OK: 3 tools e.g. "verify_jurisdiction"; 3/3 described, 3/3 fully-typed schemas, median description 281 chars |
| latency | 10 / 10 | initialize round-trip 269ms |
| provenance | 8 / 15 | description present; repository linked; version 0.1.0; namespace com.geiant does NOT match remote host (expected *.geiant.com) |
Score 93/100 · latency 269ms · 3 tools · auth: open
Claude Code:
claude mcp add --transport http mcp-agentcore https://geiant-agentcore-production.up.railway.app/mcp
Generic MCP client config:
{ "mcpServers": { "mcp-agentcore": { "type": "http", "url": "https://geiant-agentcore-production.up.railway.app/mcp" } } }
MCP Queen is a graded index, not a middleman — your agent connects directly to the server above. Check the grade and evidence first; that's the point.
Share this server: permalink https://mcpqueen.com/s/com.geiant/mcp-agentcore · referral link https://mcpqueen.com/go/com.geiant/mcp-agentcore (counts as “routed via the queen”).
Live badge, re-probed continuously — put it in your README:
[](https://mcpqueen.com/s/com.geiant/mcp-agentcore)
Think the grade is wrong? Fix the finding the evidence shows, then the next probe cycle picks it up automatically (full cycle ≈ 3 days) — or open a dispute via the MCP endpoint.
Email alerts when the grade changes or the endpoint stops answering. Double-opt-in, one-click unwatch, free while in beta.
| When (UTC) | Grade | Score | Latency |
|---|---|---|---|
| 2026-07-13 02:00 | A | 93 | 269ms |