Remote MCP · Endpoint

Leaklens: benchmark leakage checks MCP server

No. Leaklens: benchmark leakage checks answered an MCP handshake 10 hours ago.

UpLast checked 10 hours ago

Server URL

https://leaklens.grain64.com/mcp

The last check completed an MCP handshake.

Registry name
com.grain64.leaklens/leaklens
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
639 ms
Tools exposed
2 tools
Uptime, last 30 days
3 checks from 3 checks
Described by its publisher as
Check SWE-bench Verified/Lite tasks for leaked fixes: tier, quote, fix-commit date. Free, no key.
Listing
From the official MCP registry (active).
Recent checks of Leaklens: benchmark leakage checks
CheckedResultHandshake
10 hours agoHandshake completed639 ms
4 days agoHandshake completed541 ms
7 days agoHandshake completed252 ms

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

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