Skip to content

io.github.edholofy/eyepup

by edholofy · remote · local (npm) · no sign-in to list tools · v0.1.1 · published by GitHub user edholofy

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

Changes · 1
CompareRegistry entry

5 tools: 1 change things and 4 only read.

Scanned Oct 21, 2026

No check matched anything in the tool definitions. No finding is not a safety guarantee. How the checks work.

claude mcp add --transport http eyepup https://eyepup.com/mcp

Tools

Open a tool for its reasons and full description. Descriptions are the publisher's own words, shown as they are.

5 tools

Changes things 1Claude Code: ask
  • eyepup_askAsk a natural-language question about your site visitors.No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    Description, as the server wrote it
    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.
Only reads 4Claude Code: allow
  • eyepup_logLog a change you just shipped.No findings

    Why it is in this group

    • The name "eyepup_log" says "log": a word for reading.
    Description, as the server wrote it
    Log a change you just shipped. 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.
  • eyepup_todoGet the top friction patterns ranked by impact score.No findings

    Why it is in this group

    • The description's first verb is "get": a word for reading.
    Description, as the server wrote it
    Get the top friction patterns ranked by impact score. Use 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.
  • eyepup_visitorFetch the full LLM-written profile for a single visitor by distinct_id.No findings

    Why it is in this group

    • The description's first verb is "fetch": a word for reading.
    Description, as the server wrote it
    Fetch the full LLM-written profile for a single visitor by distinct_id. Use after eyepup_visitors_hot or eyepup_todo to dig into a specific visitor.
  • eyepup_visitors_hotReturn the top high-intent visitors currently active.No findings

    Why it is in this group

    • The description's first verb is "return": a word for reading.
    Description, as the server wrote it
    Return the top high-intent visitors currently active. Use when the user asks 'who's hot', 'who's about to convert', 'who should I focus on'.

This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.

Exfil surface

Which tools read private data, which read text someone else can write, and which can send data out. One of each is a path a prompt injection can use.

No private-data, untrusted-input, outbound path in this server alone: no tool is tagged private-data or untrusted-input or outbound.

Reads private data0
Reads files, mail, messages, databases, secrets, calendars or repositories.
Reads text others write0
Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
Can send data out0
Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.

Other servers in the same agent add their own tools to these paths. Audit your whole setup to see them together.

Install

Pinned to version 0.1.1. Values in angle brackets are yours to fill in.

claude mcp add --transport http eyepup https://eyepup.com/mcp

Run in a terminal.

Claude Code permissions

Allow the reads, ask before a change or a way out, deny the deletes. Paste into .claude/settings.json.

.claude/settings.json
{
  "permissions": {
    "allow": [
      "mcp__eyepup__eyepup_todo",
      "mcp__eyepup__eyepup_visitors_hot",
      "mcp__eyepup__eyepup_visitor",
      "mcp__eyepup__eyepup_log"
    ],
    "ask": [
      "mcp__eyepup__eyepup_ask"
    ],
    "deny": []
  }
}

Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. A read that can send data out (it takes a URL, say) asks first too. It assumes the server is installed as eyepup. Review it before you use it.