Remote MCP · Endpoint

Did It Work? MCP server

No. Did It Work? answered an MCP handshake 19 minutes ago.

UpLast checked 19 minutes ago

Server URL

https://api.diditwork.org/mcp

The last check completed an MCP handshake.

Registry name
org.diditwork/did-it-work
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
214 ms
Tools exposed
22 tools
Uptime, last 30 days
100% from 12 checks
Described by its publisher as
Charity evidence for AI agents: cited evaluator figures, caveats and an outcome ledger. Read-only.
Listing
From the official MCP registry (active).
Recent checks of Did It Work?
CheckedResultHandshake
19 minutes agoHandshake completed214 ms
3 days agoHandshake completed158 ms
14 days agoHandshake completed297 ms
14 days agoHandshake completed390 ms
15 days agoHandshake completed563 ms
16 days agoHandshake completed213 ms
18 days agoHandshake completed222 ms
18 days agoHandshake completed214 ms
19 days agoHandshake completed227 ms
21 days agoHandshake completed212 ms
22 days agoHandshake completed245 ms
25 days agoHandshake completed375 ms

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

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

Did It Work? MCP server - status, uptime and latency - Glide