MCP.Market

ChurnLens MCP server

online · 100% uptime
by kindrat86·io.github.kindrat86/churnlens·v1.0.1
No reviews yet

Buyer-side SaaS due-diligence maths: NRR, GRR, revenue concentration, zombie MRR, LTV:CAC.

A87/100grade A
Write a reviewRun it
What users say
No reviews yet
Be the first
Safety scan
A87/100

full report

Adoption
New

0 stars

Reviews

Write one

Nobody has reviewed ChurnLens yet.

If you have run it, two minutes of your experience saves the next person an afternoon.

ChurnLens tools (6)

write = sends, deletes, buys or posts
  • analyze_revenue_concentrationFree

    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?

  • calculate_churn_rateFree

    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_ltvFree

    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.

  • detect_zombie_mrrFree

    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.

  • get_scoring_bandsFree

    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.

  • score_saas_healthFree

    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.

Public scan report

scanner v0.1.10 · 2026-11-03 · same rubric, same numbers if you re-run it

no findings
  • –Code scanremote-only server, no package to scann/a
  • Live reliabilityremote reachable in 714ms20/20
  • Tool poisoning6 tool descriptions checked15/15
  • Auth qualityopen endpoint, read-only tools10/15
  • Maintenancelast push 73 days ago12/15
  • Maintainer identityregistry namespace matches repository owner; GitHub account older than a year8/10
Overall 87/100. Components that don't apply are left out of the denominator. Any critical finding is an F.RubricAppeal a findingJSON

How ChurnLens compares

Against every graded MCP server, from our own scans and uptime checks. Updated after each scan run.

Safety score
87/100
higher than 73% of 48,255 servers
Tools
6
the typical server has 7
Tools that change things
0%
typical: 0%. Fewer write tools means less an agent can break
Uptime
100%
of our recent checks; the typical remote server answers 100%
Response time
201 ms
faster than 63% of 30,031 servers

What its tools let an agent do: 6 read

Install ChurnLens in Claude Code, Cursor or VS Code

claude mcp add --transport http churnlens https://churnlens.site/api/mcp
Add to Cursor

What the publisher says

From the ChurnLens repository's README, as published. We do not edit it. Read it on GitHub

ChurnLens MCP server

Buyer-side SaaS due-diligence maths for AI agents. Net and gross revenue retention, revenue concentration risk, dormant ("zombie") MRR, LTV:CAC and a composite health score — computed from figures you supply.

Live endpoint: https://churnlens.site/api/mcp — streamable HTTP, MCP protocol 2024-11-05. No authentication, no account, no rate limit, and nothing you send is stored.

Install

Claude Desktop, Claude Code, or any client that speaks stdio:

npx mcp-remote https://churnlens.site/api/mcp

By config:

{
  "mcpServers": {
    "churnlens": {
      "command": "npx",
      "args": ["mcp-remote", "https://churnlens.site/api/mcp"]
    }
  }
}

A GET on the endpoint returns the manifest. The machine-readable descriptor is at /.well-known/mcp.json.

Tools

Every tool returns structuredContent alongside the text block, so an agent gets typed numbers rather than prose it has to parse back out.

Example

calculate_churn_rate({
  starting_mrr:    100000,
  expansion_mrr:    37000,
  contraction_mrr:   5000,
  churned_mrr:      17000
})

// nrr_pct: 115, grr_pct: 78, expansion_masking_spread_pts: 37
// "A wide NRR-GRR spread: expansion revenue is masking substantial
//  churn underneath. Diligence should look at the retained base
//  separately from upsell."

A business reporting 115% net revenue retention sounds excellent. The same business at 78% gross revenue retention is losing nearly a quarter of its revenue base a year and covering the hole with upsell. Most dashboards show the first number and not the second.

On the scoring bands

getscoringbands returns thresholds, not measured data. They are informed by published industry benchmarks — SaaS Capital, Benchmarkit, Recurly and FE International — cited with sources at churnlens.site/benchmarks. Segment matters enormously: median retention for enterprise infrastructure and for SMB self-serve are not the same number. Do not present a band as though it were a survey result.

What it does not do

These tools compute from summary figures you supply. They cannot see what only emerges from customer-level data — cohort decay curves, renewal-cliff timing, concentration in specific logos. Treat them as a first-pass screen.

Verify the maths yourself

The same calculations are open source under MIT at kindrat86/saas-metrics — zero dependencies, every scoring band documented, 27 tests. A result from this server can be reproduced independently.

Interactive versions for humans, no signup: churnlens.site/free.

About

ChurnLens is a buyer-side SaaS due-diligence tool for acquirers, private-equity firms and M&A analysts.

Unaffiliated with the similarly named churnlens.io (retention automation) or

churnlens.tech (churn prediction).

MIT licensed. Free.

Nothing above is checked by us. What we check is on the safety report.

ChurnLens: common questions

Is ChurnLens MCP server safe?
Yes, by our scan: it is graded A (87/100). Read the ChurnLens safety report
How do I install ChurnLens?
It runs remotely at churnlens.site. Add it to Claude Code, Cursor, VS Code or Claude Desktop with the snippets above, or call it through the mcp.market gateway without installing anything.
Does ChurnLens need an API key?
Not as far as the registry entry and our scan can tell: no credentials are declared or required.
Is ChurnLens maintained?
The last commit was 73 days ago (2026-08-23). The latest release is v1.0.1.
Is ChurnLens up?
100% of our last 28 checks got an answer. We check remote servers about four times a day.
How does ChurnLens compare with other MCP servers?
safety score 87/100 (higher than 73% of 48,255 servers); tools 6 (the typical server has 7); tools that change things 0% (typical: 0%. Fewer write tools means less an agent can break). Full comparison.

More from kindrat86 →