First Party Data CRO

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

First-party funnel, rage-click, checkout, A/B test, and page-speed CRO intelligence.

VerifiedSTDIODesktop onlyData & Analytics

Overview

AI-generated overview

Local MCP server that gives an assistant first-party conversion-rate-optimization intelligence: funnel, rage-click, checkout, A/B test and page-speed data.

What you can do
  • The manifest lists no tools, so capabilities come from the registry description only.
  • It is described as providing first-party CRO intelligence covering funnel analysis.
  • It also covers rage-click detection, checkout behavior, A/B test results and page-speed findings.
  • It runs locally over stdio, so the assistant queries it as a local process rather than a hosted service.
When to use it
Worth considering when you want an assistant to reason about your own site's conversion data — drop-off in funnels, frustration signals like rage clicks, checkout friction, experiment results or page-speed issues — without sending that data to a hosted analytics service.
Requirements
A local runtime: run the PyPI package first-party-data-cro-mcp with uvx, or the Docker image atulhritik/first-party-data-cro-mcp:0.1.0, over stdio. A license key in EARNALL_MCP_LICENSE_KEY is required; optional EARNALL_MCP_ACTIVATION_ID and EARNALL_MCP_LICENSE_API configure the install ID and license validation endpoint. Desktop client only.
Before you install
Requires a purchased license key (EARNALL_MCP_LICENSE_KEY) obtained from the vendor's purchase page, and the server validates it against a license endpoint (EARNALL_MCP_LICENSE_API), so license and install identifiers leave your machine. The optional activation ID is described as a stable per-user/device identifier. No tools are listed, so what it can read or change in your data cannot be verified from the manifest.

Installation

In SourceWeft

  1. Open First Party Data CRO 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.