Customer Retention LTV

io.github.atul0016Published by GitHub account atul0016v0.1.1Updated Oct 24, 2026

Customer LTV, churn risk, repurchase, lifecycle email, and winback intelligence.

VerifiedSTDIODesktop onlyData & AnalyticsBusiness & Commerce

Overview

AI-generated overview

A local MCP server that gives an assistant customer lifetime value, churn risk, repurchase, lifecycle email, and winback intelligence.

What you can do
Customer Retention LTV is a local MCP server described as providing customer LTV, churn risk, repurchase, lifecycle email, and winback intelligence. The registry description lists these as its focus areas, but no tool list is published, so the exact operations an assistant can call are not documented. It runs as a local process over stdio rather than as a remote endpoint.
When to use it
Consider it when an assistant needs retention-oriented customer analytics, such as estimating lifetime value or churn risk, or supporting repurchase, lifecycle email, and winback work. Because no tool list is published, confirm the actual capabilities before relying on it.
Requirements
Runs locally over stdio, either via the PyPI package customer-retention-ltv-mcp with uvx or the Docker image atulhritik/customer-retention-ltv-mcp:0.1.0. A required license key must be supplied as the secret EARNALL_MCP_LICENSE_KEY. Optional variables are EARNALL_MCP_ACTIVATION_ID and EARNALL_MCP_LICENSE_API. Desktop only; no web execution.
Before you install
A required license key is requested as EARNALL_MCP_LICENSE_KEY, and an optional activation ID as EARNALL_MCP_ACTIVATION_ID; treat both as sensitive. The license is validated against an endpoint set by EARNALL_MCP_LICENSE_API, so license data leaves the machine. No tool list is published, so what data the server reads, writes, or sends onward cannot be verified from the listing.

Installation

In SourceWeft

  1. Open Customer Retention LTV in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.

Tools

0
SourceWeft has not started this package in its sandbox yet, so its tools are not known.

Version history

1
  1. v0.1.1LatestSep 16, 2026

Score

25% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 days25 pts

    Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.

  • Auth declared10 pts

    Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.

  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts

    Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.

  • License10 pts

    Declare a license in the repository or the registry entry.