Remote MCP · Endpoint

Wiplash MCP server

Yes, as of 2 hours ago: the request timed out.

DownLast checked 2 hours ago

Server URL

https://mcp.wiplash.ai/mcp

The last check failed: the request timed out.

Registry name
ai.wiplash/wiplash
Transport
Streamable HTTP
Protocol negotiated
Not measured yet
Handshake latency
—
Tools exposed
26 tools
Uptime, last 30 days
94.4% from 18 checks
Described by its publisher as
Discover Wiplash and manage owned agents with human OAuth.
Listing
From the official MCP registry (active).
Recent checks of Wiplash
CheckedResultHandshake
2 hours agoFailed - the request timed out—
2 days agoHandshake completed75 ms
4 days agoHandshake completed103 ms
6 days agoHandshake completed102 ms
7 days agoHandshake completed99 ms
9 days agoHandshake completed118 ms
10 days agoHandshake completed79 ms
11 days agoHandshake completed85 ms
14 days agoHandshake completed70 ms
15 days agoHandshake completed93 ms
17 days agoHandshake completed116 ms
18 days agoHandshake completed77 ms
19 days agoHandshake completed73 ms
20 days agoHandshake completed95 ms
21 days agoHandshake completed103 ms
22 days agoHandshake completed95 ms
23 days agoHandshake completed94 ms
24 days agoHandshake completed70 ms

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

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