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

com.geiant/mcp-agentcore

REMOTE · GEIANT-AGENTCORE-PRODUCTION.UP.RAILWAY.APP

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

0 this week 79 Trust /100

Last scanned (15 hours ago)

Scores higher than 74% of remote servers

Reachable. Last reached 21 Nov 2026.

Category Security

Trust breakdown (7 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 → Why this is hard to score →

Endpoint Security57
Transport & Reachability100
Schema Quality & AI Usability80
  • 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 Management100
  • No destabilizing schema changes in the last 30 days.Pass
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
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 3 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 3 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
  • Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
What we tested

Checks we ran (12)

  • TLS certificate
  • HTTPS
  • HSTS header
  • DNSSEC
  • Transport
  • Schema quality
  • Stability
  • Tool coverage
  • Injection markers
  • Destructive annotations
  • Judged manipulation
  • MCP protocol

Checks we could not complete (1)

These are gaps on our side, not findings about this hosted endpoint. We only credit what we can confirm, so a category made up entirely of them scores 0.

  • Authorization in Endpoint SecurityAuthorisation not fully verified: no authorisation is required to call this server, and 3 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe.

Does not apply to this hosted endpoint (2)

  • Supply Chain SecurityScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
  • Provenance & TransparencyScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.

The score does not measure everything. What the score does not measure →

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.

  • 11 Nov 26 0
    • Stability: 0.97 → pass security
  • 10 Nov 26 0
    • Stability: pass → 0.97 functional
  • 8 Nov 26 0
    • Stability: 0.97 → pass security
  • 7 Nov 26 0
    • Endpoint reachability: unreachable → reachable ▲ functional
    • Stability: pass → 0.97 functional
  • 6 Nov 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
  • 4 Nov 26 0
    • Endpoint reachability: reachable → unreachable ▼ security
    • HSTS header: fail → unverified ▼ security
    • Stability: pass → unverified ▼ security
    • Tool safety: pass → unverified ▼ security
    • TLS certificate: pass → unverified ▼ security
    • Transport: pass → fail ▼ security
    • Authorization: Authorisation not yet verified: we couldn't confirm whether this endpoint requires it. security
    • Capabilities: pass → unverified ▼ functional
    • Tool coverage: 100 → unverified ▼ functional
    • First check of Schema quality: unverified functional
  • 28 Sept 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
  • 25 Sept 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
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 21 Nov 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=YE2,O=Let's Encrypt,C=US 27 Sept 2026 26 Dec 2026 ECDSA 256 ECDSA-SHA384 618edc56941aa1165ddb080bf9f799eb7c1
SANs: *.up.railway.app, up.railway.app
CN=YE2,O=Let's Encrypt,C=US (CA) CN=Root YE,O=ISRG,C=US 3 Sept 2025 2 Sept 2028 ECDSA 384 ECDSA-SHA384 4df3b15dd6c0784c507cd37b58e6f115
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

Background: What to check on a remote MCP endpoint →

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. DS published 23684 8 Verified
railway.app. No DS 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

Background: How OAuth 2.1 works in the 2026 MCP spec →

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. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →

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_pkstring–Agent 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_pkstring–Agent Ed25519 public key (64 hex chars)
fromstring–ISO 8601 start of reporting period
tostring–ISO 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_pkstring–Agent Ed25519 public key (64 hex chars)
facetstring–Facet to check (e.g. "energy@italy-geiant")
h3_cellstringyesH3 cell index representing the operation territory

No output schema declared.

No examples provided.

Install

How do I install the com.geiant/mcp-agentcore server?

com.geiant/mcp-agentcore is a hosted endpoint at https://geiant-agentcore-production.up.railway.app/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

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'
Common questions

What is the com.geiant/mcp-agentcore server?

com.geiant/mcp-agentcore is listed in the public MCP registry as com.geiant/mcp-agentcore. AI governance MCP server for EU AI Act compliance and jurisdiction verification. This page covers its hosted endpoint (https://geiant-agentcore-production.up.railway.app/mcp).

Is the com.geiant/mcp-agentcore server safe to use?

com.geiant/mcp-agentcore scores 79 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

What tools does the com.geiant/mcp-agentcore server expose?

com.geiant/mcp-agentcore exposes 3 tools: verify_jurisdiction, generate_audit_proof, check_delegation_chain. Their descriptions and schemas cost roughly 350 tokens of context every time the server is loaded.

Does the com.geiant/mcp-agentcore server require authentication?

No. We connected to com.geiant/mcp-agentcore without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

Is the com.geiant/mcp-agentcore server still maintained?

com.geiant/mcp-agentcore is still listed as active in the MCP registry. We last reached this channel on 21 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

What did VerifyMCP test on the com.geiant/mcp-agentcore server?

VerifyMCP ran 12 checks on com.geiant/mcp-agentcore, covering TLS certificate, HTTPS, HSTS header, DNSSEC and 8 more. One item could not be completed, a gap on our side rather than a finding about com.geiant/mcp-agentcore: Authorization. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.