Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, email [email protected] and we’ll put it right.

com.geiant/mcp-agentcore

REMOTE · GEIANT-AGENTCORE-PRODUCTION.UP.RAILWAY.APP · SCANNED AUG 3

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

+3 this week 67 Trust /100
Trust breakdown (6 categories)

How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score →

Endpoint Security57
Transport & Reachability100
Schema Quality & AI Usability77
  • AI-judged instruction clarity (excellent).Pass
  • Tool/resource definitions use about 350 tokens (~116/item across 3 items; 3 tools + 0 resources), lean.Pass
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management27
  • Stability observed for 8 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 100% of tool parameters carry a description.Pass
Capabilities100
  • Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Install

Add this component to your MCP client. Where a client-specific snippet is available, pick your client below and copy it straight into your config; otherwise use the connection detail shown.

remote · geiant-agentcore-production.up.railway.app

# add to Claude Code
claude mcp add --transport http com-geiant-mcp-agentcore https://geiant-agentcore-production.up.railway.app/mcp
# ~/.codex/config.toml
[mcp_servers.com-geiant-mcp-agentcore]
url = "https://geiant-agentcore-production.up.railway.app/mcp"
// opencode.json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "com-geiant-mcp-agentcore": {
      "type": "remote",
      "url": "https://geiant-agentcore-production.up.railway.app/mcp",
      "enabled": true
    }
  }
}
# add to OpenClaw
openclaw mcp add com-geiant-mcp-agentcore --url https://geiant-agentcore-production.up.railway.app/mcp --transport streamable-http
# ~/.hermes/config.yaml
mcp_servers:
  com-geiant-mcp-agentcore:
    url: "https://geiant-agentcore-production.up.railway.app/mcp"
// mcp.json
{
  "mcpServers": {
    "com-geiant-mcp-agentcore": {
      "type": "http",
      "url": "https://geiant-agentcore-production.up.railway.app/mcp"
    }
  }
}

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

Changelog

Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.

  • 2 Aug 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 20 to 23. That category is still filling its 30-day observation window: 6 days of observed history at the previous scan, 7 at this one. The score rises as the window fills, whether or not the server changes.

  • 31 Jul 26 0
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 29 Jul 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 7 to 10. That category is still filling its 30-day observation window: 2 days of observed history at the previous scan, 3 at this one. The score rises as the window fills, whether or not the server changes.

  • 28 Jul 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 3 to 7. That category is still filling its 30-day observation window: 1 days of observed history at the previous scan, 2 at this one. The score rises as the window fills, whether or not the server changes.

  • 27 Jul 26 0
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 26 Jul 26 64

    First indexed and scored.

Diagnostics

Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.

Captured 3 Aug 2026 · Probed https://geiant-agentcore-production.up.railway.app/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=*.up.railway.app CN=YE1,O=Let's Encrypt,C=US 29 Jul 2026 27 Oct 2026 ECDSA 256 ECDSA-SHA384 6da79bb561da3efeb0e751ca21abd3999fe
SANs: *.up.railway.app, up.railway.app
CN=YE1,O=Let's Encrypt,C=US (CA) CN=Root YE,O=ISRG,C=US 3 Sept 2025 2 Sept 2028 ECDSA 384 ECDSA-SHA384 5ddd70dd31f801c85c186a7a04b80afe
CN=Root YE,O=ISRG,C=US (CA) CN=ISRG Root X2,O=Internet Security Research Group,C=US 13 May 2026 2 Sept 2032 ECDSA 384 ECDSA-SHA384 872165fc34b6e5fba8add5b3705fb53a
CN=ISRG Root X2,O=Internet Security Research Group,C=US (CA) CN=ISRG Root X1,O=Internet Security Research Group,C=US 13 May 2026 2 Sept 2032 ECDSA 384 SHA256-RSA 6c8f1dc727c7117f7baf853ac980f9cd
DNSSEC insecure

Validation of geiant-agentcore-production.up.railway.app. Not signed

Zone DS Keys Algorithms Outcome
. trust_anchor 20326, 38696 8, 8 Verified
app. present 23684 8 Verified
railway.app. absent Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation
Authentication No authorisation required

The endpoint answered without asking for a token. Anyone who knows the URL can reach it.

Result No authorisation required
HTTP status 200
Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://geiant-agentcore-production.up.railway.app/mcp Verified 200
http (plaintext) http://geiant-agentcore-production.up.railway.app/mcp HTTPS enforced 301 https://geiant-agentcore-production.up.railway.app/mcp
MCP tools — 3 exposed · ~350 tokens

The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability.

Tool Tokens
check_delegation_chain ~96

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.

NameTypeReqDescription
agent_pkstringAgent Ed25519 public key (64 hex chars)
tool_namestringyesName of the tool the agent intends to call

No output schema declared.

No examples provided.

generate_audit_proof ~135

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.

NameTypeReqDescription
agent_pkstringAgent Ed25519 public key (64 hex chars)
fromstringISO 8601 start of reporting period
tostringISO 8601 end of reporting period

No output schema declared.

No examples provided.

verify_jurisdiction ~119

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.

NameTypeReqDescription
agent_pkstringAgent Ed25519 public key (64 hex chars)
facetstringFacet to check (e.g. "energy@italy-geiant")
h3_cellstringyesH3 cell index representing the operation territory

No output schema declared.

No examples provided.