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

io.github.edholofy/eyepup

NPM · EYEPUP-MCP · 2 COMPONENTS · SCANNED AUG 3

Agentic visitor analytics — five tools that hand the next CRO fix to your coding agent.

Available components

remote · eyepup.com 66 npm · eyepup-mcp 59
+20 this week 59 Trust /100
Trust breakdown (6 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 →

Supply Chain Security87
  • No malware found by supply-chain analysis.Pass
  • Only part of the dependency tree could be resolved (95 of 99), so this covers what we could see, not the whole tree.Partial
  • No install/post-install scripts declared.Pass
  • Only part of the dependency tree could be resolved (95 of 99), so this covers what we could see, not the whole tree. View diagnostics → Partial
Provenance & Transparency19
  • Repository check failed: the declared repository URL returned HTTP 404. See how to fix → View diagnostics → Fail
  • Provenance check failed: no build-provenance attestation is published. See how to fix → View diagnostics → Fail
  • Clear OSI-approved license (MIT).Pass
  • Actively maintained (last published 89 days ago).Pass
  • Security-disclosure policy not yet verified: we couldn't inspect the source repository.Unverified
Schema Quality & AI Usability72
  • AI-judged instruction clarity (excellent).Pass
  • Context-footprint check failed: tool/resource definitions use about 719 tokens (~143/item across 5 items; 5 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
  • 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
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.

Install

Add this component to your MCP client. Where a client-specific snippet is available, pick your client below and copy it straight into your config; otherwise use the connection detail shown.

npm · eyepup-mcp

# add to Claude Code
claude mcp add edholofy-eyepup -- npx -y eyepup-mcp
# add to Codex CLI
codex mcp add edholofy-eyepup -- npx -y eyepup-mcp
// opencode.json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "edholofy-eyepup": {
      "type": "local",
      "command": [
        "npx",
        "-y",
        "eyepup-mcp"
      ],
      "enabled": true
    }
  }
}
# add to OpenClaw
openclaw mcp add edholofy-eyepup --command npx --arg -y --arg eyepup-mcp
# ~/.hermes/config.yaml
mcp_servers:
  edholofy-eyepup:
    command: "npx"
    args: ["-y", "eyepup-mcp"]
// mcp.json
{
  "mcpServers": {
    "edholofy-eyepup": {
      "command": "npx",
      "args": [
        "-y",
        "eyepup-mcp"
      ]
    }
  }
}
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.

  • 2 Aug 26 +59
    • Provenance: unverified → fail ▼ security
    • Install scripts: unverified → pass ▲ security
    • Known CVEs: unverified → partial ▲ security
    • Malware scan: unverified → pass ▲ security
    • Stability: Stability not yet verified: not enough scan history yet (needs a 30-day window). security
    • MCP protocol: unverified → pass ▲ functional
    • Dependency health: unverified → partial ▲ functional
    • Maintenance: unverified → pass ▲ functional
    • Schema quality: unverified → excellent ▲ functional
    • License: unverified → pass ▲ functional
    • Tool coverage: unverified → 100 ▲ functional
    • Licence: MIT functional
  • 1 Aug 26 −15
    • Tool coverage: 100 → unverified ▼ functional
    • First check of Schema quality: unverified functional
  • 31 Jul 26 −24
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 27 Jul 26 39

    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 3 Aug 2026 · Analysed npm/[email protected]

Provenance none

Ecosystem: npm · Outcome: none

Dependencies 95 packages

95 packages in the resolved dependency tree · 95 deprecated · 29 stale.

The dependency tree was only partially resolved, so these counts may be incomplete.

MCP tools — 5 exposed · ~719 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.

Tool Tokens
eyepup_ask ~183

Ask a natural-language question about your site visitors. Use this when the user asks 'why are people bouncing from /pricing', 'who's hot right now', 'what changed this week', or any other free-text question about visitor behaviour. Returns an LLM-grounded answer with evidence and ranked actions. Routes the question across visitor / funnel / anomaly buckets internally.

NameTypeReqDescription
daysinteger—Lookback window in days, 1-90. Default 7 if omitted.
questionstringyesThe free-text question. Examples: 'why are people bouncing from /pricing', 'who almost bought but didn't', 'what's the highest-impact friction pattern this week'.
sitestring—Optional apex domain to scope the question to one site (e.g. 'glp1watchdog.com'). Omit to span the whole team.

No output schema declared.

No examples provided.

eyepup_log ~213

Write back to Eyepup that you (or your coding agent) just shipped a change. The dossier agent reasons about every visitor profiled AFTER this log row, so it can grade whether the friction pattern recovered. CALL THIS after every UX edit, copy change, or pricing tweak — without the log, the agent has no idea what changed and the auto-loop stays open.

NameTypeReqDescription
descriptionstring—Longer notes the AI should weigh.
kindstring—What kind of change. Pick the most accurate — wrong kinds poison the dossier agent's reasoning. Default 'other'.
pathsstring—Comma-separated paths affected, e.g. '/pricing,/checkout'. Helps the agent scope the impact analysis.
sitestring—Apex domain — if you have multiple sites, scope the log.
titlestringyesOne-line headline of what shipped (5-120 chars). Examples: 'Rewrote /pricing CTA', 'Replaced annual/monthly toggle with two cards'.

No output schema declared.

No examples provided.

eyepup_todo ~124

Get the top friction patterns ranked by impact score. Use this BEFORE making any UX edit — the highest-impact pattern is usually a more valuable fix than whatever the user just asked about. Each row carries a paste-ready recommended_action you can ship as-is. Returns up to 25 patterns; the first row is the one to ship first.

NameTypeReqDescription
limitinteger—Max patterns to return. Default 5.
sitestring—Apex domain to filter to one site (e.g. 'glp1watchdog.com'). Omit for team-wide.

No output schema declared.

No examples provided.

eyepup_visitor ~109

Fetch the full LLM-written profile for a single visitor by distinct_id. Use this after eyepup_visitors_hot or eyepup_todo to dig into a specific visitor — heat reasoning, friction points, expressed desires, predicted next action, recent sessions. The distinct_id is a UUID-shaped string returned by the other tools.

NameTypeReqDescription
distinct_idstringyesThe visitor's distinct_id (UUID-shaped, returned by eyepup_visitors_hot or eyepup_todo).

No output schema declared.

No examples provided.

eyepup_visitors_hot ~90

Return the top high-intent visitors currently active. Use this when the user asks 'who's hot', 'who's about to convert', 'who should I focus on'. Each visitor row has a heat score, persona, and a one-line headline of what they did.

NameTypeReqDescription
limitinteger—Max visitors. Default 5.
sitestring—Apex domain filter.

No output schema declared.

No examples provided.