Skip to content

Staats MCP server

io.github.MrViolets/staatsMrVioletsstreamable-httpv1.0.1Scanned

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

15 tools: 2 can delete or cancel things, 2 do something that can't be undone, 5 change things and 6 only read.

Tools: 2 delete, 2 irreversible, 5 write, 6 read.
  • Reads private data · 0
  • Reads text others write · 0
  • Can send data out · 2
  • 2 findings

Sign-in required, OAuth metadata published. Remote posture

With Anlyon

2 tools here can delete or cancel things and 2 do something that can't be undone. Govern them.

  • Anlyon lists the tools and adopts none.
  • Each tool you adopt gets approvals and receipts.
  • Your agent never holds the key.
Govern this server →

A tool your agent calls directly is not routed through Anlyon and is not governed by it. Anlyon Radar only lists and labels, and these labels are the same either way.

What the Staats MCP server can do

The Staats MCP server is published by the GitHub account MrViolets. It has 15 tools. It can delete or cancel things (2 tools: update_site_context and delete_site), do things that cannot be undone, such as sending, paying or publishing (funnel and journeys) and create or change data (5 tools: what_changed, what_broke, record_annotation, create_site and 1 more). 6 tools only read.

2 tools can send data out of your system (funnel and journeys).

The fixed checks matched 2 findings (annotation-conflict). Each one comes with the text it matched.

Its remote endpoint asks for sign-in and publishes OAuth metadata.

Last scanned Oct 21, 2026, version 1.0.1.

Tools

Grouped by what each tool does, most consequential first. Open one for its reasons and full description; descriptions are the publisher's own words.

15 tools

Deletes or cancels 2Claude Code: deny
  • delete_sitePERMANENTLY delete a site and ALL its analytics data (every event and annotation).No findings

    Why it is in this group

    • The name "delete_site" says "delete": a word for removing or ending something.
    • The description says "PERMANENTLY delete".
    • The server marks it destructive (destructiveHint: true).
    Description, as the server wrote it
    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.

    Annotations the server declares

    • destructiveHint: true
    • idempotentHint: true
    • openWorldHint: false
  • update_site_contextSave or amend what a site is for.No findings

    Why it is in this group

    • The name "update_site_context" says "update": a word for a change.
    • The server marks it destructive (destructiveHint: true).
    Description, as the server wrote it
    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.

    Annotations the server declares

    • destructiveHint: true
    • idempotentHint: true
    • openWorldHint: false
Can't be undone 2Claude Code: ask
  • funnelOrdered conversion funnel across up to 5 steps within the period.Can send data out1 finding

    Why it is in this group

    • The input addresses people (input.to): what it sends cannot be taken back.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.

    What it can reach

    • outboundThe input takes a destination (input.to): what the tool writes goes there.

    Findings

    • Warn

      The server marks "funnel" read-only (readOnlyHint: true), and its own name, description or input give the class "irreversible".

      Matched text

      annotations: {"readOnlyHint":true,"openWorldHint":false}; The input addresses people (input.to): what it sends cannot be taken back.

      What this check looks for
    Description, as the server wrote it
    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.

    Annotations the server declares

    • readOnlyHint: true
    • openWorldHint: false
  • journeysThe routes visitors actually take, grouped into identical sequences and counted, busiest first.Can send data out1 finding

    Why it is in this group

    • The input addresses people (input.to): what it sends cannot be taken back.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.

    What it can reach

    • outboundThe input takes a destination (input.to): what the tool writes goes there.

    Findings

    • Warn

      The server marks "journeys" read-only (readOnlyHint: true), and its own name, description or input give the class "irreversible".

      Matched text

      annotations: {"readOnlyHint":true,"openWorldHint":false}; The input addresses people (input.to): what it sends cannot be taken back.

      What this check looks for
    Description, as the server wrote it
    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.

    Annotations the server declares

    • readOnlyHint: true
    • openWorldHint: false
Changes things 5Claude Code: ask
  • create_siteCreate a new site on this account and get its script tag.No findings

    Why it is in this group

    • The name "create_site" says "create": a word for a change.
    Description, as the server wrote it
    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).

    Annotations the server declares

    • destructiveHint: false
    • idempotentHint: false
    • openWorldHint: false
  • portfolio_overviewVisitors and pageviews for every site this account can use, owned and shared alike, with change vs the previous period, busiest first.No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • readOnlyHint: true
    • openWorldHint: false
  • record_annotationMark a moment on a site timeline: a deploy, a content change, or a campaign start.No findings

    Why it is in this group

    • The description's first verb is "mark": a word for a change.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • destructiveHint: false
    • idempotentHint: false
    • openWorldHint: false
  • what_brokeSigns 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…No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • readOnlyHint: true
    • openWorldHint: false
  • what_changedNotable movements in the period without scanning raw numbers: statistically unusual traffic days, referrer surges and first-time referrers, pages whose share of traffic jumped, alo…No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • readOnlyHint: true
    • openWorldHint: false
