A remote AI-governance server that lets an assistant verify agent jurisdiction, check human-to-agent delegation chains, and produce EU AI Act audit evidence.
What you can do
Verify whether an AI agent is authorized to operate in a specific H3 territorial cell, including delegation certificate signature, time bounds, cell and facet authorization, with a structured allow-or-deny result. Check the human-to-agent delegation chain, returning principal identity, delegation depth, certificate validity and whether a specific tool is whitelisted. Generate an EU AI Act Article 12 and Article 14 compliance evidence bundle with the cryptographic audit chain, Merkle epoch roots, delegation certificate, trust score and violation history.
When to use it
Useful when an assistant must gate agent actions on jurisdiction or delegation checks, or when you need regulator-ready EU AI Act record-keeping and human-oversight evidence for AI agent activity.
Requirements
A remote streamable HTTP endpoint; no packages, environment variables or headers are declared. The manifest declares no authentication, so check whether the endpoint expects credentials before relying on it.
Before you install
The server returns compliance and audit evidence, including trust scores and violation history, so treat its output as authoritative only after independent validation. No authentication is declared, so anyone reaching the endpoint may be able to call it; confirm access control before sending sensitive agent or identity data.
Enable the server for the chats that should use its tools.
Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.
Use with an agent
Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.
Read https://sourceweft.com/mcp/com.geiant%2Fmcp-agentcore/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.
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.
Parametersfaceth3_cellrequiredagent_pk
generate_audit_proof
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.
Parameterstofromagent_pk
check_delegation_chain
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.
Parametersagent_pktool_namerequired
Version history
1
v0.1.0LatestSep 16, 2026
Score
75%
75% of the applicable checks met
How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.
Reached in the last 30 daysRequired25 pts
Auth declaredRequired10 pts
Tools listedRequired15 pts
DescriptionRequired15 pts
Logo10 pts
Documentation15 pts
Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.
License10 pts
Declare a license in the repository or the registry entry.