Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

io.github.GetUserProof/userproof

NPM · USERPROOF

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

Available components

0 this week 65 Trust /100

Last scanned (8 hours ago)

Scores higher than 32% of npm servers

Category Marketing and SEO

Trust breakdown (7 categories)

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 Security81
  • No malware found by supply-chain analysis.Pass
  • CVE check failed: a known high-severity CVE affects @modelcontextprotocol/sdk 1.26.0, a direct dependency. A fixed version is available. View diagnostics → Fail
  • No install/post-install scripts declared.Pass
  • 30 of 93 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency45
Schema Quality & AI Usability75
  • AI-judged instruction clarity (good).Pass
  • Tool/resource definitions use about 1205 tokens (~92/item across 13 items; 13 tools + 0 resources), lean.Pass
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management0
  • Stability not yet verified: not enough scan history yet (needs a 30-day window).Unverified
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 13 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 13 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

Unverified: 1 category

A category scored 0 because we could not verify it: a data source with nothing on this package, evidence we could not reach, or a check we could not run. We only credit what we can confirm.

Changelog

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.

  • 29 Oct 26 0
    • CVE-2026-118663 affects this package: high ▼ security
  • 28 Oct 26 +15
    • Malware scan: unverified → pass ▲ security
  • 27 Oct 26 50

    First indexed and scored.

Diagnostics

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 5 Nov 2026 · Analysed npm/userproof@3.3.0

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 →

Vulnerabilities 8 findings
ID CVE Severity Vector Fix available
GHSA-rmxm-3fg6-px4f CVE-2026-118663 medium CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N yes
GHSA-22jm-h49p-29qw CVE-2026-111767 high CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:L/A:L yes
GHSA-46jr-4wx8-v453 CVE-2026-111768 high CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H yes
GHSA-6prh-2h8m-c8cw CVE-2026-111769 medium CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:L/A:N yes
GHSA-6qxp-vccf-f47h CVE-2026-104850 high CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N yes
GHSA-f897-62hf-6gxq high CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H yes
GHSA-rvq5-wwqv-78pq CVE-2026-111771 medium CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:N yes
GHSA-mrhx-c7xc-m3w5 CVE-2023-54404 high CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H yes

Background: What a vulnerability scan can and cannot prove →

Dependencies 93 packages
Packages resolved 93
Stale 30
Tree resolution Complete

Background: SBOMs and build attestations, explained →

MCP tools · 13 exposed · ~1,205 tokens

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 →

Tool Tokens
check_coverage ~48

Which pages of this site are missing the UserProof snippet, from the sitemap. Free.

NameTypeReqDescription
freshboolean–Re-run now instead of reusing a check under 6 hours old

No output schema declared.

No examples provided.

check_fix ~127

Did a shipped fix work? Compares the finding's signal before and after the fix, the share of sessions that go on to a next step (click a control, use a form, open a second page), and conversion, the last two against untouched pages (difference-in-differences). Says 'inconclusive' when traffic is too thin. Free.

NameTypeReqDescription
finding_idstringyesFinding id the fix was recorded for
urlstring–Scan defects only: test this base URL instead of the live site, e.g. a local dev server running the fix

No output schema declared.

No examples provided.

fleet ~31

All your sites in one read: top fix or biggest leak per site, plus patterns that repeat across sites. Free.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

get_activation ~33

Onboarding milestones for this UserProof account and minutes from signup to each, including time to the first verified fix. Free.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

get_top_fix ~195

The single highest-impact fix on this site, with the sessions that prove it and the dollar math when a conversion event is set. Analyses are unlimited; plans are priced on recorded visits. If the result has a notice (visit limit near or passed), tell the user in one line and show any upgrade link on its own line. Free keeps 7 days of recordings: if the user asks about anything older or longer trends, tell them Pro and Scale keep 90 days and offer the upgrade tool. When no finding passes the evidence bar the result ends with a funnel read (biggest visible leak, entry pages, sources, coverage): present it as a lead, not proof, and never as a verified fix.

NameTypeReqDescription
domainstring–Read this site instead of the active one, e.g. example.com
site_idstring–Read this site id instead of the active one (from list_sites)

No output schema declared.

No examples provided.

get_usage ~33

The plan, recorded visits this month against its limit, sites against the site limit, and when the count resets. Free.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