Only reads 6Show 6 read-only tools
  • compare_aroundBefore/after impact of a recorded annotation: visitors and pageviews in the N days preceding vs following it (window_days, default 7).No findings

    Why it is in this group

    • The name "compare_around" says "compare": a word for reading.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • readOnlyHint: true
    • openWorldHint: false
  • get_overviewTraffic pulse: visitor/pageview totals vs the previous period, top pages, top referrers, and a per-day series.No findings

    Why it is in this group

    • The name "get_overview" says "get": a word for reading.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • readOnlyHint: true
    • openWorldHint: false
  • get_site_contextWhat a site is and what the owner wants from it, plus its data-retention settings.No findings

    Why it is in this group

    • The name "get_site_context" says "get": a word for reading.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • readOnlyHint: true
    • openWorldHint: false
  • list_annotationsRecorded deploy/change markers, newest first.No findings

    Why it is in this group

    • The name "list_annotations" says "list": a word for reading.
    Description, as the server wrote it
    Recorded deploy/change markers, newest first. period defaults to '90d'.

    Annotations the server declares

    • readOnlyHint: true
    • openWorldHint: false
  • list_sitesAll sites on this account, with the public site codes used in their script tags and the ready-to-paste script_tag for each.No findings

    Why it is in this group

    • The name "list_sites" says "list": a word for reading.
    Description, as the server wrote it
    All sites on this account, with the public site codes used in their script tags and the ready-to-paste script_tag for each.

    Annotations the server declares

    • readOnlyHint: true
    • openWorldHint: false
  • queryBreak a metric down by a dimension with optional equality filters.No findings

    Why it is in this group

    • The name "query" says "query": a word for reading.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • readOnlyHint: true
    • openWorldHint: false

This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.

Exfil surface

Which tools read private data, which read text someone else can write, and which can send data out. One of each is a path a prompt injection can use.

No private-data, untrusted-input, outbound path in this server alone: no tool is tagged private-data or untrusted-input.

Reads private data0
Reads files, mail, messages, databases, secrets, calendars or repositories.
Reads text others write0
Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
Can send data out2
Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.

Other servers in the same agent add their own tools to these paths. Audit your whole setup to see them together.

Remote posture

What anyone on the internet sees at the remote endpoint: an anonymous initialize and tools/list, and the public OAuth metadata.

Sign-in required, OAuth metadata published

Looked at Nov 20, 2026, 18:59 UTC, unchanged since Oct 29, 2026. No credentials were sent and no tool was called. What is looked at.

Reachable
yes
HTTP status of an anonymous initialize
401
tools/list served without credentials
no
Tools that change things, listed without credentials
0
Protocol version
not observed
WWW-Authenticate on 401
yes
resource_metadata in WWW-Authenticate
https://api.staats.ai/.well-known/oauth-protected-resource/mcp
RFC 9728 protected resource metadata
https://api.staats.ai/.well-known/oauth-protected-resource/mcp
Authorization servers
https://aynnkkzvvckdvswwswhs.supabase.co/auth/v1
Legacy HTTP+SSE transport
no
Dynamic client registration
yes
Client ID metadata documents
no

Posture changes

  1. Oct 29, 2026
    • HTTP status of an anonymous initialize: 200 to 401
    • tools/list served without credentials: yes to no
    • Tools that change things, listed without credentials: 9 to 0
    • Protocol version: 2025-06-18 to none
    • WWW-Authenticate on 401: not observed to yes
    • resource_metadata in WWW-Authenticate: none to https://api.staats.ai/.well-known/oauth-protected-resource/mcp
    • RFC 9728 protected resource metadata: none to https://api.staats.ai/.well-known/oauth-protected-resource/mcp
    • Authorization servers: none to https://aynnkkzvvckdvswwswhs.supabase.co/auth/v1
    • Dynamic client registration: not observed to yes
    • Client ID metadata documents: not observed to no

Findings

Matches of fixed checks, with the text they matched.

2 warn
  • Warnfunnel

    The server marks "funnel" read-only (readOnlyHint: true), and its own name, description or input give the class "irreversible".

    Matched text

    annotations: {"readOnlyHint":true,"openWorldHint":false}; The input addresses people (input.to): what it sends cannot be taken back.

    What this check looks for
  • The server marks "journeys" read-only (readOnlyHint: true), and its own name, description or input give the class "irreversible".

    Matched text

    annotations: {"readOnlyHint":true,"openWorldHint":false}; The input addresses people (input.to): what it sends cannot be taken back.

    What this check looks for

