# io.github.edholofy/eyepup (remote · eyepup.com)

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

- Trust score: 66/100 (medium)
- Change this week: +5
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-08-03

## Components

- remote · `eyepup.com`: 66/100 (this document), [markdown](https://verifymcp.io/servers/edholofy-eyepup/eyepup.md), [page](https://verifymcp.io/servers/edholofy-eyepup/eyepup)
- npm · `eyepup-mcp`: 59/100, [markdown](https://verifymcp.io/servers/edholofy-eyepup/eyepup-mcp.md), [page](https://verifymcp.io/servers/edholofy-eyepup/eyepup-mcp)

## Channel facts

- Endpoint: `https://eyepup.com/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `0.1.1`

## Trust breakdown

How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-08-03.

- **Endpoint Security**: 63/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - Authorisation not fully verified: no authorisation is required to call this server, and 5 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe.
  - HTTPS is enforced; there's no plaintext access path.
  - The HSTS (Strict-Transport-Security) header is present.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 66/100
  - AI-judged instruction clarity (good).
  - Tool/resource definitions use about 400 tokens (~80/item across 5 items; 5 tools + 0 resources), lean.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 27/100
  - Stability observed for 8 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 87/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 62% of tool parameters carry a description.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

## Install

### Claude

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

### Codex

```toml
[mcp_servers.edholofy-eyepup]
url = "https://eyepup.com/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "edholofy-eyepup": {
      "type": "remote",
      "url": "https://eyepup.com/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add edholofy-eyepup --url https://eyepup.com/mcp --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  edholofy-eyepup:
    url: "https://eyepup.com/mcp"
```

### Other

```json
{
  "mcpServers": {
    "edholofy-eyepup": {
      "type": "http",
      "url": "https://eyepup.com/mcp"
    }
  }
}
```

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-08-02 (score 66, +1)

No change was recorded against any check on this day. Stability & Change Management went from 20 to 23. That category is still filling its 30-day observation window: 6 days of observed history at the previous scan, 7 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-07-31 (score 65, +2)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-07-30 (score 63, +1)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-07-28 (score 62, +1)

No change was recorded against any check on this day. Stability & Change Management went from 3 to 7. That category is still filling its 30-day observation window: 1 days of observed history at the previous scan, 2 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-07-27 (score 61, +1)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-07-26 (score 60)

First indexed and scored.

## MCP tools (5)

### `eyepup_ask` (~109 tokens)

Ask Eyepup about your visitors

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.

Input parameters:

- `days` (integer): Lookback days (default 7).
- `question` (string, required): The free-text question.
- `site` (string): Optional apex domain to scope.

### `eyepup_todo` (~78 tokens)

List the friction-pattern To-Do queue

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.

Input parameters:

- `limit` (integer): Max patterns (default 5).
- `site` (string): Apex-domain scope.

### `eyepup_visitors_hot` (~60 tokens)

Top high-intent visitors right now

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'.

Input parameters:

- `limit` (integer)
- `site` (string)

### `eyepup_visitor` (~59 tokens)

Get the full dossier for one 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.

Input parameters:

- `distinct_id` (string, required): UUID-shaped distinct_id.

### `eyepup_log` (~94 tokens)

Log a change you just shipped

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.

Input parameters:

- `description` (string)
- `kind` (string)
- `paths` (string): Comma-separated paths affected.
- `site` (string)
- `title` (string, required): One-line headline of what shipped.

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/edholofy-eyepup/eyepup#diagnostics

## Score history

- 2026-08-03: 66
- 2026-08-02: 66
- 2026-08-01: 65
- 2026-07-31: 65
- 2026-07-30: 63
- 2026-07-29: 62
- 2026-07-28: 62
- 2026-07-27: 61
- 2026-07-26: 60

## Links

- Remote endpoint: https://eyepup.com/mcp
- Website: https://eyepup.com/mcp-analytics
- Changelog RSS feed: https://verifymcp.io/servers/edholofy-eyepup/eyepup/changelog.xml
- Changelog JSON feed: https://verifymcp.io/servers/edholofy-eyepup/eyepup/changelog.json
- HTML version of this page: https://verifymcp.io/servers/edholofy-eyepup/eyepup