GEIANT AgentCore MCP Server

Installation

Clone the repository, install dependencies, and build the server:

• git clone https://github.com/GNS-Foundation/geiant
• cd geiant/packages/mcp-agentcore
• npm install
• npm run build

Start

Run the compiled server locally:

• npm start

Deployment

Deploy to AWS AgentCore Runtime with the documented CLI flow:

• npm install -g @aws/agentcore
• agentcore init --protocol mcp
• agentcore deploy

Configuration

The server reads the following runtime environment variables:

• PORT default 8000 - Binds the HTTP server on 0.0.0.0:$PORT and serves POST /mcp and GET /health.
• COMPLIANCE_URL default https://packagesmcp-perception-production.up.railway.app - Base URL for compliance lookups used by generate_audit_proof.
• GEIANT_DELEGATION_CERT - JSON string containing the delegation certificate loaded at startup. If omitted, jurisdiction checks are limited.

Capabilities

• verify_jurisdiction checks H3 territory, facet scope, certificate validity, and signature state.
• generate_audit_proof returns a compliance evidence bundle with audit chain, epoch roots, delegation certificate, trust score, and violation history.
• check_delegation_chain verifies the human-to-agent delegation chain and tool whitelist.
• HTTP endpoints include POST /mcp, GET /mcp, DELETE /mcp, and GET /health.

Limitations

• The server is streamable HTTP on /mcp and is not a stdio MCP server.
• Without GEIANT_DELEGATION_CERT, authorization responses fail closed or return limited results.
• The compliance evidence flow depends on the external compliance service configured by COMPLIANCE_URL.
• AgentCore deployment expects the runtime to listen on port 8000 by default.