Remote MCP · Endpoint

Whisper MCP server

No. Whisper answered an MCP handshake 2 hours ago.

UpLast checked 2 hours ago

Server URL

https://whisper.online/mcp

The last check completed an MCP handshake.

Registry name
io.github.whisper-sec/whisper
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
301 ms
Tools exposed
17 tools
Uptime, last 30 days
100% from 16 checks
Described by its publisher as
One routable IPv6 per AI agent, verifiable from the DNS root. Keyless tools need no signup.
Listing
From the official MCP registry (active).
Recent checks of Whisper
CheckedResultHandshake
2 hours agoHandshake completed301 ms
2 days agoHandshake completed271 ms
4 days agoHandshake completed274 ms
5 days agoHandshake completed273 ms
7 days agoHandshake completed279 ms
8 days agoHandshake completed277 ms
9 days agoHandshake completed270 ms
12 days agoHandshake completed277 ms
14 days agoHandshake completed271 ms
15 days agoHandshake completed275 ms
17 days agoHandshake completed271 ms
18 days agoHandshake completed283 ms
19 days agoHandshake completed270 ms
20 days agoHandshake completed280 ms
20 days agoHandshake completed272 ms
21 days agoHandshake completed287 ms

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

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 Whisper and makes no claim about it beyond what these checks measured.