Index / MCP servers / ChurnLens

ChurnLens MCP server

Connect ChurnLens and your agent gets 6 tools, among them analyze_revenue_concentration, calculate_churn_rate, calculate_ltv. It answers at https://churnlens.site/api/mcp over streamable HTTP, and it listed its tools to an anonymous client, so no sign-in was needed for that. Our probes reached it 6 of 6 times since 11 September 2026; the last check, on 22 October 2026, succeeded.

Status
Answering
Tools
6
Reliability
6 of 6 checks
Response time
87 ms
Transport
streamable HTTP
Last checked
22 October 2026

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

Description as the publisher wrote it.

The 6 tools ChurnLens offers

ToolWhat it does
analyze_revenue_concentrationAssess 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?
Inputs: customer_mrrs, top_n, whale_threshold_pct
calculate_churn_rateCalculate 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 expans
Inputs: starting_mrr, expansion_mrr, contraction_mrr, churned_mrr
calculate_ltvCalculate 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.
Inputs: arpa, monthly_churn_rate_pct, gross_margin_pct, cac
detect_zombie_mrrIdentify 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.
Inputs: accounts, threshold_days
get_scoring_bandsReturn 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.
Inputs: metric
score_saas_healthScore 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.
Inputs: monthly_churn_rate_pct, nrr_pct, top_customer_share_pct, ltv_to_cac_ratio, annual_plan_share_pct

Add ChurnLens to your AI client

Every block below points at https://churnlens.site/api/mcp. Pick your client and copy.

Claude Code: one command in your terminal
claude mcp add --transport http churnlens https://churnlens.site/api/mcp
Claude Desktop: claude_desktop_config.json
{
  "mcpServers": {
    "churnlens": {
      "command": "npx",
      "args": ["-y", "mcp-remote", "https://churnlens.site/api/mcp"]
    }
  }
}
Cursor: ~/.cursor/mcp.json, or .cursor/mcp.json in a project
{
  "mcpServers": {
    "churnlens": {
      "url": "https://churnlens.site/api/mcp"
    }
  }
}
VS Code and GitHub Copilot: .vscode/mcp.json
{
  "servers": {
    "churnlens": {
      "type": "http",
      "url": "https://churnlens.site/api/mcp"
    }
  }
}
Zed: Zed settings.json
{
  "context_servers": {
    "churnlens": {
      "url": "https://churnlens.site/api/mcp"
    }
  }
}
Windsurf: ~/.codeium/mcp_config.json
{
  "mcpServers": {
    "churnlens": {
      "serverUrl": "https://churnlens.site/api/mcp"
    }
  }
}
JetBrains AI Assistant: Settings, Tools, AI Assistant, MCP, New MCP Server, as JSON
{
  "mcpServers": {
    "churnlens": {
      "url": "https://churnlens.site/api/mcp"
    }
  }
}
Continue: .continue/mcpServers/neuronto.yaml
name: ChurnLens
version: 0.0.1
schema: v1
mcpServers:
  - name: ChurnLens
    type: streamable-http
    url: https://churnlens.site/api/mcp
Gemini CLI: ~/.gemini/settings.json
{
  "mcpServers": {
    "churnlens": {
      "httpUrl": "https://churnlens.site/api/mcp"
    }
  }
}
Codex CLI: MCP server config
{
  "mcpServers": {
    "churnlens": {
      "type": "http",
      "url": "https://churnlens.site/api/mcp"
    }
  }
}
Warp: MCP servers, + Add, paste JSON
{
  "mcpServers": {
    "churnlens": {
      "url": "https://churnlens.site/api/mcp"
    }
  }
}
Goose: a one-click extension link
goose://extension?url=https%3A%2F%2Fchurnlens.site%2Fapi%2Fmcp&type=streamable_http&id=churnlens&name=ChurnLens

Is ChurnLens up right now?

It answered our last check on 22 October 2026 in 87 ms. Over 6 checks since 11 September 2026 it answered 6. Status here comes from Neuronto's own probes, not from the publisher.

MCP servers similar to ChurnLens

Questions about ChurnLens

How many tools does ChurnLens have?

6, as returned by the server's own tools/list on 15 September 2026: analyze_revenue_concentration, calculate_churn_rate, calculate_ltv, detect_zombie_mrr, get_scoring_bands, score_saas_health.

Is ChurnLens down?

It answered our last check on 22 October 2026 in 87 ms. Over 6 checks since 11 September 2026 it answered 6.

How do I add ChurnLens to Cursor?

Put the server under mcpServers in ~/.cursor/mcp.json with the URL https://churnlens.site/api/mcp. The exact JSON is above, with the same setup for Claude Code, Claude Desktop, VS Code, Windsurf, Zed, Gemini CLI and the rest.

Does ChurnLens need an API key?

It listed its tools to an anonymous client, so reading the tool list needs no key. Individual tools can still ask for credentials in their own inputs.

Where this comes from

Publisher: io.github.kindrat86. Endpoint host: churnlens.site. ARD identifier: urn:air:io.github.kindrat86:mcp:churnlens. First indexed 10 September 2026. The tools are exactly what the server returned; nothing on this page is inferred from its name. Ranking in Neuronto search is never for sale.

Is this your server? Get a message the day it stops answering or its tools change: monitoring, 14 days free. Or claim the domain to manage how it is listed.