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-perception

REMOTE · PACKAGESMCP-PERCEPTION-PRODUCTION.UP.RAILWAY.APP · SCANNED SEP 23

Geospatial AI MCP server — satellite imagery, embeddings, weather, GNS governance

0 this week 73 Trust /100
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 Usability48
  • 0% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Fail
  • AI-judged instruction clarity (good).Pass
  • Tool/resource definitions use about 802 tokens (~89/item across 9 items; 8 tools + 1 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 8 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 9 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
  • Supports UI / widget rendering.Pass
Install

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

com.geiant/mcp-perception is a hosted endpoint at https://packagesmcp-perception-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 · packagesmcp-perception-production.up.railway.app

# add to Claude Code
claude mcp add --transport http com-geiant-mcp-perception 'https://packagesmcp-perception-production.up.railway.app/mcp'
// .cursor/mcp.json
{
  "mcpServers": {
    "com-geiant-mcp-perception": {
      "url": "https://packagesmcp-perception-production.up.railway.app/mcp"
    }
  }
}
// .vscode/mcp.json
{
  "servers": {
    "com-geiant-mcp-perception": {
      "type": "http",
      "url": "https://packagesmcp-perception-production.up.railway.app/mcp"
    }
  }
}
# ~/.codex/config.toml
[mcp_servers.com-geiant-mcp-perception]
url = "https://packagesmcp-perception-production.up.railway.app/mcp"
// opencode.json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "com-geiant-mcp-perception": {
      "type": "remote",
      "url": "https://packagesmcp-perception-production.up.railway.app/mcp",
      "enabled": true
    }
  }
}
# add to OpenClaw
openclaw mcp add com-geiant-mcp-perception --url 'https://packagesmcp-perception-production.up.railway.app/mcp' --transport streamable-http
# ~/.hermes/config.yaml
mcp_servers:
  com-geiant-mcp-perception:
    url: "https://packagesmcp-perception-production.up.railway.app/mcp"
// ~/.netclaw/config/netclaw.json
{
  "McpServers": {
    "com-geiant-mcp-perception": {
      "Transport": "http",
      "Url": "https://packagesmcp-perception-production.up.railway.app/mcp"
    }
  }
}
# add to Vellum
assistant mcp add com-geiant-mcp-perception -t streamable-http -u 'https://packagesmcp-perception-production.up.railway.app/mcp'
// mcp.json
{
  "mcpServers": {
    "com-geiant-mcp-perception": {
      "type": "http",
      "url": "https://packagesmcp-perception-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.

  • 26 Aug 26 +1
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 25 Aug 26 72
    • Stability: 0.97 → pass security
  • 11 Aug 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
  • 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
  • 30 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
  • 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 0

    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 23 Sept 2026 · Probed https://packagesmcp-perception-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

Background: What to check on a remote MCP endpoint →

DNSSEC insecure

Validation of packagesmcp-perception-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

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

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://packagesmcp-perception-production.up.railway.app/mcp Verified 200
http (plaintext) http://packagesmcp-perception-production.up.railway.app/mcp HTTPS enforced 301 https://packagesmcp-perception-production.up.railway.app/mcp
MCP tools · 8 exposed · ~795 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
gns_get_compliance_report ~69

Returns a full EU AI Act compliance report for a GNS agent, including trust score, chain verification, Merkle epoch proofs, delegation certificate, and regulatory status.

NameTypeReqDescription
agentHandlestringGNS handle of the agent (e.g. energy@italy-geiant)

No output schema declared.

No examples provided.

gns_get_trust_score ~88

Get the current TierGate trust tier and score for an agent. Tiers: provisioned (0%) → observed (25%) → trusted (60%) → certified (85%) → sovereign (99%). Omit agent_pk to query the server's own agent.

NameTypeReqDescription
agent_pkstringEd25519 public key (64 hex chars). Omit for own agent.

No output schema declared.

No examples provided.

gns_roll_epoch ~59

Roll all pending breadcrumbs into a new sealed epoch with a Merkle root. Returns { epoch_index, merkle_root, block_count, epoch_hash }. Call this at the end of a session to produce a tamper-evident compliance snapshot.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

gns_verify_chain ~75

Verify the cryptographic integrity of an agent's breadcrumb chain. Returns { is_valid, block_count, issues[] } plus epoch Merkle roots. A valid chain proves no audit records have been tampered with.

NameTypeReqDescription
agent_pkstringEd25519 public key (64 hex chars). Omit for own agent.

No output schema declared.

No examples provided.

perception_classify ~181

Run Prithvi-EO-2.0-300M-TL-Sen1Floods11 flood classification on a Sentinel-2 tile previously fetched by perception_fetch_tile. Sends the 6-band chip to a RunPod endpoint and returns: dominant_class, flood_pixel_pct, confidence, class_counts, and the full perception_chain. The perception chain is written to Spatial Memory and a signed audit breadcrumb is dropped to the agent trail.

NameTypeReqDescription
h3_cellstringOverride H3 cell. Defaults to the cell from the original fetch.
taskstringyesClassification task. Currently only "flood" is supported.
tile_idstringyestile_id from perception_fetch_tile result (must be in session cache).
write_to_spatial_memorybooleanWrite perception chain to geiant_geometry_state. Default: true.

No output schema declared.

No examples provided.

perception_embed ~46

[Sub-phase 4.2 — NOT YET IMPLEMENTED] Will generate Clay v1.5 embeddings.

NameTypeReqDescription
tile_idstringyestile_id from perception_fetch_tile result

No output schema declared.

No examples provided.

perception_fetch_tile ~173

Fetch the least-cloudy Sentinel-2 L2A tile covering a given H3 cell from Microsoft Planetary Computer. Returns signed COG band URLs for all 6 Prithvi/Clay spectral bands (B02 Blue, B03 Green, B04 Red, B8A NIR, B11 SWIR1, B12 SWIR2), plus tile metadata. The tile is cached in memory for subsequent perception_classify or perception_embed calls.

NameTypeReqDescription
days_backnumberDays to search back. Default: 30.
h3_cellstringyesH3 cell ID at any resolution.
max_cloud_covernumberMax cloud cover %. Default: 20.
timestampstringISO 8601 datetime. Search back from this point. Defaults to now.

No output schema declared.

No examples provided.

perception_weather ~104

Query atmospheric conditions for an H3 cell at a given timestamp from Open-Meteo ERA5. Returns wind, precipitation, temperature. Writes to Spatial Memory and drops a signed audit breadcrumb.

NameTypeReqDescription
h3_cellstringyesH3 cell ID at any resolution.
timestampstringISO 8601 datetime for weather lookup. Defaults to now.
write_to_spatial_memorybooleanWrite weather context to geiant_geometry_state. Default: true.

No output schema declared.

No examples provided.

Common questions

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

com.geiant/mcp-perception is listed in the public MCP registry as com.geiant/mcp-perception. Geospatial AI MCP server, satellite imagery, embeddings, weather, GNS governance. This page covers its hosted endpoint (https://packagesmcp-perception-production.up.railway.app/mcp).

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

com.geiant/mcp-perception scores 73 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-perception server expose?

com.geiant/mcp-perception exposes 8 tools: perception_fetch_tile, perception_classify, perception_embed, perception_weather, gns_get_trust_score, and 3 more. Their descriptions and schemas cost roughly 795 tokens of context every time the server is loaded.

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

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

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

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