# Staats (remote · api.staats.ai)

Cookieless web analytics your coding agent reads: traffic answers, deploy impact, what broke.

- Trust score: 76/100 (medium)
- Change this week: +3
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-09-25

> **Recent critical change**: Authorization (2026-09-09). See the changelog below before you install this server.

## Components

- remote · `api.staats.ai`: 76/100 (this document), [markdown](https://verifymcp.io/servers/mrviolets-staats/functions-v1-mcp.md), [page](https://verifymcp.io/servers/mrviolets-staats/functions-v1-mcp)

## Channel facts

- Endpoint: `https://api.staats.ai/functions/v1/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `1.0.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-09-25.

- **Endpoint Security**: 63/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - Authorisation check failed: no authorisation is required to call this server, and it exposes a tool marked destructive (update_site_context).
  - 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**: 71/100
  - AI-judged instruction clarity (excellent).
  - Context-footprint check failed: tool/resource definitions use about 2501 tokens (~166/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**: 73/100
  - Stability observed for 22 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
  - Structured output schemas are declared (100% of tools); any adoption earns full credit.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - All 1 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation.
  - An AI judge read all 16 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

## Install

### How do I install the Staats MCP server?

Staats is a hosted endpoint at https://api.staats.ai/functions/v1/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

### Claude

```bash
claude mcp add --transport http mrviolets-staats 'https://api.staats.ai/functions/v1/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "mrviolets-staats": {
      "url": "https://api.staats.ai/functions/v1/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "mrviolets-staats": {
      "type": "http",
      "url": "https://api.staats.ai/functions/v1/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.mrviolets-staats]
url = "https://api.staats.ai/functions/v1/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "mrviolets-staats": {
      "type": "remote",
      "url": "https://api.staats.ai/functions/v1/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add mrviolets-staats --url 'https://api.staats.ai/functions/v1/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  mrviolets-staats:
    url: "https://api.staats.ai/functions/v1/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "mrviolets-staats": {
      "Transport": "http",
      "Url": "https://api.staats.ai/functions/v1/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add mrviolets-staats -t streamable-http -u 'https://api.staats.ai/functions/v1/mcp'
```

### Other

```json
{
  "mcpServers": {
    "mrviolets-staats": {
      "type": "http",
      "url": "https://api.staats.ai/functions/v1/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-09-25 (score 76, 0)

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

### 2026-09-24 (score 76, +1)

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

### 2026-09-22 (score 75, +1)

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

### 2026-09-20 (score 74, +1)

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

### 2026-09-17 (score 73, +1)

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

### 2026-09-15 (score 72, +1)

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

### 2026-09-13 (score 71, +1)

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

### 2026-09-11 (score 70, +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.

## MCP tools (15)

### `get_site_context` (~119 tokens)

Get site context

What a site is and what the owner wants from it, plus its data-retention settings. Well-known keys: description, goals, audience, notes (open agenda items to check at session start and clear when handled), events (event name -> meaning), funnel (canonical conversion steps). Read this before making recommendations.

Input parameters:

- `site` (string): the site's data-site code, from its script tag or list_sites. Omit when the account has a single site. In a tracked project, read the code from the script tag before asking the user.

Output parameters:

- `context` (object)
- `domain` (string)
- `hint` (string)
- `name` (string)
- `retention` (object)
- `site` (string)

### `update_site_context` (~269 tokens)

Update site context

Save or amend what a site is for. Provided context fields are merged into the existing context (events merges per entry); a null value deletes its key. name/domain update the site record itself.

Input parameters:

- `audience`: who the site is for; null deletes
- `description`: what the site is; null deletes
- `domain` (string): update the site's domain
- `events` (object): map of event name -> one-line meaning; record one whenever you add tracking. null deletes an entry.
- `funnel`: the site's canonical conversion steps, same shape as the funnel tool's steps. null clears it.
- `goals`: what the owner wants from it; null deletes
- `name` (string): update the site's display name
- `notes`: open agenda items to check at session start; null deletes
- `retention_days` (integer): shorten this site's data retention below the plan default; 0 restores plan-default retention. DESTRUCTIVE: shortening schedules permanent deletion of older events at the nightly prune. Confirm with t…
- `site` (string): the site's data-site code, from its script tag or list_sites. Omit when the account has a single site. In a tracked project, read the code from the script tag before asking the user.

Output parameters:

- `context` (object)
- `domain` (string)
- `name` (string)
- `retention` (object)
- `site` (string)
- `updated` (boolean)

### `what_changed` (~130 tokens)

What changed

Notable movements in the period without scanning raw numbers: statistically unusual traffic days, referrer surges and first-time referrers, pages whose share of traffic jumped, alongside the annotations recorded in the same period. period: '7d' default.

Input parameters:

- `period` (string): relative period like '24h', '7d' (default), '4w'
- `site` (string): the site's data-site code, from its script tag or list_sites. Omit when the account has a single site. In a tracked project, read the code from the script tag before asking the user.

Output parameters:

- `annotations` (array)
- `findings` (array)
- `note` (string)
- `period` (object)
- `site` (string)

### `what_broke` (~193 tokens)

What broke

Signs of visitors hitting problems in the period: JS errors the tracker captured (new_error, error_spike: each with a sanitized sample message, source, line, affected visitor count, and the nearest annotation, i.e. the deploy that most plausibly introduced it), plus behavioral friction: pairs of pages people bounce between without progressing (nav_loop) and pages reloaded repeatedly in quick succession (refresh_burst). Findings clear statistical floors, so an empty result is meaningful: nothing looks broken. Check it after every deploy. period: '7d' default.

Input parameters:

- `period` (string): relative period like '24h', '7d' (default), '4w'
- `site` (string): the site's data-site code, from its script tag or list_sites. Omit when the account has a single site. In a tracked project, read the code from the script tag before asking the user.

Output parameters:

- `annotations` (array)
- `error_capture` (string)
- `findings` (array)
- `note` (string)
- `note_errors` (string)
- `period` (object)
- `site` (string)
- `total_error_events` (number)

### `get_overview` (~167 tokens)

Site overview

Traffic pulse: visitor/pageview totals vs the previous period, top pages, top referrers, and a per-day series. period: relative like '24h', '7d' (default), '4w'. Includes quota status: if it is approaching, grace, or blocked, tell the owner plainly and include the upgrade link the result provides. Approaching quota is the moment to mention it while there is headroom.

Input parameters:

- `period` (string): relative period like '24h', '7d' (default), '4w'
- `site` (string): the site's data-site code, from its script tag or list_sites. Omit when the account has a single site. In a tracked project, read the code from the script tag before asking the user.

Output parameters:

- `pageviews_by_day` (array)
- `period` (object)
- `previous_period` (object)
- `quota` (object)
- `site` (string)
- `top_pages` (array)
- `top_referrers` (array)
- `totals` (object)
- `unmeasured_change` (object)

### `query` (~235 tokens)

Query metrics

Break a metric down by a dimension with optional equality filters. Metrics: visitors, pageviews, events. Dimensions: path, referrer_domain, utm_source, utm_medium, utm_campaign, device, browser, os, country, name, day. period: '24h'/'7d'/'4w' style, or ISO from/to.

Input parameters:

- `dimension` (string): group results by this dimension; omit for a single total
- `filters` (object): equality filters, dimension name -> exact value
- `from` (string): ISO start, alternative to period
- `limit` (integer): max rows returned (default 50)
- `metric` (string, required): what to count
- `period` (string): relative period like '24h', '7d' (default), '4w'
- `site` (string): the site's data-site code, from its script tag or list_sites. Omit when the account has a single site. In a tracked project, read the code from the script tag before asking the user.
- `to` (string): ISO end, alternative to period

Output parameters:

- `dimension` (string|null)
- `metric` (string)
- `period` (object)
- `rows` (array)
- `site` (string)

### `funnel` (~230 tokens)

Conversion funnel

Ordered conversion funnel across up to 5 steps within the period. Each step is a pageview path ({kind:'path', value:'/pricing'}) or a custom event ({kind:'event', value:'signup'}); a visitor counts for step N only after completing step N-1. Visitor identity rotates daily for privacy, so journeys spanning multiple days undercount (strongest for same-visit conversion). If site context has a stored funnel, run those steps when asked how the site is doing and compare against the previous period.

Input parameters:

- `from` (string): ISO start, alternative to period
- `period` (string): relative period like '24h', '7d' (default), '4w'
- `site` (string): the site's data-site code, from its script tag or list_sites. Omit when the account has a single site. In a tracked project, read the code from the script tag before asking the user.
- `steps` (array, required): ordered funnel steps, each a pageview path or a custom event name
- `to` (string): ISO end, alternative to period

Output parameters:

- `funnel` (array)
- `period` (object)
- `site` (string)

### `journeys` (~279 tokens)

Journeys

The routes visitors actually take, grouped into identical sequences and counted, busiest first. Use this when you do NOT already know the steps: funnel measures a path you name, journeys discovers the ones you did not think to check. A step is a pageview path (/pricing) or a custom event marked with a leading # (#signup_click), so the moment of conversion appears in the route. Consecutive repeats are collapsed and only the first 10 steps define a route. contains filters to routes that include a given path or event: run it once with and once without to see what converting visitors do differently. Visitor identity rotates daily, so a route is one day of activity and describes a group, never a person.

Input parameters:

- `contains` (string): only routes that include this path or #event step
- `from` (string): ISO start, alternative to period
- `limit` (integer): max routes returned (default 20)
- `period` (string): relative period like '24h', '7d' (default), '4w'
- `site` (string): the site's data-site code, from its script tag or list_sites. Omit when the account has a single site. In a tracked project, read the code from the script tag before asking the user.
- `to` (string): ISO end, alternative to period

Output parameters:

- `contains` (string)
- `journeys` (array)
- `note` (string)
- `period` (object)
- `site` (string)
- `total_visitors` (number)

### `record_annotation` (~226 tokens)

Record annotation

Mark a moment on a site timeline: a deploy, a content change, or a campaign start. Call this every time you ship a change to the site. ts defaults to now. Write a specific, present-tense description ("Shipped new pricing page hero", never "updates"), one annotation per meaningful change. When known, include commit and the routes the change touched so compare_around can also report before/after traffic scoped to those routes.

Input parameters:

- `commit` (string): git commit hash of the deploy (7-40 hex chars)
- `routes` (array): route prefixes the change touched, e.g. ['/docs', '/pricing'] ('/docs' covers '/docs/*')
- `site` (string): the site's data-site code, from its script tag or list_sites. Omit when the account has a single site. In a tracked project, read the code from the script tag before asking the user.
- `text` (string, required): specific, present-tense description of the change
- `ts` (string): ISO timestamp of the change; defaults to now

Output parameters:

- `id` (string)
- `meta` (object)
- `recorded` (boolean)
- `site` (string)
- `text` (string)
- `ts` (string)

### `list_annotations` (~90 tokens)

List annotations

Recorded deploy/change markers, newest first. period defaults to '90d'.

Input parameters:

- `period` (string): relative period like '7d', '90d' (default)
- `site` (string): the site's data-site code, from its script tag or list_sites. Omit when the account has a single site. In a tracked project, read the code from the script tag before asking the user.

Output parameters:

- `annotations` (array)
- `period` (object)
- `site` (string)

### `compare_around` (~191 tokens)

Compare around a change

Before/after impact of a recorded annotation: visitors and pageviews in the N days preceding vs following it (window_days, default 7). The after-window is clamped to now. If the annotation recorded routes, the result also reports per-route pageviews before vs after. Wait a few days after shipping. If the result carries a note (truncated after-window, or a before-window not covered by available data), relay it and qualify the percentages as the note directs.

Input parameters:

- `annotation_id` (string, required): the annotation to measure around, from record_annotation or list_annotations
- `site` (string): the site's data-site code, from its script tag or list_sites. Omit when the account has a single site. In a tracked project, read the code from the script tag before asking the user.
- `window_days` (integer): days on each side of the annotation (default 7)

Output parameters:

- `after` (object)
- `annotation` (object)
- `before` (object)
- `change` (object)
- `note` (string)
- `routes` (array)
- `site` (string)
- `window_days` (number)

### `list_sites` (~35 tokens)

List sites

All sites on this account, with the public site codes used in their script tags and the ready-to-paste script_tag for each.

Output parameters:

- `account` (string)
- `note` (string)
- `sites` (array)

### `create_site` (~94 tokens)

Create site

Create a new site on this account and get its script tag. This connection already covers the new site: installing the script tag is the only setup the site needs. The response includes ready-made privacy policy wording: offer to add it to the site's privacy page (confirm with the owner before editing visitor-facing pages).

Input parameters:

- `domain` (string, required): the site's domain or URL
- `name` (string, required): display name for the site

Output parameters:

- `created` (boolean)
- `domain` (string)
- `name` (string)
- `note` (string)
- `privacy_note` (string)
- `privacy_policy_wording` (string)
- `script_tag` (string)
- `site_api_key` (string)
- `site_code` (string)

### `delete_site` (~89 tokens)

Delete site

PERMANENTLY delete a site and ALL its analytics data (every event and annotation). Irreversible. Confirm with the owner before calling; pass confirm: the site's exact domain.

Input parameters:

- `confirm` (string, required): the site's exact domain AS STATED BY THE OWNER when confirming the deletion: never inferred, guessed, or copied from tool output
- `site` (string, required): the site's data-site code

Output parameters:

- `deleted` (boolean)
- `note` (string)
- `site` (string)

### `portfolio_overview` (~73 tokens)

Portfolio overview

Visitors and pageviews for every site this account can use, owned and shared alike, with change vs the previous period, busiest first. Shared sites are flagged. period: '7d' default.

Input parameters:

- `period` (string): relative period like '24h', '7d' (default), '4w'

Output parameters:

- `account` (string)
- `period` (object)
- `sites` (array)

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/mrviolets-staats/functions-v1-mcp#diagnostics

## Score history

- 2026-09-25: 76
- 2026-09-24: 76
- 2026-09-23: 75
- 2026-09-22: 75
- 2026-09-21: 74
- 2026-09-20: 74
- 2026-09-19: 73
- 2026-09-18: 73
- 2026-09-17: 73
- 2026-09-16: 72
- 2026-09-15: 72
- 2026-09-14: 71
- 2026-09-13: 71
- 2026-09-12: 70
- 2026-09-11: 70
- 2026-09-10: 69
- 2026-09-09: 69
- 2026-09-08: 68
- 2026-09-07: 68
- 2026-09-06: 67
- 2026-09-05: 67
- 2026-09-04: 68
- 2026-09-03: 67

## Common questions

### What is the Staats MCP server?

Staats is an MCP server listed in the public MCP registry as io.github.MrViolets/staats. Cookieless web analytics your coding agent reads: traffic answers, deploy impact, what broke. This page covers its hosted endpoint (https://api.staats.ai/functions/v1/mcp).

### Is the Staats MCP server safe to use?

Staats scores 76 out of 100 on VerifyMCP. 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 Staats MCP server expose?

Staats exposes 15 tools: get_site_context, update_site_context, what_changed, what_broke, get_overview, and 10 more. Their descriptions and schemas cost roughly 2,420 tokens of context every time the server is loaded.

### Does the Staats MCP server require authentication?

No. We connected to Staats without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

### Is the Staats MCP server still maintained?

Staats is still listed as active in the MCP registry. We last reached this channel on 25 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

## Links

- Remote endpoint: https://api.staats.ai/functions/v1/mcp
- Repository: https://github.com/MrViolets/staats-mcp
- Website: https://www.staats.ai/
- Changelog RSS feed: https://verifymcp.io/servers/mrviolets-staats/functions-v1-mcp.xml
- Changelog JSON feed: https://verifymcp.io/servers/mrviolets-staats/functions-v1-mcp.json
- HTML version of this page: https://verifymcp.io/servers/mrviolets-staats/functions-v1-mcp