Userproof

io.github.GetUserProofPublished by GitHub account GetUserProofv3.3.0Updated Oct 29, 2026

The top conversion fix from real visitor sessions, with file and line, checked after you ship.

VerifiedSTDIODesktop onlyDeveloper ToolsData & Analytics

Overview

AI-generated overview

UserProof surfaces the top conversion fix from real visitor sessions, with file and line, and checks whether it worked after you ship.

What you can do
  • Report the highest-impact conversion fix suggested by real visitor sessions, pointing to the file and line to change.
  • Re-check after deployment whether the fix actually improved results.
  • Set up the project: create the account, add the tracking snippet to the site, and confirm it records.
  • Run a review from the coding agent to get the current top fix.
When to use it
Useful when you maintain a website and want an agent to turn real visitor behavior into a concrete, located code change, then verify the outcome after shipping. Aimed at Claude Code, Codex and Cursor users working on a project with a live site.
Requirements
Runs locally over stdio as a Node.js 18+ process, installed as a Claude Code plugin or via npx from the GitHub repository; no npm install needed. Needs a UserProof account and an API key, supplied through the USERPROOF_API_KEY environment variable or the key file at ~/.config/userproof/key. Network access to the UserProof API and ingest endpoints.
Before you install
Setup creates an account and sends your email and site domain to the vendor, and the tracking snippet sends visitor behavior (page views, clicks, scrolls, errors) to the vendor's ingest endpoint. The API key is a secret stored in a local key file. Setup modifies your site by adding a tracking snippet, so review that change before shipping.

Installation

In SourceWeft

  1. Open Userproof 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.

Other MCP clients

Follow the launch instructions in the repository.

README

UserProof for Claude Code, Codex and Cursor

UserProof shows you the one fix your real visitors are begging for, with the file and line, then checks whether it worked after you ship. https://getuserproof.com

Install

/plugin marketplace add GetUserProof/userproof/plugin install userproof@userproof/userproof:setup

Codex

codex mcp add userproof -- npx -y github:GetUserProof/userproofcodex "Read https://getuserproof.com/setup.md and follow it to set up UserProof for this project."

Cursor

Add to ~/.cursor/mcp.json under mcpServers:

json
"userproof": { "command": "npx", "args": ["-y", "github:GetUserProof/userproof"] }

Then ask the agent: "Read https://getuserproof.com/setup.md and follow it to set up UserProof for this project."

Setup creates your account, adds the tracking snippet to your site, and proves it records. After a Claude Code restart (or /mcp reconnect) run /userproof:review for the top fix.

What data it collects

  • Your email and site domain, sent to api.getuserproof.com at signup.
  • Visitor behavior on your site (page views, clicks, scrolls, errors) sent by the snippet to ingest.getuserproof.com.
  • The plugin itself reads only .userproof in your repo and your API key. The key is stored in ~/.config/userproof/key (mode 600). It does not upload your source code.

No npm install is needed: the MCP server ships inside the plugin as one file (plugin/mcp/server.mjs, also run by npx github:GetUserProof/userproof) and needs Node 18+.

Source: README.md at commit 548d0cd

Tools

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

Version history

1
  1. v3.3.0LatestOct 29, 2026

Score

50% 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
  • License10 pts