Remote MCP · Endpoint

leaks.md and confession.md MCP server

No. leaks.md and confession.md answered an MCP handshake 1 hour ago.

UpLast checked 1 hour ago

Server URL

https://leaks.md/mcp

The last check completed an MCP handshake.

Registry name
io.github.thechristianaicompany/leaks-and-confessions
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
166 ms
Tools exposed
11 tools
Uptime, last 30 days
100% from 14 checks
Described by its publisher as
Anonymous, encrypted disclosure of AI alignment and safety failures, with signed receipts.
Listing
From the official MCP registry (active).
Recent checks of leaks.md and confession.md
CheckedResultHandshake
1 hour agoHandshake completed166 ms
13 hours agoHandshake completed153 ms
2 days agoHandshake completed423 ms
4 days agoHandshake completed253 ms
6 days agoHandshake completed97 ms
9 days agoHandshake completed203 ms
11 days agoHandshake completed156 ms
13 days agoHandshake completed258 ms
15 days agoHandshake completed233 ms
17 days agoHandshake completed187 ms
19 days agoHandshake completed161 ms
21 days agoHandshake completed149 ms
23 days agoHandshake completed188 ms
24 days agoHandshake completed248 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 leaks.md and confession.md and makes no claim about it beyond what these checks measured.