Skip to content

com.geiant/mcp-agentcore

by geiant.com · remote · no sign-in to list tools · v0.1.0 · published by com.geiant

AI governance MCP server for EU AI Act compliance and jurisdiction verification

Final · 1Changes · 2
CompareRegistry entry

3 tools: 1 do something that can't be undone and 2 change things.

Scanned Oct 21, 2026

No check matched anything in the tool definitions. No finding is not a safety guarantee. How the checks work.

claude mcp add --transport http agentcore https://geiant-agentcore-production.up.railway.app/mcp

Tools

Open a tool for its reasons and full description. Descriptions are the publisher's own words, shown as they are.

3 tools

Can't be undone 1Claude Code: ask
  • generate_audit_proofGenerate a EU AI Act Art.No findings

    Why it is in this group

    • The name "generate_audit_proof" says "generate": a word for a change.
    • The input addresses people (input.to): what it sends cannot be taken back.
    Description, as the server wrote it
    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.
Changes things 2Claude Code: ask
  • check_delegation_chainVerify the human → agent delegation chain and check whether a specific tool is whitelisted for this agent.No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    Description, as the server wrote it
    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.
  • verify_jurisdictionVerify that an AI agent is authorized to operate in a specific H3 territorial cell.No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    Description, as the server wrote it
    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.

This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.

Install

Pinned to version 0.1.0. Values in angle brackets are yours to fill in.

claude mcp add --transport http agentcore https://geiant-agentcore-production.up.railway.app/mcp

Run in a terminal.

Claude Code permissions

Allow the reads, ask before a change, deny the deletes. Paste into .claude/settings.json.

.claude/settings.json
{
  "permissions": {
    "allow": [],
    "ask": [
      "mcp__agentcore__verify_jurisdiction",
      "mcp__agentcore__generate_audit_proof",
      "mcp__agentcore__check_delegation_chain"
    ],
    "deny": []
  }
}

Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. It assumes the server is installed as agentcore. Review it before you use it.