# ChurnLens (remote · churnlens.site)

Buyer-side SaaS due diligence: upload subscription CSV, detect hidden churn risk

- Trust score: 66/100 (medium)
- Change this week: +50
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-08-03

## Components

- remote · `churnlens.site`: 66/100 (this document), [markdown](https://verifymcp.io/servers/kindrat86-churnlens/api-mcp.md), [page](https://verifymcp.io/servers/kindrat86-churnlens/api-mcp)

## Channel facts

- Endpoint: `https://churnlens.site/api/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `1.0.0`

## Trust breakdown

How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-08-03.

- **Endpoint Security**: 63/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - Authorisation not fully verified: no authorisation is required to call this server, and 6 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe.
  - HTTPS is enforced; there's no plaintext access path.
  - The HSTS (Strict-Transport-Security) header is present.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 81/100
  - AI-judged instruction clarity (excellent).
  - Context-footprint check failed: tool/resource definitions use about 713 tokens (~118/item across 6 items; 6 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 27/100
  - Stability observed for 8 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
- **Capabilities**: 20/100
  - Spec-recency check failed: implements MCP spec 2024-11-05; the latest is 2026-07-28.

## Install

### Claude

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

### Codex

```toml
[mcp_servers.kindrat86-churnlens]
url = "https://churnlens.site/api/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "kindrat86-churnlens": {
      "type": "remote",
      "url": "https://churnlens.site/api/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add kindrat86-churnlens --url https://churnlens.site/api/mcp --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  kindrat86-churnlens:
    url: "https://churnlens.site/api/mcp"
```

### Other

```json
{
  "mcpServers": {
    "kindrat86-churnlens": {
      "type": "http",
      "url": "https://churnlens.site/api/mcp"
    }
  }
}
```

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-08-02 (score 66, +1)

No change was recorded against any check on this day. Stability & Change Management went from 20 to 23. That category is still filling its 30-day observation window: 6 days of observed history at the previous scan, 7 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-07-31 (score 65, 0)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-07-30 (score 65, +1)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-07-28 (score 64, +48)

- [security improvement] Transport: fail → pass
- [security] Authorization: Authorisation not fully verified: no authorisation is required to call this server, and 6 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe.
- [functional regression] MCP protocol: unverified → fail
- [functional improvement] Stability: unverified → 0.07
- [functional improvement] Tool coverage: unverified → 100

### 2026-07-27 (score 16, −46)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-07-26 (score 62)

First indexed and scored.

## MCP tools (6)

### `calculate_churn_rate` (~144 tokens)

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.

Input parameters:

- `churned_mrr` (number): MRR lost to full cancellations.
- `contraction_mrr` (number): MRR lost to downgrades (customer retained).
- `expansion_mrr` (number): MRR gained from upgrades and expansion within the existing base. Excludes new customers.
- `starting_mrr` (number, required): MRR at the start of the period, in any single currency unit.

### `analyze_revenue_concentration` (~126 tokens)

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?

Input parameters:

- `customer_mrrs` (array, required): Per-customer MRR values. Order does not matter.
- `top_n` (number): How many top customers to aggregate for the top-N share. Default 5.
- `whale_threshold_pct` (number): Revenue share above which a customer counts as a whale. Default 25.

### `detect_zombie_mrr` (~81 tokens)

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.

Input parameters:

- `accounts` (array, required): One entry per paying account.
- `threshold_days` (number): Days of inactivity before an account counts as dormant. Default 90.

### `score_saas_health` (~151 tokens)

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.

Input parameters:

- `annual_plan_share_pct` (number, required): Share of revenue on annual contracts, as a percentage.
- `ltv_to_cac_ratio` (number, required): Lifetime value divided by customer acquisition cost.
- `monthly_churn_rate_pct` (number, required): Monthly revenue churn, as a percentage (5 means 5%).
- `nrr_pct` (number, required): Net revenue retention, as a percentage.
- `top_customer_share_pct` (number, required): Largest single customer's share of revenue, as a percentage.

### `calculate_ltv` (~126 tokens)

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.

Input parameters:

- `arpa` (number, required): Average revenue per account, per month.
- `cac` (number): Customer acquisition cost. Optional — supply it to get the ratio and payback.
- `gross_margin_pct` (number): Gross margin percentage. Defaults to 100, which gives lifetime revenue.
- `monthly_churn_rate_pct` (number, required): Monthly churn, as a percentage.

### `get_scoring_bands` (~85 tokens)

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.

Input parameters:

- `metric` (string): Which band set to return: 'nrr', 'concentration', 'health', or omit for all.

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/kindrat86-churnlens/api-mcp#diagnostics

## Score history

- 2026-08-03: 66
- 2026-08-02: 66
- 2026-08-01: 65
- 2026-07-31: 65
- 2026-07-30: 65
- 2026-07-29: 64
- 2026-07-28: 64
- 2026-07-27: 16
- 2026-07-26: 62

## Links

- Remote endpoint: https://churnlens.site/api/mcp
- Website: https://churnlens.site/
- Changelog RSS feed: https://verifymcp.io/servers/kindrat86-churnlens/api-mcp/changelog.xml
- Changelog JSON feed: https://verifymcp.io/servers/kindrat86-churnlens/api-mcp/changelog.json
- HTML version of this page: https://verifymcp.io/servers/kindrat86-churnlens/api-mcp