Remote MCP · Endpoint

Offline Protocol (hosted) MCP server

No. Offline Protocol (hosted) answered an MCP handshake 1 hour ago.

UpLast checked 1 hour ago

Server URL

https://mcp.offlineprotocol.com/public/mcp

The last check completed an MCP handshake.

Registry name
com.offlineprotocol/hosted
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
266 ms
Tools exposed
15 tools
Uptime, last 30 days
100% from 14 checks
Described by its publisher as
Offline Protocol packages, workflows and integration guides over HTTPS. Read-only.
Listing
From the official MCP registry (active).
Recent checks of Offline Protocol (hosted)
CheckedResultHandshake
1 hour agoHandshake completed266 ms
2 days agoHandshake completed264 ms
4 days agoHandshake completed263 ms
7 days agoHandshake completed437 ms
9 days agoHandshake completed264 ms
11 days agoHandshake completed250 ms
13 days agoHandshake completed266 ms
15 days agoHandshake completed297 ms
16 days agoHandshake completed269 ms
18 days agoHandshake completed255 ms
19 days agoHandshake completed285 ms
20 days agoHandshake completed261 ms
23 days agoHandshake completed283 ms
24 days agoHandshake completed273 ms

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

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 Offline Protocol (hosted) and makes no claim about it beyond what these checks measured.