Skip to content

ChurnLens

by kindrat86 · remote · no sign-in to list tools · v1.0.1 · published by GitHub user kindrat86

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

Changes · 4
CompareRegistry entry

6 tools: 4 change things and 2 only read.

Scanned Oct 21, 2026

No check matched anything in the tool definitions. No finding is not a safety guarantee. How the checks work.

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

Tools

Open a tool for its reasons and full description. Descriptions are the publisher's own words, shown as they are.

6 tools

Changes things 4Claude Code: ask
  • calculate_churn_rateCalculate net revenue retention (NRR), gross revenue retention (GRR), revenue churn and implied customer lifetime from one period's MRR movements.No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    Description, as the server wrote it
    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_ltvCalculate gross-margin-adjusted customer lifetime value, the LTV:CAC ratio and CAC payback in months.No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    Description, as the server wrote it
    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_mrrIdentify dormant-but-paying accounts — revenue that still counts in MRR but whose customers have stopped showing up.No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    Description, as the server wrote it
    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_saas_healthScore a SaaS business 0-100 across five dimensions — retention, growth, concentration, efficiency and durability — and return the composite.No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    Description, as the server wrote it
    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.
Only reads 2Claude Code: allow
  • analyze_revenue_concentrationAssess customer concentration risk across a book of revenue using the Herfindahl-Hirschman Index (HHI), top-N share and whale detection.No findings

    Why it is in this group

    • The name "analyze_revenue_concentration" says "analyze": a word for reading.
    Description, as the server wrote it
    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?
  • get_scoring_bandsReturn the scoring thresholds ChurnLens applies to NRR, revenue concentration and the composite health score.No findings

    Why it is in this group

    • The name "get_scoring_bands" says "get": a word for reading.
    Description, as the server wrote it
    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.

This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.

Install

Pinned to version 1.0.1. Values in angle brackets are yours to fill in.

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

Run in a terminal.

Claude Code permissions

Allow the reads, ask before a change, deny the deletes. Paste into .claude/settings.json.

.claude/settings.json
{
  "permissions": {
    "allow": [
      "mcp__churnlens__analyze_revenue_concentration",
      "mcp__churnlens__get_scoring_bands"
    ],
    "ask": [
      "mcp__churnlens__calculate_churn_rate",
      "mcp__churnlens__detect_zombie_mrr",
      "mcp__churnlens__score_saas_health",
      "mcp__churnlens__calculate_ltv"
    ],
    "deny": []
  }
}

Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. It assumes the server is installed as churnlens. Review it before you use it.