mcpbeat

ChurnLens MCP Server

io.github.kindrat86/churnlens
answering

ChurnLens is answering right now. Last checked 4 min ago. It exposes 6 tools.

Buyer-side SaaS due diligence: upload subscription CSV, detect hidden churn risk

Uptime history 41 hours of history · worst hour 0%
41 hours agonow
94.5%
Uptime 24h
86 of 91 checks
6
Tools
read from the server
274 ms
Response time
average over 24h
open, no key
Access
streamable-http

Connect this server

Endpoint below is the one we actually reach during checks — not the one copied from a README. Last verified 4 min ago.

run in your terminal
claude mcp add churnlens --transport http https://churnlens.site/api/mcp
~/Library/Application Support/Claude/claude_desktop_config.json
{
  "mcpServers": {
    "churnlens": {
      "url": "https://churnlens.site/api/mcp"
    }
  }
}
~/.codex/config.toml
[mcp_servers.churnlens]
url = "https://churnlens.site/api/mcp"
.cursor/mcp.json
{
  "mcpServers": {
    "churnlens": {
      "url": "https://churnlens.site/api/mcp"
    }
  }
}
.vscode/mcp.json
{
  "mcpServers": {
    "churnlens": {
      "url": "https://churnlens.site/api/mcp"
    }
  }
}

Available tools 6

Read directly from the server with tools/list, grouped by what they act on. If a tool disappears, we record the date.

calculate
calculate_churn_rate
Calculate net revenue retention (NRR), gross revenue retention (GRR), revenue churn and implied customer lifetime from one period's MRR movements. Also reports the NRR-minus-GRR spread, which reveals how much churn is being masked by expansion revenue.
calculate_ltv
Calculate gross-margin-adjusted customer lifetime value, the LTV:CAC ratio and CAC payback in months. Omitting gross margin yields lifetime revenue rather than lifetime value — usually a third of the number.
analyze
analyze_revenue_concentration
Assess customer concentration risk across a book of revenue using the Herfindahl-Hirschman Index (HHI), top-N share and whale detection. Answers the question every acquirer asks first: how much revenue walks out with one logo?
detect
detect_zombie_mrr
Identify dormant-but-paying accounts — revenue that still counts in MRR but whose customers have stopped showing up. Zombie revenue is one renewal notice from cancelling and is invisible to standard revenue dashboards.
score
score_saas_health
Score a SaaS business 0-100 across five dimensions — retention, growth, concentration, efficiency and durability — and return the composite. Every mapping is published, so the score can be reconstructed by hand.
scoring
get_scoring_bands
Return the scoring thresholds ChurnLens applies to NRR, revenue concentration and the composite health score. These are bands, not measured benchmark data — the sourced benchmark figures are cited at https://churnlens.site/benchmarks.

Endpoints

URLTransportStateLatencyChecked
https://churnlens.site/api/mcp streamable-http answering 257 ms 4 min ago

ChurnLens — questions

Answers built from our own checks of this server.

What can ChurnLens do?
It exposes 6 tools, read directly from the server on our last check. Among them: analyze_revenue_concentration, calculate_churn_rate, calculate_ltv, detect_zombie_mrr, get_scoring_bands, score_saas_health. The full list with descriptions is on this page — we take it from the server itself via tools/list, not from a README. How MCP servers expose tools in the first place →
Is ChurnLens working right now?
We send a real MCP handshake every 15 minutes. Over the last 24 hours 86 of 91 checks got a reply (94.5%), average response time 274 ms. The bar chart above shows every period we have measured.
How do I connect ChurnLens?
Copy the ready config from this page — we generate it for Claude Code, Claude Desktop, Codex, Cursor and VS Code, each with the file path that client actually reads. It is a remote server, so there is nothing to install — the client connects to the address.
Does ChurnLens need an API key?
No. ChurnLens completed a full MCP handshake with us as an anonymous client and listed its tools without asking for anything. All 6 of them are readable on this page. This is what we observed, not what the docs claim.
How fast is ChurnLens?
It answers our handshake in 274 ms on average, which is faster than 50% of all working MCP servers we measure. The comparison comes from our own checks across the whole registry, every 15 minutes.