Koskamo

ChurnLens MCP

A buyer-side SaaS due-diligence MCP server that computes NRR, GRR, revenue concentration, zombie MRR, LTV:CAC, and a composite health score from supplied figures. It provides structured data for AI agents to assess revenue quality and churn risk before acquisitions, with no authentication or data retention.

Endpoint and access

No sign-in to connect and list tools. Individual tools may still need a vendor account, credentials, or permissions; check the documented prerequisites.

ChurnLens MCP logo, by ChurnLensCommunity listingStreamable HTTPNo sign-inEndpoint checked 2026-11-06Published by ChurnLens
MCP endpoint (Streamable HTTP)
https://churnlens.site/api/mcp
Vendor documentation

What its tools do

6 tools, grouped by the hints the server advertises. Hints are self-declared, not verified behavior.

6 of 6 have a description · 0 of 6 declare behavior hints · 6 of 6 with parameters document them all

Checks and signals

Each line is separate evidence, not a trust score.

  • Passed Endpoint answered the live check ·
  • Warning Advertises resources/templates/list but does not implement it
  • Availability 1 of 1 checks passed in 30 days

What you can do with it

  • Calculate Net and Gross Revenue Retention (NRR/GRR)
  • Analyze revenue concentration using HHI
  • Detect dormant or zombie MRR accounts
  • Score overall SaaS health composite

Source and maintenance

Community listingRegistry 1.0.1
Maintenance checked

Protocol and capabilities

Server
churnlens-mcp 2.0.0
MCP protocol negotiated in check
2024-11-05
Tools
6 advertised
Resources
0 advertised
Resource templates
Not advertised
Prompts
0 advertised
Server-advertised capabilities
{
  "tools": {
    "listChanged": false
  },
  "prompts": {},
  "resources": {}
}

Tools

6 advertised

calculate_churn_rate
Advertised by the server during the last successful anonymous check.

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_churn_rate input schema
{
  "type": "object",
  "required": [
    "starting_mrr"
  ],
  "properties": {
    "churned_mrr": {
      "type": "number",
      "description": "MRR lost to full cancellations."
    },
    "starting_mrr": {
      "type": "number",
      "description": "MRR at the start of the period, in any single currency unit."
    },
    "expansion_mrr": {
      "type": "number",
      "description": "MRR gained from upgrades and expansion within the existing base. Excludes new customers."
    },
    "contraction_mrr": {
      "type": "number",
      "description": "MRR lost to downgrades (customer retained)."
    }
  }
}
analyze_revenue_concentration
Advertised by the server during the last successful anonymous check.

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?

analyze_revenue_concentration input schema
{
  "type": "object",
  "required": [
    "customer_mrrs"
  ],
  "properties": {
    "top_n": {
      "type": "number",
      "description": "How many top customers to aggregate for the top-N share. Default 5."
    },
    "customer_mrrs": {
      "type": "array",
      "items": {
        "type": "number"
      },
      "description": "Per-customer MRR values. Order does not matter."
    },
    "whale_threshold_pct": {
      "type": "number",
      "description": "Revenue share above which a customer counts as a whale. Default 25."
    }
  }
}
detect_zombie_mrr
Advertised by the server during the last successful anonymous check.

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.

detect_zombie_mrr input schema
{
  "type": "object",
  "required": [
    "accounts"
  ],
  "properties": {
    "accounts": {
      "type": "array",
      "items": {
        "type": "object",
        "required": [
          "mrr",
          "days_since_last_activity"
        ],
        "properties": {
          "mrr": {
            "type": "number"
          },
          "customer": {
            "type": "string"
          },
          "days_since_last_activity": {
            "type": "number"
          }
        }
      },
      "description": "One entry per paying account."
    },
    "threshold_days": {
      "type": "number",
      "description": "Days of inactivity before an account counts as dormant. Default 90."
    }
  }
}
score_saas_health
Advertised by the server during the last successful anonymous check.

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.

score_saas_health input schema
{
  "type": "object",
  "required": [
    "monthly_churn_rate_pct",
    "nrr_pct",
    "top_customer_share_pct",
    "ltv_to_cac_ratio",
    "annual_plan_share_pct"
  ],
  "properties": {
    "nrr_pct": {
      "type": "number",
      "description": "Net revenue retention, as a percentage."
    },
    "ltv_to_cac_ratio": {
      "type": "number",
      "description": "Lifetime value divided by customer acquisition cost."
    },
    "annual_plan_share_pct": {
      "type": "number",
      "description": "Share of revenue on annual contracts, as a percentage."
    },
    "monthly_churn_rate_pct": {
      "type": "number",
      "description": "Monthly revenue churn, as a percentage (5 means 5%)."
    },
    "top_customer_share_pct": {
      "type": "number",
      "description": "Largest single customer's share of revenue, as a percentage."
    }
  }
}
calculate_ltv
Advertised by the server during the last successful anonymous check.

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.

