Remote MCP · Endpoint

ChurnLens MCP server

No. ChurnLens answered an MCP handshake 1 hour ago.

UpLast checked 1 hour ago

Server URL

https://churnlens.site/api/mcp

The last check completed an MCP handshake.

Registry name
io.github.kindrat86/churnlens
Transport
Streamable HTTP
Protocol negotiated
2024-11-05
Handshake latency
77 ms
Tools exposed
6 tools
Uptime, last 30 days
100% from 17 checks
Described by its publisher as
Buyer-side SaaS due-diligence maths: NRR, GRR, revenue concentration, zombie MRR, LTV:CAC.
Listing
From the official MCP registry (active).
Recent checks of ChurnLens
CheckedResultHandshake
1 hour agoHandshake completed77 ms
2 days agoHandshake completed80 ms
4 days agoHandshake completed87 ms
5 days agoHandshake completed89 ms
7 days agoHandshake completed83 ms
8 days agoHandshake completed120 ms
9 days agoHandshake completed88 ms
12 days agoHandshake completed269 ms
13 days agoHandshake completed658 ms
15 days agoHandshake completed62 ms
17 days agoHandshake completed68 ms
18 days agoHandshake completed94 ms
19 days agoHandshake completed98 ms
20 days agoHandshake completed70 ms
20 days agoHandshake completed555 ms
21 days agoHandshake completed91 ms
23 days agoHandshake completed67 ms

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

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