list_sites ~26

List the sites on this UserProof account (id, domain, created date). Free.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

mark_fix_applied ~80

Record that a fix for a finding shipped, so check_fix can compare before and after. Call it once the change is live in production.

NameTypeReqDescription
finding_idstringyesFinding id from get_top_fix
fixed_atstring–ISO time the fix went live; defaults to now
notestring–What was changed

No output schema declared.

No examples provided.

scan_site ~95

Pre-traffic scan of the live site (read-only: no form posts): clicks what looks clickable, checks links and errors, and returns the one worst defect it can reproduce 3 of 3 times. Results are labelled as a scan, not visitor behaviour. Takes 1-3 minutes. Free, 10 a day per site.

NameTypeReqDescription
urlstring–Page to start from; defaults to the site's home page

No output schema declared.

No examples provided.

select_site ~78

Choose which UserProof site this project uses. With a site_id or domain it is validated against your account and returned so it can be saved to .userproof; with no argument it lists the sites. Free.

NameTypeReqDescription
domainstring–Domain, e.g. example.com
site_idstring–Site id from list_sites

No output schema declared.

No examples provided.

set_goal ~280

Set the one thing this site's visitors should do (book a call, start checkout, sign up). Findings then rank by what they cost it, and fixes are judged by it. Find candidates in the code first (Stripe/checkout links, signup forms, CTA button text) and confirm with the user. Free. The reply carries goal_check {status, matches, suggestions}: the goal is checked at once against real clicks from the last 14 days, else the live page. If status is no_match, the goal will count 0 conversions: do not leave it; pick the right text from suggestions (or the code) and call set_goal again in the same session. If unverified (no click data yet, page may be drawn by JavaScript), confirm the exact button text in the code.

NameTypeReqDescription
kindstringyesclick = a click whose text or selector contains match; page = visiting a path (exact, or a prefix ending in *)
matchesarrayyesButton texts exactly as rendered (e.g. ['Book a call', 'BOOK A CALL']) or paths (e.g. ['/thank-you', '/c/*'])
namestringyesPlain name, e.g. 'Book a call'
value_usdnumber–What one conversion is worth, if the user knows; enables dollar figures

No output schema declared.

No examples provided.

upgrade ~74

Get a checkout link to upgrade the UserProof plan (Pro $29/mo for 50,000 visits, Scale $99/mo for 250,000; both unlimited sites). Use when the user asks to upgrade or pay. Show the link on its own line.

NameTypeReqDescription
planstring–Defaults to the next plan up

No output schema declared.

No examples provided.

wait_for_first_event ~105

Confirm the UserProof snippet records: waits up to `wait` seconds for the first event from this site and says what arrived (page loads, clicks) and from where (live site, local dev server, or setup check). If nothing arrives it returns the likely cause. Free.

NameTypeReqDescription
sincestring–ISO time to count events from; defaults to 15 minutes ago
waitnumber–Seconds to wait, max 90; default 60

No output schema declared.

No examples provided.

Install

How do I install the io.github.GetUserProof/userproof MCP server?

io.github.GetUserProof/userproof runs locally as an npm package, launched with npx -y userproof. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

npm · userproof

# add to Claude Code
claude mcp add getuserproof-userproof -- npx -y userproof
Common questions

What is the io.github.GetUserProof/userproof MCP server?

io.github.GetUserProof/userproof is an MCP server listed in the public MCP registry as io.github.GetUserProof/userproof. The top conversion fix from real visitor sessions, with file and line, checked after you ship. This page covers its npm package (userproof).

Is the io.github.GetUserProof/userproof MCP server safe to use?

io.github.GetUserProof/userproof scores 65 out of 100 on VerifyMCP. We recorded 8 known advisories against it as of 5 November 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 io.github.GetUserProof/userproof MCP server expose?

io.github.GetUserProof/userproof exposes 13 tools: list_sites, select_site, get_top_fix, fleet, mark_fix_applied, and 8 more. Their descriptions and schemas cost roughly 1,205 tokens of context every time the server is loaded.

Is the io.github.GetUserProof/userproof MCP server still maintained?

io.github.GetUserProof/userproof is still listed as active in the MCP registry. We last reached this channel on 5 November 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 io.github.GetUserProof/userproof MCP server under?

io.github.GetUserProof/userproof declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.