Buyer-side SaaS due-diligence maths: NRR, GRR, revenue concentration, zombie MRR, LTV:CAC.
MCPpedia last refreshed this data
io.github.kindrat86/churnlens is an MCP server that buyer-side SaaS due-diligence maths: NRR, GRR, revenue concentration, zombie MRR, LTV:CAC. Its tool list has not been published yet over http, requires no API key, and scores 72/100 on MCPpedia's security, maintenance and efficiency rubric.
Config is the same across clients — only the file and path differ.
{
"mcpServers": {
"churnlens": {
"args": [
"mcp-remote",
"https://churnlens.site/api/mcp"
],
"command": "npx"
}
}
}Are you the author?
Add this badge to your README to show your security score and help users find safe servers.
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.
No automated test available for this server. Check the GitHub README for setup instructions.
Five weighted categories — click any category to see the underlying evidence.
No known CVEs.
No package registry to scan.
Click any tool to inspect its schema.
Be the first to review
Have you used this server?
Share your experience — it helps other developers decide.
Sign in to write a review.
Others in cloud / finance
MCP Server for GCP environment for interacting with various Observability APIs.
OKX trading MCP server — connect AI agents to spot, swap, futures, options & grid bots via the Model Context Protocol.
Real-time financial market data: stocks, forex, crypto, commodities, and economic indicators
HoneyBook client-portal MCP server for Claude — view contracts and invoices from wedding vendors
MCP Security Weekly
Get CVE alerts and security updates for io.github.kindrat86/churnlens and similar servers.
Start a conversation
Ask a question, share a tip, or report an issue.
Sign in to join the discussion.
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.
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.
| Tool | What it returns |
|---|---|
calculate_churn_rate | NRR, GRR, revenue churn, correctly compounded annualised churn, and the NRR−GRR spread that exposes churn masked by expansion |
analyze_revenue_concentration | Herfindahl-Hirschman Index, top-N revenue share, and which customers are large enough that losing one is a balance-sheet event |
detect_zombie_mrr | Accounts still paying but dormant past a threshold, and the ARR at risk behind them |
score_saas_health | Composite 0–100 across retention, growth, concentration, efficiency and durability, plus the weakest dimension |
calculate_ltv | Gross-margin-adjusted lifetime value, LTV:CAC and CAC payback in months |
get_scoring_bands | Every threshold the tools apply, with its provenance |
Every tool returns structuredContent alongside the text block, so an agent
gets typed numbers rather than prose it has to parse back out.
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.
get_scoring_bands 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.
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.
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.
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.