ChurnLens
REMOTE · CHURNLENS.SITE
Buyer-side SaaS due-diligence maths: NRR, GRR, revenue concentration, zombie MRR, LTV:CAC.
Available components
Last scanned (6 hours ago)
Scores higher than 76% of remote servers
Reachable. Last reached 5 Nov 2026.
Category Finance and Payments
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. How we score → Why this is hard to score →
Endpoint Security63
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- 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. See how to fix → View diagnostics → Unverified
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability76
- AI-judged instruction clarity (good).Pass
- 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. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management100
- No destabilizing schema changes in the last 30 days.Pass
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 6 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 6 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities20
- Spec-recency check failed: implements MCP spec 2024-11-05; the latest is 2026-07-28. See how to fix → Fail
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 28 Sept 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 25 Sept 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 27 Aug 26 0
- Stability: 0.97 → pass security
- 26 Aug 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 25 Aug 26 0
- Stability: 0.97 → pass security
- 11 Aug 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 31 Jul 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 30 Jul 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 5 Nov 2026 · Probed https://churnlens.site/api/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=churnlens.site | CN=YR1,O=Let's Encrypt,C=US | 3 Sept 2026 | 2 Dec 2026 | RSA 2048 | SHA256-RSA | 65ca89e7adb8d235e43e6f1d89bb4035d4a |
| SANs: churnlens.site | ||||||
| CN=YR1,O=Let's Encrypt,C=US (CA) | CN=Root YR,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | RSA 2048 | SHA256-RSA | a20253f15f2691c05dc1ce13b9bcca4e |
| CN=Root YR,O=ISRG,C=US (CA) | CN=ISRG Root X1,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | RSA 4096 | SHA256-RSA | f24b6d17f9d9ad7cb1c9fea78782699f |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of churnlens.site. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| site. | present | 31826 | 13 | Verified |
| churnlens.site. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
| Header | Value |
|---|---|
| strict-transport-security | max-age=63072000; includeSubDomains; preload |
| content-security-policy | default-src 'self'; script-src 'self' 'unsafe-inline' https://eu.i.posthog.com https://eu-assets.i.posthog.com; style-src 'self' 'unsafe-inline' https://fonts.googleapis.com; font-src 'self' https://fonts.gstatic.com; img-src 'self' data: https:; connect-src 'self' https://eu.i.posthog.com https://eu-assets.i.posthog.com; frame-src 'self'; frame-ancestors 'none'; object-src 'none'; base-uri 'self'; form-action 'self'; upgrade-insecure-requests |
| x-content-type-options | nosniff |
| x-frame-options | DENY |
| referrer-policy | strict-origin-when-cross-origin |
| permissions-policy | camera=(), microphone=(), geolocation=(), payment=(), usb=(), fullscreen=(), display-capture=(), accelerometer=(), gyroscope=(), magnetometer=(), browsing-topics=(), interest-cohort=() |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://churnlens.site/api/mcp | Verified | 200 | |
| http (plaintext) | http://churnlens.site/api/mcp | HTTPS enforced | 308 | https://churnlens.site/api/mcp |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
analyze_revenue_concentration ~126
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?
| Name | Type | Req | Description |
|---|---|---|---|
| customer_mrrs | array | yes | 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. |
No output schema declared.
No examples provided.
calculate_churn_rate ~144
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.
| Name | Type | Req | Description |
|---|---|---|---|
| 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 | yes | MRR at the start of the period, in any single currency unit. |
No output schema declared.
No examples provided.
calculate_ltv ~126
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.
| Name | Type | Req | Description |
|---|---|---|---|
| arpa | number | yes | 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 | yes | Monthly churn, as a percentage. |
No output schema declared.
No examples provided.
detect_zombie_mrr ~81
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.
| Name | Type | Req | Description |
|---|---|---|---|
| accounts | array | yes | One entry per paying account. |
| threshold_days | number | – | Days of inactivity before an account counts as dormant. Default 90. |
No output schema declared.
No examples provided.
get_scoring_bands ~85
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.
| Name | Type | Req | Description |
|---|---|---|---|
| metric | string | – | Which band set to return: 'nrr', 'concentration', 'health', or omit for all. |
No output schema declared.
No examples provided.
score_saas_health ~151
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.
| Name | Type | Req | Description |
|---|---|---|---|
| annual_plan_share_pct | number | yes | Share of revenue on annual contracts, as a percentage. |
| ltv_to_cac_ratio | number | yes | Lifetime value divided by customer acquisition cost. |
| monthly_churn_rate_pct | number | yes | Monthly revenue churn, as a percentage (5 means 5%). |
| nrr_pct | number | yes | Net revenue retention, as a percentage. |
| top_customer_share_pct | number | yes | Largest single customer's share of revenue, as a percentage. |
No output schema declared.
No examples provided.
How do I install the ChurnLens MCP server?
ChurnLens is a hosted endpoint at https://churnlens.site/api/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
remote · churnlens.site
claude mcp add --transport http kindrat86-churnlens 'https://churnlens.site/api/mcp'
What is the ChurnLens MCP server?
ChurnLens is an MCP server listed in the public MCP registry as io.github.kindrat86/churnlens. Buyer-side SaaS due-diligence maths: NRR, GRR, revenue concentration, zombie MRR, LTV:CAC. This page covers its hosted endpoint (https://churnlens.site/api/mcp).
Is the ChurnLens MCP server safe to use?
ChurnLens scores 78 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the ChurnLens MCP server expose?
ChurnLens exposes 6 tools: calculate_churn_rate, analyze_revenue_concentration, detect_zombie_mrr, score_saas_health, calculate_ltv, get_scoring_bands. Their descriptions and schemas cost roughly 713 tokens of context every time the server is loaded.
Does the ChurnLens MCP server require authentication?
No. We connected to ChurnLens without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the ChurnLens MCP server still maintained?
ChurnLens is still listed as active in the MCP registry. We last reached this channel on 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.