io.github.edholofy/eyepup
NPM · EYEPUP-MCP · 2 COMPONENTS · SCANNED SEP 20
Agentic visitor analytics — five tools that hand the next CRO fix to your coding agent.
Available components
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 Security98
- No malware found by supply-chain analysis.Pass
- No known CVEs affecting this package version or its production dependencies.Pass
- No install/post-install scripts declared.Pass
- 31 of 96 dependencies flagged as unhealthy. 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 137 days ago).Pass
- Security-disclosure policy not yet verified: we couldn't inspect the source repository.Unverified
Schema Quality & AI Usability75
- 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 Management90
- Stability observed for 27 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
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 5 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 5 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
How do I install the io.github.edholofy/eyepup MCP server?
io.github.edholofy/eyepup runs locally as an npm package, launched with npx -y eyepup-mcp. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
npm · eyepup-mcp
claude mcp add edholofy-eyepup -- npx -y eyepup-mcp
{
"mcpServers": {
"edholofy-eyepup": {
"command": "npx",
"args": [
"-y",
"eyepup-mcp"
]
}
}
} {
"servers": {
"edholofy-eyepup": {
"command": "npx",
"args": [
"-y",
"eyepup-mcp"
]
}
}
} codex mcp add edholofy-eyepup -- npx -y eyepup-mcp
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"edholofy-eyepup": {
"type": "local",
"command": [
"npx",
"-y",
"eyepup-mcp"
],
"enabled": true
}
}
} openclaw mcp add edholofy-eyepup --command npx --arg -y --arg eyepup-mcp
mcp_servers:
edholofy-eyepup:
command: "npx"
args: ["-y", "eyepup-mcp"] {
"McpServers": {
"edholofy-eyepup": {
"Transport": "stdio",
"Command": "npx",
"Arguments": [
"-y",
"eyepup-mcp"
]
}
}
} assistant mcp add edholofy-eyepup -t stdio -c npx -a -y eyepup-mcp
{
"mcpServers": {
"edholofy-eyepup": {
"command": "npx",
"args": [
"-y",
"eyepup-mcp"
]
}
}
} 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.
- 19 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 83 to 87. That category is still filling its 30-day observation window: 25 days of observed history at the previous scan, 26 at this one. The score rises as the window fills, whether or not the server changes.
- 17 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 77 to 80. That category is still filling its 30-day observation window: 23 days of observed history at the previous scan, 24 at this one. The score rises as the window fills, whether or not the server changes.
- 16 Sept 26 −4
- Stability: pass → 0.77 functional
- 15 Sept 26 +1
- Stability: 0.97 → pass security
- 13 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 90 to 93. That category is still filling its 30-day observation window: 27 days of observed history at the previous scan, 28 at this one. The score rises as the window fills, whether or not the server changes.
- 11 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 83 to 87. That category is still filling its 30-day observation window: 25 days of observed history at the previous scan, 26 at this one. The score rises as the window fills, whether or not the server changes.
- 10 Sept 26 −3
- Stability: pass → 0.83 functional
- 9 Sept 26 +1
- Stability: 0.97 → pass security
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 20 Sept 2026 · Analysed npm/eyepup-mcp@0.1.1
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 →
Dependencies 96 packages
| Packages resolved | 96 |
|---|---|
| Stale | 31 |
| Tree resolution | Complete |
Background: SBOMs and build attestations, explained →
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 →
eyepup_ask Ask Eyepup about your visitors ~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.
| Name | Type | Req | Description |
|---|---|---|---|
| days | integer | – | Lookback window in days, 1-90. Default 7 if omitted. |
| question | string | yes | The 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'. |
| site | string | – | 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 Log a change you just shipped ~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.
| Name | Type | Req | Description |
|---|---|---|---|
| description | string | – | Longer notes the AI should weigh. |
| kind | string | – | What kind of change. Pick the most accurate — wrong kinds poison the dossier agent's reasoning. Default 'other'. |
| paths | string | – | Comma-separated paths affected, e.g. '/pricing,/checkout'. Helps the agent scope the impact analysis. |
| site | string | – | Apex domain — if you have multiple sites, scope the log. |
| title | string | yes | One-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 List the friction-pattern To-Do queue ~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.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | Max patterns to return. Default 5. |
| site | string | – | Apex domain to filter to one site (e.g. 'glp1watchdog.com'). Omit for team-wide. |
No output schema declared.
No examples provided.
eyepup_visitor Get the full dossier for one 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.
| Name | Type | Req | Description |
|---|---|---|---|
| distinct_id | string | yes | The visitor's distinct_id (UUID-shaped, returned by eyepup_visitors_hot or eyepup_todo). |
No output schema declared.
No examples provided.
eyepup_visitors_hot List the hottest visitors right now ~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.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | Max visitors. Default 5. |
| site | string | – | Apex domain filter. |
No output schema declared.
No examples provided.
What is the io.github.edholofy/eyepup MCP server?
io.github.edholofy/eyepup is an MCP server listed in the public MCP registry as io.github.edholofy/eyepup. Agentic visitor analytics, five tools that hand the next CRO fix to your coding agent. This page covers its npm package (eyepup-mcp).
Is the io.github.edholofy/eyepup MCP server safe to use?
io.github.edholofy/eyepup scores 77 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 20 September 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.edholofy/eyepup MCP server expose?
io.github.edholofy/eyepup exposes 5 tools: eyepup_ask, eyepup_todo, eyepup_visitors_hot, eyepup_visitor, eyepup_log. Their descriptions and schemas cost roughly 719 tokens of context every time the server is loaded.
Is the io.github.edholofy/eyepup MCP server still maintained?
io.github.edholofy/eyepup is still listed as active in the MCP registry. We last reached this channel on 20 September 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.edholofy/eyepup MCP server under?
io.github.edholofy/eyepup declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.