Remote MCP · Endpoint

io.github.terradev-cloud/prism MCP server

No. io.github.terradev-cloud/prism answered an MCP handshake 1 hour ago.

UpLast checked 1 hour ago

Server URL

https://prism-mcp.terradev.cloud/mcp

The last check completed an MCP handshake.

Registry name
io.github.terradev-cloud/prism
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
30 ms
Tools exposed
3 tools
Uptime, last 30 days
100% from 15 checks
Described by its publisher as
Stateless MCP gateway and OTel span-streaming bridge for hosted MCP servers.
Listing
From the official MCP registry (active).
Recent checks of io.github.terradev-cloud/prism
CheckedResultHandshake
1 hour agoHandshake completed30 ms
2 days agoHandshake completed26 ms
4 days agoHandshake completed37 ms
6 days agoHandshake completed54 ms
8 days agoHandshake completed120 ms
10 days agoHandshake completed40 ms
11 days agoHandshake completed31 ms
13 days agoHandshake completed29 ms
14 days agoHandshake completed26 ms
15 days agoHandshake completed26 ms
18 days agoHandshake completed28 ms
19 days agoHandshake completed20 ms
21 days agoHandshake completed22 ms
22 days agoHandshake completed27 ms
23 days agoHandshake completed24 ms

The last 15 checks. Full history is kept for 30 days; the all-time counter stands at 15 responding of 15.

How to read this

  • ·Handshake latency is one measurement from one probe, from our infrastructure. It is a smoke signal about the endpoint, not a benchmark of your own connection to it.
  • ·An authentication challenge counts as responding. A hosted server that refuses an anonymous prober is behaving correctly.
  • ·A tool count of “behind credentials” means the handshake worked but listing tools needed a token we do not hold.
  • ·Uptime covers the last 30 days of our own checks, at most one an hour, and says how many checks it is drawn from.

Listing data comes from the official MCP registry. Glide is not affiliated with io.github.terradev-cloud/prism and makes no claim about it beyond what these checks measured.