Remote MCP · Endpoint

Witness MCP server

Yes, as of 1 hour ago: the server returned an HTTP error.

DownLast checked 1 hour ago

Server URL

https://witness-contractwitness-production.witness-test.workers.dev/mcp

The last check failed: the server returned an HTTP error.

Registry name
io.github.tfitzgerwitness/witness
Transport
Streamable HTTP
Protocol negotiated
Not measured yet
Handshake latency
—
Tools exposed
1 tool
Uptime, last 30 days
83.3% from 18 checks
Described by its publisher as
Production proofs for breaking JSON Schema/MCP changes; UNKNOWN/NO_WITNESS_FOUND not compatible.
Listing
From the official MCP registry (active).
Recent checks of Witness
CheckedResultHandshake
1 hour agoFailed - the server returned an HTTP error—
1 day agoFailed - the server returned an HTTP error—
2 days agoFailed - the server returned an HTTP error—
3 days agoHandshake completed437 ms
4 days agoHandshake completed503 ms
5 days agoHandshake completed305 ms
6 days agoHandshake completed423 ms
9 days agoHandshake completed277 ms
11 days agoHandshake completed606 ms
14 days agoHandshake completed372 ms
16 days agoHandshake completed622 ms
18 days agoHandshake completed607 ms
20 days agoHandshake completed282 ms
22 days agoHandshake completed326 ms
24 days agoHandshake completed488 ms
26 days agoHandshake completed267 ms
27 days agoHandshake completed727 ms
29 days agoHandshake completed499 ms

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

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.

Related

All hosted MCP serversGlide connector for AI assistantsGlide for AI agents

Listing data comes from the official MCP registry. Glide is not affiliated with Witness and makes no claim about it beyond what these checks measured.