calculate_ltv input schema
{
  "type": "object",
  "required": [
    "arpa",
    "monthly_churn_rate_pct"
  ],
  "properties": {
    "cac": {
      "type": "number",
      "description": "Customer acquisition cost. Optional — supply it to get the ratio and payback."
    },
    "arpa": {
      "type": "number",
      "description": "Average revenue per account, per month."
    },
    "gross_margin_pct": {
      "type": "number",
      "description": "Gross margin percentage. Defaults to 100, which gives lifetime revenue."
    },
    "monthly_churn_rate_pct": {
      "type": "number",
      "description": "Monthly churn, as a percentage."
    }
  }
}
get_scoring_bands
Advertised by the server during the last successful anonymous check.

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.

get_scoring_bands input schema
{
  "type": "object",
  "properties": {
    "metric": {
      "enum": [
        "nrr",
        "concentration",
        "health"
      ],
      "type": "string",
      "description": "Which band set to return: 'nrr', 'concentration', 'health', or omit for all."
    }
  }
}

Prompts

0 advertised

No prompt definitions available.

Resources

0 advertised

No resource definitions available.

90-day uptime

A lightweight connection check about every six hours, sampled on hosts with many listings. It shows the server answered, not that its tools work.

Too few checks for a percentage yet (2 of 2 answered).

  1. 2026-11-06: 1 of 1 checks answered
  2. 2026-11-07: 1 of 1 checks answered

30-day availability

Aggregated from read-only remote checks; this is not a tool-execution or security guarantee.

Successful checks
1 of 1 (100%)
Average latency
1412 ms
95th percentile latency
1412 ms

Maintenance history

Public check and source-refresh events. Editorial and ownership records remain private.

  • · probe · passed · 1412 ms · metadata changed · 6 tool(s), 0 resource(s), 0 prompt(s); warnings: Advertises resources/templates/list but does not implement it

Connect from your client

Each snippet registers the same endpoint; pick the client you use.

This server is operated by the named third party. Listing and endpoint checks are not an endorsement or a security audit. Review the operator's permissions, terms, and data handling before connecting. How listings are checked and corrected.

Claude Code

Run this once in a terminal. It registers the remote server. Use --scope project to write .mcp.json for the repo.
Claude Code configuration
claude mcp add --transport http churnlens-mcp https://churnlens.site/api/mcp

Codex

Run this once. Codex stores MCP servers in ~/.codex/config.toml (or .codex/config.toml in a trusted project).
Codex configuration
codex mcp add churnlens-mcp --url https://churnlens.site/api/mcp

Cursor

Merge this server into .cursor/mcp.json in your project, then enable churnlens-mcp in your MCP settings.
Cursor configuration
{
  "mcpServers": {
    "churnlens-mcp": {
      "url": "https://churnlens.site/api/mcp"
    }
  }
}

Cline

Merge this into cline_mcp_settings.json (Cline → MCP Servers → Configure).
Cline configuration
{
  "mcpServers": {
    "churnlens-mcp": {
      "type": "streamableHttp",
      "url": "https://churnlens.site/api/mcp",
      "disabled": false
    }
  }
}

VS Code

Merge this server into .vscode/mcp.json. Use MCP: List Servers to start churnlens-mcp and inspect its tools.
VS Code configuration
{
  "servers": {
    "churnlens-mcp": {
      "type": "http",
      "url": "https://churnlens.site/api/mcp"
    }
  }
}

Gemini CLI

Run this once. It writes .gemini/settings.json in the current project; pass --scope user for ~/.gemini/settings.json.
Gemini CLI configuration
gemini mcp add --transport http churnlens-mcp https://churnlens.site/api/mcp

Claude Desktop

Open Claude Settings > Connectors > Add custom connector, enter this server URL and enable it for the conversation. This is a manual remote-connector handoff, not a desktop JSON configuration.
Claude Desktop configuration
https://churnlens.site/api/mcp

Windsurf

Merge this into ~/.codeium/windsurf/mcp_config.json, then refresh MCP in Cascade. Windsurf remote servers use serverUrl, not url.
Windsurf configuration
{
  "mcpServers": {
    "churnlens-mcp": {
      "serverUrl": "https://churnlens.site/api/mcp"
    }
  }
}

Let your agent find its tools

Find servers like ChurnLens MCP from your agent. Add Koskamo once to search the index for endpoints, access requirements, and client setup. Public discovery needs no key.