History

Changes to its tool definitions and to its remote endpoint, newest first.

  1. PostureRemote posture changed. HTTP status of an anonymous initialize: 200 -> 401; tools/list served without credentials: yes -> no; Tools that change things, listed without credentials: 9 -> 0 (and 7 more).View diff
    • HTTP status of an anonymous initialize: 200 to 401
    • tools/list served without credentials: yes to no
    • Tools that change things, listed without credentials: 9 to 0
    • Protocol version: 2025-06-18 to none
    • WWW-Authenticate on 401: not observed to yes
    • resource_metadata in WWW-Authenticate: none to https://api.staats.ai/.well-known/oauth-protected-resource/mcp
    • RFC 9728 protected resource metadata: none to https://api.staats.ai/.well-known/oauth-protected-resource/mcp
    • Authorization servers: none to https://aynnkkzvvckdvswwswhs.supabase.co/auth/v1
    • Dynamic client registration: not observed to yes
    • Client ID metadata documents: not observed to no

Install

Pinned to version 1.0.1. Values in angle brackets are yours to fill in.

claude mcp add --transport http staats https://api.staats.ai/functions/v1/mcp
claude mcp add --transport http staats https://api.staats.ai/functions/v1/mcp

Run in a terminal.

Claude Code permissions

Allow the reads, ask before a change or a way out, deny the deletes. Paste into .claude/settings.json.

.claude/settings.json
{
  "permissions": {
    "allow": [
      "mcp__staats__get_site_context",
      "mcp__staats__get_overview",
      "mcp__staats__query",
      "mcp__staats__list_annotations",
      "mcp__staats__compare_around",
      "mcp__staats__list_sites"
    ],
    "ask": [
      "mcp__staats__what_changed",
      "mcp__staats__what_broke",
      "mcp__staats__funnel",
      "mcp__staats__journeys",
      "mcp__staats__record_annotation",
      "mcp__staats__create_site",
      "mcp__staats__portfolio_overview"
    ],
    "deny": [
      "mcp__staats__update_site_context",
      "mcp__staats__delete_site"
    ]
  }
}

Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. A read that can send data out (it takes a URL, say) asks first too. It assumes the server is installed as staats. Review it before you use it.

Capability tags behind 2 rules
  • mcp__staats__funnel outbound
  • mcp__staats__journeys outbound

Pin

Keep the decision: fail CI when the tools change, follow every change, or show a badge.

Pin in CI

Fail a build when the tools you reviewed are not the tools the server serves today.

curl -s "https://radar.anlyon.com/api/v1/servers/io.github.MrViolets/staats/verify?hash=f1f437f7f0656e2e86e9f1fd53ae8d168c4debf32151b7fa814ce097758f7908" | jq -e '.changed == false'

Pinned hash f1f437f7f065, from Oct 21, 2026, 19:04 UTC.

Watch

Get told when its tools change: a new tool, a new description, a new class.

https://radar.anlyon.com/servers/io.github.MrViolets/staats/changes.xml

An Atom feed. Works in any feed reader or Slack's RSS app.

Badge

Anlyon Radar badge for io.github.MrViolets/staats
[![Anlyon Radar](https://radar.anlyon.com/badge/io.github.MrViolets/staats.svg)](https://radar.anlyon.com/servers/io.github.MrViolets/staats)

Source: MCP Registry · repository. Synced Oct 21, 2026, 18:18 UTC.

Staats MCP server: questions and answers

Answered from the scan above, not from the publisher's description.

Is the Staats MCP server safe?

No scan can promise that. What its definitions show: 15 tools, 9 of which can change, send or delete something, and 2 findings from fixed checks. Allow the reads, ask before each change, and deny the deletes; the permissions block on this page does that.

Can the Staats MCP server delete data?

Yes. 2 tools can delete, cancel or revoke something: update_site_context and delete_site.

Can the Staats MCP server do things that cannot be undone?

Yes. 2 tools can send, pay, publish or merge: funnel and journeys.

What tools does the Staats MCP server have?

15 tools: 2 destructive, 2 irreversible, 5 write, 6 read. update_site_context, delete_site, funnel, journeys, what_changed, what_broke, record_annotation, create_site and 7 more.

Does the Staats MCP server need sign-in or OAuth?

Yes. Its remote endpoint answered 401 without credentials, and it publishes OAuth protected resource metadata (RFC 9728); its authorization server supports dynamic client registration.

Does the Staats MCP server send data to outside services?

2 tools can carry data out (it sends, posts or publishes, or takes a recipient, channel or URL): funnel and journeys.

Has the Staats MCP server changed its tools?

Not since Anlyon Radar started tracking it. Last scanned Oct 21, 2026.