co.churnkey/churnkey
REMOTE · MCP.CHURNKEY.CO · SCANNED AUG 23
Read and manage Churnkey cancel flows, retention metrics, and payment recovery
Available components
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 →
Endpoint Security78
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- The endpoint enforces authorisation, advertised via RFC 9728 protected-resource metadata. View diagnostics → Pass
- HTTPS enforcement could not be verified: the plaintext port answered with HTTP 405, which proves neither a plaintext path nor enforcement. View diagnostics → Unverified
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
- The authorisation server offers only Dynamic Client Registration (RFC 7591), which MCP 2026-07-28 deprecated in favour of Client ID Metadata Documents. View diagnostics → Partial
Transport & Reachability0
- Transport blocked by authentication: the endpoint requires auth we don't have to verify streamable-http. See how to fix → View diagnostics → Unverified
Schema Quality & AI Usability0
- Schema blocked by authentication: the endpoint requires auth we don't have to read it. See how to fix → Unverified
Stability & Change Management0
- Stability not yet verified: not enough scan history yet (needs a 30-day window).Unverified
Tool Coverage0
- Tool coverage blocked by authentication: the endpoint requires auth we don't have to read its tools.Unverified
Capabilities0
- Capabilities blocked by authentication: the endpoint requires auth we don't have to read them. See how to fix → Unverified
Unverified: 5 categories
Categories scored 0 because we could not verify them: authentication we do not have, an unreachable endpoint, or not enough scan history. We only credit what we can confirm.
How do I install the co.churnkey/churnkey MCP server?
co.churnkey/churnkey is a hosted endpoint at https://mcp.churnkey.co/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 · mcp.churnkey.co
claude mcp add --transport http co-churnkey-churnkey 'https://mcp.churnkey.co/mcp'
{
"mcpServers": {
"co-churnkey-churnkey": {
"url": "https://mcp.churnkey.co/mcp"
}
}
} {
"servers": {
"co-churnkey-churnkey": {
"type": "http",
"url": "https://mcp.churnkey.co/mcp"
}
}
} [mcp_servers.co-churnkey-churnkey] url = "https://mcp.churnkey.co/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"co-churnkey-churnkey": {
"type": "remote",
"url": "https://mcp.churnkey.co/mcp",
"enabled": true
}
}
} openclaw mcp add co-churnkey-churnkey --url 'https://mcp.churnkey.co/mcp' --transport streamable-http
mcp_servers:
co-churnkey-churnkey:
url: "https://mcp.churnkey.co/mcp" {
"McpServers": {
"co-churnkey-churnkey": {
"Transport": "http",
"Url": "https://mcp.churnkey.co/mcp"
}
}
} assistant mcp add co-churnkey-churnkey -t streamable-http -u 'https://mcp.churnkey.co/mcp'
{
"mcpServers": {
"co-churnkey-churnkey": {
"type": "http",
"url": "https://mcp.churnkey.co/mcp"
}
}
} The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.
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.
- 12 Aug 26 31
First indexed and scored.
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 23 Aug 2026 · Probed https://mcp.churnkey.co/mcp
TLS valid
Negotiated TLS 1.2 with TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=*.churnkey.co | CN=Amazon RSA 2048 M01,O=Amazon,C=US | 27 Mar 2026 | 10 Oct 2026 | RSA 2048 | SHA256-RSA | 1258e7bb03b70c5e61008aee6850037 |
| SANs: *.churnkey.co, churnkey.co | ||||||
| CN=Amazon RSA 2048 M01,O=Amazon,C=US (CA) | CN=Amazon Root CA 1,O=Amazon,C=US | 23 Aug 2022 | 23 Aug 2030 | RSA 2048 | SHA256-RSA | 77312380b9d6688a33b1ed9bf9ccda68e0e0f |
| CN=Amazon Root CA 1,O=Amazon,C=US (CA) | CN=Starfield Services Root Certificate Authority - G2,O=Starfield Technologies\, Inc.,L=Scottsdale,ST=Arizona,C=US | 25 May 2015 | 31 Dec 2037 | RSA 2048 | SHA256-RSA | 67f944a2a27cdf3fac2ae2b01f908eeb9c4c6 |
DNSSEC insecure
Validation of mcp.churnkey.co. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| co. | present | 7786 | 8 | Verified |
| churnkey.co. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication Enforced and verified
The endpoint asked for a token and published valid RFC 9728 metadata describing how to get one.
| Result | Enforced and verified |
|---|---|
| Enforced | On connection |
| HTTP status | 401 |
WWW-Authenticate challenge Bearer resource_metadata="https://mcp.churnkey.co/.well-known/oauth-protected-resource", scope="cancel_flows.blueprints.read cancel_flows.blueprints.write cancel_flows.metrics.read cancel_flows.sessions.read cancel_flows.adaptive_offers.read cancel_flows.adaptive_offers.write stripe_settings.read stripe_settings.write dns.read dns.write ab_test.read ab_test.write payment_recovery.metrics.read payment_recovery.blueprints.read payment_recovery.blueprints.write payment_recovery.campaigns.read payment_recovery.campaigns.write account.api_usage.read account.audit_log.read dsr.read"
Bearer resource_metadata="https://mcp.churnkey.co/.well-known/oauth-protected-resource", scope="cancel_flows.blueprints.read cancel_flows.blueprints.write cancel_flows.metrics.read cancel_flows.sessions.read cancel_flows.adaptive_offers.read cancel_flows.adaptive_offers.write stripe_settings.read stripe_settings.write dns.read dns.write ab_test.read ab_test.write payment_recovery.metrics.read payment_recovery.blueprints.read payment_recovery.blueprints.write payment_recovery.campaigns.read payment_recovery.campaigns.write account.api_usage.read account.audit_log.read dsr.read"| Header | Value |
|---|---|
| www-authenticate | Bearer resource_metadata="https://mcp.churnkey.co/.well-known/oauth-protected-resource", scope="cancel_flows.blueprints.read cancel_flows.blueprints.write cancel_flows.metrics.read cancel_flows.sessions.read cancel_flows.adaptive_offers.read cancel_flows.adaptive_offers.write stripe_settings.read stripe_settings.write dns.read dns.write ab_test.read ab_test.write payment_recovery.metrics.read payment_recovery.blueprints.read payment_recovery.blueprints.write payment_recovery.campaigns.read payment_recovery.campaigns.write account.api_usage.read account.audit_log.read dsr.read" |
Protected resource metadata
| Document | https://mcp.churnkey.co/.well-known/oauth-protected-resource |
|---|---|
| Retrieved | Yes |
| Resource | https://mcp.churnkey.co |
| Authorisation server | https://api.churnkey.co |
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://mcp.churnkey.co/mcp | Auth required | 401 | |
| http (plaintext) | http://mcp.churnkey.co/mcp | Inconclusive | 405 |
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.
No tool schema has been captured from this endpoint yet.
What is the co.churnkey/churnkey MCP server?
co.churnkey/churnkey is an MCP server listed in the public MCP registry as co.churnkey/churnkey. Read and manage Churnkey cancel flows, retention metrics, and payment recovery. This page covers its hosted endpoint (https://mcp.churnkey.co/mcp).
Is the co.churnkey/churnkey MCP server safe to use?
co.churnkey/churnkey scores 31 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.
Does the co.churnkey/churnkey MCP server require authentication?
Yes. co.churnkey/churnkey asked us for credentials when we connected, so you will need to authorise it in your MCP client before it can do anything.
Is the co.churnkey/churnkey MCP server still maintained?
co.churnkey/churnkey is still listed as active in the MCP registry. We last reached this channel on 23 August 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.