Remote MCP · Endpoint

NotWorking MCP server

No. NotWorking answered an MCP handshake 1 hour ago.

UpLast checked 1 hour ago

Server URL

https://notworking.io/mcp

The last check completed an MCP handshake.

Registry name
io.notworking/notworking
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
659 ms
Tools exposed
2 tools
Uptime, last 30 days
100% from 14 checks
Described by its publisher as
Downdetector for AI agents: stop paying for retries that can't succeed. Check once, then report.
Listing
From the official MCP registry (active).
Recent checks of NotWorking
CheckedResultHandshake
1 hour agoHandshake completed659 ms
9 hours agoHandshake completed684 ms
1 day agoHandshake completed649 ms
2 days agoHandshake completed738 ms
4 days agoHandshake completed660 ms
7 days agoHandshake completed642 ms
9 days agoHandshake completed652 ms
11 days agoHandshake completed742 ms
14 days agoHandshake completed741 ms
16 days agoHandshake completed700 ms
18 days agoHandshake completed692 ms
20 days agoHandshake completed695 ms
22 days agoHandshake completed780 ms
23 days agoHandshake completed763 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 NotWorking and makes no claim about it beyond what these checks measured.