# io.github.Dan-Cleary/convalytics (remote · api.convalytics.dev)

Read-only analytics for Convex apps, queryable via MCP from Claude, Cursor, and other clients.

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

## Components

- remote · `api.convalytics.dev`: 64/100 (this document), [markdown](https://verifymcp.io/servers/dan-cleary-convalytics/api.md), [page](https://verifymcp.io/servers/dan-cleary-convalytics/api)

## Channel facts

- Endpoint: `https://api.convalytics.dev/mcp`
- Transports: `streamable-http`
- Auth: `required`
- Version: `1.0.0`

## 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**: 57/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - Authorisation not fully verified: this server exposes a tool marked destructive (delete_funnel) and its handshake is open, but we could not confirm whether a tool call is gated, so we do not assert it is callable unauthenticated.
  - HTTPS is enforced; there's no plaintext access path.
  - HSTS check failed: the Strict-Transport-Security header is absent.
  - 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**: 71/100
  - AI-judged instruction clarity (excellent).
  - Context-footprint check failed: tool/resource definitions use about 2011 tokens (~134/item across 15 items; 15 tools + 0 resources), over budget; trim descriptions and params.
  - 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**: 95/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 85% of tool parameters carry a description.
- **Capabilities**: 60/100
  - Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28.

## Install

### Claude

```bash
claude mcp add --transport http dan-cleary-convalytics https://api.convalytics.dev/mcp
```

### Codex

```toml
[mcp_servers.dan-cleary-convalytics]
url = "https://api.convalytics.dev/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "dan-cleary-convalytics": {
      "type": "remote",
      "url": "https://api.convalytics.dev/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add dan-cleary-convalytics --url https://api.convalytics.dev/mcp --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  dan-cleary-convalytics:
    url: "https://api.convalytics.dev/mcp"
```

### Other

```json
{
  "mcpServers": {
    "dan-cleary-convalytics": {
      "type": "http",
      "url": "https://api.convalytics.dev/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-03 (score 64, +1)

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

### 2026-08-01 (score 63, +1)

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

### 2026-07-31 (score 62, 0)

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

### 2026-07-30 (score 62, −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 63, +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 62, +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 61)

First indexed and scored.

## MCP tools (15)

### `list_projects` (~38 tokens)

List all Convalytics projects on the team this token belongs to. Useful when the agent needs to confirm the project it's querying against. No arguments.

### `get_usage` (~29 tokens)

Return the current month's custom-event usage, monthly quota, retention days, and plan name for the team.

### `top_pages` (~200 tokens)

Return the top pages for a specific project, ranked by views in a time window. Default window is the last 7 days. Use list_projects first if you don't know the project name. Returns path, views, uniqueVisitors, and percentage of total views for each page. Pass `user` to see pages a specific visitor hit.

Input parameters:

- `limit` (number): Maximum number of pages to return. Default 20, max 50.
- `project` (string, required): Project name (case-insensitive, e.g. 'slopbench') or project id from list_projects.
- `since` (number): Start of window as unix milliseconds. Defaults to 7 days ago.
- `until` (number): End of window as unix milliseconds. Defaults to now.
- `user` (string): Optional. Filter to one visitor/user. Accepts userEmail (case-insensitive) or visitorId (exact). For the full per-user snapshot prefer user_activity.

### `top_referrers` (~137 tokens)

Return the top referring hosts for a specific project, ranked by visit count in a time window. Includes '(direct)' for visits with no referrer. Default window is the last 7 days.

Input parameters:

- `limit` (number): Maximum number of referrers to return. Default 10, max 50.
- `project` (string, required): Project name (case-insensitive, e.g. 'slopbench') or project id from list_projects.
- `since` (number): Start of window as unix milliseconds. Defaults to 7 days ago.
- `until` (number): End of window as unix milliseconds. Defaults to now.

### `pageviews_count` (~183 tokens)

Count page views for a specific project in a time window. Page views are the automatic hits captured by the browser script tag (separate from custom events). Use this for web-traffic questions like 'how many pageviews in the last 24 hours'. Default window is the last 7 days. Pass `user` to scope to one visitor.

Input parameters:

- `project` (string, required): Project name (case-insensitive, e.g. 'slopbench') or project id from list_projects.
- `since` (number): Start of window as unix milliseconds. Defaults to 7 days ago.
- `until` (number): End of window as unix milliseconds. Defaults to now.
- `user` (string): Optional. Filter to one visitor/user. Accepts userEmail (case-insensitive) or visitorId (exact). For the full per-user snapshot prefer user_activity.

### `events_count` (~246 tokens)

Count CUSTOM PRODUCT events for a specific project in a time window, optionally filtered to one event name and/or one user. Custom events are emitted by explicit analytics.track() calls in app code (signup_completed, payment_succeeded, etc.). This does NOT count page views — use pageviews_count or weekly_digest for those. Returns count, unique visitors, and a `truncated` flag if the scan hit the maximum scan size.

Input parameters:

- `name` (string): Optional event name to filter by (e.g. 'signup_completed'). If omitted, counts all custom events in the window. Do NOT pass 'page_view' here — page views are in a separate table.
- `project` (string, required): Project name (case-insensitive, e.g. 'slopbench') or project id from list_projects.
- `since` (number): Start of window as unix milliseconds. Defaults to 7 days ago.
- `until` (number): End of window as unix milliseconds. Defaults to now.
- `user` (string): Optional. Filter to one visitor/user. Accepts userEmail (case-insensitive) or visitorId (exact). For the full per-user snapshot prefer user_activity.

### `recent_events` (~201 tokens)

Return the most recent custom events for a specific project, optionally filtered to one event name and/or one user. PII (userEmail, userName, props) is redacted by default; pass redact: false to include them.

Input parameters:

- `limit` (number): Maximum number of events to return. Default 20, max 100.
- `name` (string): Optional event name to filter by (e.g. 'signup_completed'). Omit to return events of any name.
- `project` (string, required): Project name (case-insensitive, e.g. 'slopbench') or project id from list_projects.
- `redact` (boolean): If true (default), userEmail/userName are null and props is {}. Set to false to include them.
- `user` (string): Optional. Filter to one visitor/user. Accepts userEmail (case-insensitive) or visitorId (exact). For the full per-user snapshot prefer user_activity.

### `user_activity` (~241 tokens)

Composite snapshot of a specific user's activity on a project. Returns an identity block (visitorId, userEmail, userName, firstSeen, lastSeen), total pageviews, total custom events, session count, top pages this user visited, their most-fired event names, and their 20 most recent events with props. Use this for 'how is dancleary54@gmail.com using my app?' style questions — one call, full picture. For ad-hoc drill-down (just a count, just recent events) pass `user` to the individual tools instead. Default window is the last 7 days.

Input parameters:

- `project` (string, required): Project name (case-insensitive, e.g. 'slopbench') or project id from list_projects.
- `since` (number): Start of window as unix milliseconds. Defaults to 7 days ago.
- `until` (number): End of window as unix milliseconds. Defaults to now.
- `user` (string, required): User identifier. Accepts userEmail (case-insensitive, e.g. 'dan@example.com') or visitorId (the exact string passed as userId on the original track() call).

### `weekly_digest` (~183 tokens)

Composite snapshot of a project's web analytics over a lookback window. Returns unique visitors, pageviews, sessions, bounce rate, average session duration, top 5 pages, top 5 referrers, total custom events, and top 5 event names. Includes period-over-period comparison against the prior equal-length window unless compare: false. Prefer this over chaining top_pages + top_referrers + events_count when the agent just wants to report on the week.

Input parameters:

- `compare` (boolean): Include period-over-period comparison against the prior equal-length window. Default true. Set false for faster response when only current numbers matter.
- `days` (number): Lookback window in days, 1 to 90. Default 7.
- `project` (string, required): Project name (case-insensitive, e.g. 'slopbench') or project id from list_projects.

### `list_funnels` (~79 tokens)

List active funnels defined on a project. A funnel is a saved ordered sequence of steps (events or pageview paths) that Convalytics computes step-by-step conversion for. Soft-deleted funnels are excluded.

Input parameters:

- `project` (string, required): Project name (case-insensitive, e.g. 'slopbench') or project id from list_projects.

### `get_funnel` (~48 tokens)

Return the full definition of one funnel by id: name, description, ordered steps, and conversion window.

Input parameters:

- `funnelId` (string, required): Funnel id from list_funnels or create_funnel.

### `create_funnel` (~186 tokens)

Create a new funnel on a project. Steps are 2–10 ordered events or pageview paths. conversionWindowMs caps how long a visitor has between consecutive steps (default 7 days); this is the step-to-step limit, without which a funnel is just event co-occurrence. Returns { id } on success.

Input parameters:

- `conversionWindowMs` (number): Max ms between consecutive steps. Default 7 days (604800000). Bounds: 60000 (1 min) to 7776000000 (90 days).
- `description` (string): Optional longer description.
- `name` (string, required): Human-readable name.
- `project` (string, required): Project name (case-insensitive, e.g. 'slopbench') or project id from list_projects.
- `steps` (array, required): Ordered list of 2–10 steps. Visitors must hit them in order.

### `update_funnel` (~72 tokens)

Patch an existing funnel. Any subset of name/description/steps/conversionWindowMs. Refuses updates on deleted funnels.

Input parameters:

- `conversionWindowMs` (number)
- `description` (string)
- `funnelId` (string, required)
- `name` (string)
- `steps` (array)

### `delete_funnel` (~70 tokens)

Soft delete a funnel. The row is retained with status='deleted' and excluded from list/get/compute. Idempotent — calling twice is a no-op. Use if the funnel is obsolete; the record is kept for audit and cannot be undone from MCP.

Input parameters:

- `funnelId` (string, required)

### `compute_funnel` (~98 tokens)

Run a funnel over a time window and return per-step visitor count, conversion from previous step, conversion from start, and average time to convert between steps. Returns `truncated` flags if the scan cap was hit.

Input parameters:

- `funnelId` (string, required)
- `since` (number): Start of window as unix milliseconds. Defaults to 7 days ago.
- `until` (number): End of window as unix milliseconds. Defaults to now.

## Diagnostics

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

## Score history

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

## Links

- Remote endpoint: https://api.convalytics.dev/mcp
- Authorisation metadata: https://api.convalytics.dev/.well-known/oauth-protected-resource/mcp
- Repository: https://github.com/Dan-Cleary/convalytics
- Website: https://convalytics.dev/mcp
- Changelog RSS feed: https://verifymcp.io/servers/dan-cleary-convalytics/api/changelog.xml
- Changelog JSON feed: https://verifymcp.io/servers/dan-cleary-convalytics/api/changelog.json
- HTML version of this page: https://verifymcp.io/servers/dan-cleary-convalytics/api