Official MCP RegistryListed
io.github.edholofy/eyepup
Agentic visitor analytics — five tools that hand the next CRO fix to your coding agent.
First seen 2 Oct 2026. Evidence as of 9 Oct 2026.
5
Tools
From an anonymous probe
1
Source listings
Each with its own history
0
Recorded changes
Since first seen
Tools
| Tool | Description | Behaviour |
|---|---|---|
| eyepup_ask | 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. | Not declared |
| eyepup_log | 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. | Not declared |
| eyepup_todo | 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. | Not declared |
| eyepup_visitor | 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. | Not declared |
| eyepup_visitors_hot | 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'. | Not declared |
Change history
No changes since the first observation. The first snapshot is the baseline.
| Source | Listing | First seen | Last seen | Versions |
|---|---|---|---|---|
| Official MCP Registry | io.github.edholofy/eyepup | 2 Oct 2026 | 9 Oct 2026 | 1 |