Remote MCP · Endpoint

ExitProof MCP server

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

DownLast checked 1 hour ago

Server URL

https://exitproof.davisvillelabs.com/mcp

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

Registry name
com.davisvillelabs/exitproof
Transport
Streamable HTTP
Protocol negotiated
Not measured yet
Handshake latency
—
Tools exposed
6 tools
Uptime, last 30 days
52.6% from 19 checks
Described by its publisher as
Reversibility intelligence and durable exit evidence for AI agents before real-world commitments.
Listing
From the official MCP registry (active).
Recent checks of ExitProof
CheckedResultHandshake
1 hour agoFailed - the server returned an HTTP error—
18 hours agoFailed - the server returned an HTTP error—
2 days agoFailed - the server returned an HTTP error—
3 days agoFailed - the server returned an HTTP error—
4 days agoFailed - the server returned an HTTP error—
5 days agoFailed - the server returned an HTTP error—
6 days agoFailed - the server returned an HTTP error—
7 days agoFailed - the server returned an HTTP error—
10 days agoFailed - the server returned an HTTP error—
13 days agoHandshake completed693 ms
15 days agoHandshake completed344 ms
17 days agoHandshake completed423 ms
19 days agoHandshake completed656 ms
21 days agoHandshake completed535 ms
23 days agoHandshake completed580 ms
25 days agoHandshake completed405 ms
27 days agoHandshake completed164 ms
28 days agoHandshake completed410 ms
29 days agoHandshake completed466 ms

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

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