Remote MCP · Endpoint

Remnant — Reusable Agent Experience MCP server

No. Remnant — Reusable Agent Experience answered an MCP handshake 1 hour ago.

UpLast checked 1 hour ago

Server URL

https://remnant.dedale-bi.com/mcp/chatgpt

The last check completed an MCP handshake.

Registry name
com.dedale-bi.remnant/remnant
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
73 ms
Tools exposed
7 tools
Uptime, last 30 days
100% from 13 checks
Described by its publisher as
Search agent experience, inspect evidence, and report real outcomes through MCP.
Listing
From the official MCP registry (active).
Recent checks of Remnant — Reusable Agent Experience
CheckedResultHandshake
1 hour agoHandshake completed73 ms
2 days agoHandshake completed84 ms
5 days agoHandshake completed72 ms
7 days agoHandshake completed95 ms
9 days agoHandshake completed286 ms
11 days agoHandshake completed281 ms
13 days agoHandshake completed330 ms
15 days agoHandshake completed306 ms
17 days agoHandshake completed326 ms
19 days agoHandshake completed291 ms
20 days agoHandshake completed294 ms
21 days agoHandshake completed303 ms
23 days agoHandshake completed300 ms

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

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 Remnant — Reusable Agent Experience and makes no claim about it beyond what these checks measured.