io.github.terradev-cloud/prism
REMOTE · PRISM-MCP.TERRADEV.CLOUD
Stateless MCP gateway and OTel span-streaming bridge for hosted MCP servers.
Available components
Last scanned (10 days ago)
Scores higher than 0% of remote servers
Unreachable for 7 days in a row. Last reached 4 Nov 2026.
Category Monitoring and Observability
Dead
Every channel of this server has been unreachable for long enough to be marked dead. Its trust score is pinned to 0 and does not recover automatically: even once the server responds again it stays dead until it is manually reinstated.
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 Security11
- TLS not yet verified: we couldn't open a connection to check the certificate. View diagnostics → Unverified
- Authorisation not yet verified: we couldn't confirm whether this endpoint requires it. View diagnostics → Unverified
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- HSTS not yet verified: we couldn't read the response headers to check for it. View diagnostics → Unverified
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability0
- Transport check failed: declared streamable-http, but we couldn't connect to verify it. See how to fix → View diagnostics → Fail
Schema Quality & AI Usability0
- Schema not yet verified: we couldn't read the endpoint's schema, or could read only part of its tool list.Unverified
Stability & Change Management0
- Stability not yet verified: not enough scan history yet (needs a 30-day window).Unverified
Tool Coverage0
- Tool coverage not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.Unverified
Tool Safety0
- Tool safety not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.Unverified
Capabilities0
- Capabilities not yet verified: we couldn't read the endpoint's capabilities.Unverified
Unverified: 5 categories
Categories scored 0 because we could not verify them: authentication we do not have, an unreachable endpoint, or not enough scan history. We only credit what we can confirm.
Checks we ran (3)
- HTTPS
- DNSSEC
- Transport
Checks we could not complete (8)
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.
- TLS certificate in Endpoint SecurityTLS not yet verified: we couldn't open a connection to check the certificate.
- Authorization in Endpoint SecurityAuthorisation not yet verified: we couldn't confirm whether this endpoint requires it.
- HSTS header in Endpoint SecurityHSTS not yet verified: we couldn't read the response headers to check for it.
- Schema quality in Schema Quality & AI Usability (scores 0 for this)Schema not yet verified: we couldn't read the endpoint's schema, or could read only part of its tool list.
- Stability in Stability & Change Management (scores 0 for this)Stability not yet verified: not enough scan history yet (needs a 30-day window).
- Tool coverage in Tool Coverage (scores 0 for this)Tool coverage not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.
- Tool safety in Tool Safety (scores 0 for this)Tool safety not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.
- Capabilities in Capabilities (scores 0 for this)Capabilities not yet verified: we couldn't read the endpoint's capabilities.
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 →
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 −17
The score moved with no change recorded against any check. We would rather say so than guess.
- 10 Nov 26 −18
The score moved with no change recorded against any check. We would rather say so than guess.
- 9 Nov 26 −17
The score moved with no change recorded against any check. We would rather say so than guess.
- 8 Nov 26 −18
The score moved with no change recorded against any check. We would rather say so than guess.
- 7 Nov 26 −17
The score moved with no change recorded against any check. We would rather say so than guess.
- 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
- 5 Nov 26 0
- Endpoint reachability: reachable → unreachable ▼ security
- HSTS header: fail → unverified ▼ security
- Stability: pass → unverified ▼ security
- Authorization: partial → unverified ▼ security
- Tool safety: pass → unverified ▼ security
- TLS certificate: pass → unverified ▼ security
- Transport: pass → fail ▼ security
- Capabilities: pass → unverified ▼ functional
- Tool coverage: 100 → unverified ▼ functional
- First check of Schema quality: unverified functional
- 29 Oct 26 +7
- Stability: fail → pass ▲ security
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 11 Nov 2026 · Probed https://prism-mcp.terradev.cloud/mcp
TLS unreached
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of prism-mcp.terradev.cloud. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | Trust anchor | 20326, 38696 | 8, 8 | Verified |
| cloud. | DS published | 7041 | 13 | Verified |
| terradev.cloud. | No DS | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication Inconclusive
We could not reach the endpoint well enough to judge its authorisation posture.
| Result | Inconclusive |
|---|
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://prism-mcp.terradev.cloud/mcp | Unreachable | ||
| http (plaintext) | http://prism-mcp.terradev.cloud/mcp | HTTPS enforced |
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 →
prism_help How to use Prism ~72
Returns connection instructions: how to set the upstream MCP server (X-Prism-Upstream header or ?upstream= query param), the query-param config keys for header-less clients, how destinations and the borrowed-token model work, and example client configs. Start here if you are an agent discovering Prism for the first time.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
prism_info Prism service info ~58
Returns Prism's service identity and runtime state: version, transport, public URL, capture default, and the number of MCP sessions currently being traced. Use this to confirm which Prism deployment you are talking to and whether it is healthy before configuring an upstream.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
prism_ping Liveness check ~69
Returns {"pong": true, "time": <unix seconds>} plus an optional echo of the 'echo' argument. Use to verify connectivity through the gateway before pointing it at an upstream MCP server.
| Name | Type | Req | Description |
|---|---|---|---|
| echo | string | – | Optional string echoed back in the response — useful for confirming round-trip integrity. |
No output schema declared.
No examples provided.
How do I install the io.github.terradev-cloud/prism MCP server?
io.github.terradev-cloud/prism is a hosted endpoint at https://prism-mcp.terradev.cloud/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 · prism-mcp.terradev.cloud
claude mcp add --transport http terradev-cloud-prism 'https://prism-mcp.terradev.cloud/mcp'
What is the io.github.terradev-cloud/prism MCP server?
io.github.terradev-cloud/prism is an MCP server listed in the public MCP registry as io.github.terradev-cloud/prism. Stateless MCP gateway and OTel span-streaming bridge for hosted MCP servers. This page covers its hosted endpoint (https://prism-mcp.terradev.cloud/mcp).
Is the io.github.terradev-cloud/prism MCP server safe to use?
io.github.terradev-cloud/prism scores 0 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 io.github.terradev-cloud/prism MCP server expose?
io.github.terradev-cloud/prism exposes 3 tools: prism_info, prism_ping, prism_help. Their descriptions and schemas cost roughly 199 tokens of context every time the server is loaded.
Does the io.github.terradev-cloud/prism MCP server require authentication?
Its publisher declares no required credentials for io.github.terradev-cloud/prism. We have not been able to confirm that against the live endpoint, and a server can require authorisation without declaring it here.
Is the io.github.terradev-cloud/prism MCP server still maintained?
io.github.terradev-cloud/prism has been unreachable for long enough that we treat it as dead, and its score is pinned to zero. We last reached this channel on 4 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 io.github.terradev-cloud/prism MCP server?
VerifyMCP ran 3 checks on io.github.terradev-cloud/prism, covering HTTPS, DNSSEC and Transport. 8 items could not be completed, a gap on our side rather than a finding about io.github.terradev-cloud/prism: TLS certificate, Authorization, HSTS header, Schema quality and 4 more. 5 categories score 0 for that reason, because we only credit what we can confirm. 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.