RetentionCheck
NPM · @RETENTIONCHECK/MCP-SERVER · SCANNED SEP 20
Pull churn from Stripe, Postgres, MySQL, or pasted feedback. AI-ranked drivers + fixes.
Available components
How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score → Why this is hard to score →
Supply Chain Security98
- No malware found by supply-chain analysis.Pass
- No known CVEs affecting this package version or its production dependencies.Pass
- No install/post-install scripts declared.Pass
- 40 of 123 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency19
- Repository check failed: the declared repository URL returned HTTP 404. See how to fix → View diagnostics → Fail
- Provenance check failed: no build-provenance attestation is published. See how to fix → View diagnostics → Fail
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 123 days ago).Pass
- Security-disclosure policy not yet verified: we couldn't inspect the source repository.Unverified
Schema Quality & AI Usability79
- AI-judged instruction clarity (excellent).Pass
- Tool/resource definitions use about 487 tokens (~121/item across 4 items; 4 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management93
- Stability observed for 28 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
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 4 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 4 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
How do I install the RetentionCheck MCP server?
RetentionCheck runs locally as an npm package, launched with npx -y @retentioncheck/mcp-server. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
npm · @retentioncheck/mcp-server
claude mcp add brianfofficial-retentioncheck-mcp-server -- npx -y @retentioncheck/mcp-server
{
"mcpServers": {
"brianfofficial-retentioncheck-mcp-server": {
"command": "npx",
"args": [
"-y",
"@retentioncheck/mcp-server"
]
}
}
} {
"servers": {
"brianfofficial-retentioncheck-mcp-server": {
"command": "npx",
"args": [
"-y",
"@retentioncheck/mcp-server"
]
}
}
} codex mcp add brianfofficial-retentioncheck-mcp-server -- npx -y @retentioncheck/mcp-server
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"brianfofficial-retentioncheck-mcp-server": {
"type": "local",
"command": [
"npx",
"-y",
"@retentioncheck/mcp-server"
],
"enabled": true
}
}
} openclaw mcp add brianfofficial-retentioncheck-mcp-server --command npx --arg -y --arg @retentioncheck/mcp-server
mcp_servers:
brianfofficial-retentioncheck-mcp-server:
command: "npx"
args: ["-y", "@retentioncheck/mcp-server"] {
"McpServers": {
"brianfofficial-retentioncheck-mcp-server": {
"Transport": "stdio",
"Command": "npx",
"Arguments": [
"-y",
"@retentioncheck/mcp-server"
]
}
}
} assistant mcp add brianfofficial-retentioncheck-mcp-server -t stdio -c npx -a -y @retentioncheck/mcp-server
{
"mcpServers": {
"brianfofficial-retentioncheck-mcp-server": {
"command": "npx",
"args": [
"-y",
"@retentioncheck/mcp-server"
]
}
}
} 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.
- 18 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 83 to 87. That category is still filling its 30-day observation window: 25 days of observed history at the previous scan, 26 at this one. The score rises as the window fills, whether or not the server changes.
- 16 Sept 26 −2
- Stability: pass → 0.80 functional
- 15 Sept 26 0
- Stability: 0.97 → pass security
- 14 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 93 to 97. That category is still filling its 30-day observation window: 28 days of observed history at the previous scan, 29 at this one. The score rises as the window fills, whether or not the server changes.
- 11 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 83 to 87. That category is still filling its 30-day observation window: 25 days of observed history at the previous scan, 26 at this one. The score rises as the window fills, whether or not the server changes.
- 10 Sept 26 −2
- Stability: pass → 0.83 functional
- 9 Sept 26 0
- Stability: 0.97 → pass security
- 8 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 93 to 97. That category is still filling its 30-day observation window: 28 days of observed history at the previous scan, 29 at this one. The score rises as the window fills, whether or not the server changes.
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 20 Sept 2026 · Analysed npm/@retentioncheck/mcp-server@0.6.2
Provenance No attestation
The registry publishes no build provenance for this version, so there is nothing to verify.
| Result | No attestation |
|---|---|
| Ecosystem | npm |
Background: How many MCP packages publish verified provenance →
Dependencies 123 packages
| Packages resolved | 123 |
|---|---|
| Stale | 40 |
| Tree resolution | Complete |
Background: SBOMs and build attestations, explained →
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_churn Analyze Churn ~92
Analyze customer cancellation feedback to identify churn patterns, severity, and actionable recommendations. Paste raw feedback text (one response per line) or CSV data.
| Name | Type | Req | Description |
|---|---|---|---|
| feedback | string | yes | Raw cancellation feedback. One response per line. Example: Too expensive Missing features we need Switched to competitor |
| focus | string | – | Optional focus area to narrow the analysis (e.g., 'pricing', 'onboarding') |
No output schema declared.
No examples provided.
analyze_sql_churn Analyze Churn from SQL Database ~206
Pull canceled subscriptions directly from a Postgres or MySQL database and analyze them for churn patterns. Requires POSTGRES_URL or MYSQL_URL env var (use a read-only database user , see retentioncheck.com/integrations for the exact SQL to create one). You describe your schema in plain arguments (table, cancelled_at_column, reason_column, etc.) and the tool generates a safe parameterized SELECT query. Includes plan MRR, sub age, and schema-mismatch detection with actionable errors. Defaults to last 90 days.
| Name | Type | Req | Description |
|---|---|---|---|
| dialect | string | yes | Which SQL dialect. Reads POSTGRES_URL or MYSQL_URL from env accordingly. |
| focus | string | – | Optional focus area to narrow the analysis (e.g., 'pricing', 'onboarding'). |
| lookback_days | integer | – | How many days back to analyze. Defaults to 90. Min 7. Max 365. |
| schema | object | yes | Schema mapping that tells the tool which columns hold what. |
No output schema declared.
No examples provided.
analyze_stripe_churn Analyze Stripe Churn ~127
Pull canceled subscriptions directly from Stripe and analyze them for churn patterns. Requires STRIPE_SECRET_KEY env var (use a restricted read-only key with Subscriptions, Customers, and Prices read access). Includes plan, MRR, sub age, and voluntary/involuntary context for each cancellation. Defaults to last 90 days.
| Name | Type | Req | Description |
|---|---|---|---|
| focus | string | – | Optional focus area to narrow the analysis (e.g., 'pricing', 'onboarding') |
| lookback_days | integer | – | How many days back to analyze. Defaults to 90. Min 7. Max 365. |
No output schema declared.
No examples provided.
get_example_analysis Example Churn Analysis ~62
See an example churn analysis to understand what RetentionCheck produces. Returns a pre-computed analysis , no API key required.
| Name | Type | Req | Description |
|---|---|---|---|
| scenario | string | – | Which example scenario to show. Options: b2b-saas (default), consumer-app, pricing |
No output schema declared.
No examples provided.
What is the RetentionCheck MCP server?
RetentionCheck is an MCP server listed in the public MCP registry as io.github.brianfofficial/retentioncheck-mcp-server. Pull churn from Stripe, Postgres, MySQL, or pasted feedback. AI-ranked drivers + fixes. This page covers its npm package (@retentioncheck/mcp-server).
Is the RetentionCheck MCP server safe to use?
RetentionCheck scores 78 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 20 September 2026. It declares no install or post-install scripts. 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 RetentionCheck MCP server expose?
RetentionCheck exposes 4 tools: analyze_churn, analyze_stripe_churn, analyze_sql_churn, get_example_analysis. Their descriptions and schemas cost roughly 487 tokens of context every time the server is loaded.
Is the RetentionCheck MCP server still maintained?
RetentionCheck is still listed as active in the MCP registry. We last reached this channel on 20 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.
What licence is the RetentionCheck MCP server under?
RetentionCheck declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.