Remote MCP · Endpoint

In-band sleeper sentinel MCP server

No. In-band sleeper sentinel answered an MCP handshake 30 minutes ago.

UpLast checked 30 minutes ago

Server URL

https://textforagents.com/products/in-band-sleeper-sentinel/mcp

The last check completed an MCP handshake.

Registry name
com.textforagents/in-band-sleeper-sentinel
Transport
Streamable HTTP
Protocol negotiated
2025-03-26
Handshake latency
63 ms
Tools exposed
2 tools
Uptime, last 30 days
100% from 13 checks
Described by its publisher as
In-band MCP sleeper sentinel — mid-session diff and quarantine inside your own client's session.
Listing
From the official MCP registry (active).
Recent checks of In-band sleeper sentinel
CheckedResultHandshake
30 minutes agoHandshake completed63 ms
3 days agoHandshake completed20 ms
13 days agoHandshake completed15 ms
14 days agoHandshake completed21 ms
15 days agoHandshake completed70 ms
16 days agoHandshake completed76 ms
17 days agoHandshake completed51 ms
18 days agoHandshake completed74 ms
19 days agoHandshake completed45 ms
21 days agoHandshake completed35 ms
23 days agoHandshake completed51 ms
25 days agoHandshake completed41 ms
27 days agoHandshake completed59 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 In-band sleeper sentinel and makes no claim about it beyond what these checks measured.