Remote MCP · Endpoint

Edge Case Museum MCP server

No. Edge Case Museum answered an MCP handshake 42 minutes ago.

UpLast checked 42 minutes ago

Server URL

https://gateway.pipeworx.io/edge-case-museum/mcp

The last check completed an MCP handshake.

Registry name
io.github.pipeworx-io/edge-case-museum
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
71 ms
Tools exposed
48 tools
Uptime, last 30 days
100% from 14 checks
Described by its publisher as
Edge Case Museum MCP — 'Your code works. Except for these wonderfully terrible inputs.'
Listing
From the official MCP registry (active).
Recent checks of Edge Case Museum
CheckedResultHandshake
42 minutes agoHandshake completed71 ms
9 days agoHandshake completed109 ms
10 days agoHandshake completed99 ms
11 days agoHandshake completed87 ms
12 days agoHandshake completed65 ms
14 days agoHandshake completed94 ms
14 days agoHandshake completed110 ms
15 days agoHandshake completed96 ms
17 days agoHandshake completed527 ms
19 days agoHandshake completed162 ms
21 days agoHandshake completed77 ms
24 days agoHandshake completed92 ms
26 days agoHandshake completed48 ms
28 days agoHandshake completed90 ms

The last 14 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 Edge Case Museum and makes no claim about it beyond what these checks measured.