Staats
REMOTE · API.STAATS.AI
Cookieless web analytics your coding agent reads: traffic answers, deploy impact, what broke.
Available components
Last scanned (15 hours ago)
Scores higher than 28% of remote servers
Reachable. Last reached 21 Nov 2026.
Category Data and Analytics
Recent critical change
Authorization (9 Sept 2026). See the changelog before you install this server.
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. How we score → Why this is hard to score →
Endpoint Security94
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- The endpoint enforces authorisation, advertised via RFC 9728 protected-resource metadata. View diagnostics → Pass
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
- The authorisation server offers only Dynamic Client Registration (RFC 7591), which MCP 2026-07-28 deprecated in favour of Client ID Metadata Documents. View diagnostics → Partial
Transport & Reachability0
- Transport blocked by authentication: the endpoint requires auth we don't have to verify streamable-http. See how to fix → View diagnostics → Unverified
Schema Quality & AI Usability0
- Schema blocked by authentication: the endpoint requires auth we don't have to read it. See how to fix → Unverified
Stability & Change Management0
- Stability not yet verified: not enough scan history yet (needs a 30-day window).Unverified
Tool Coverage0
- Tool coverage blocked by authentication: the endpoint requires auth we don't have to read its tools.Unverified
Tool Safety0
- Tool safety blocked by authentication: the endpoint requires auth we don't have to read its tools.Unverified
Capabilities0
- Capabilities blocked by authentication: the endpoint requires auth we don't have to read them. See how to fix → Unverified
Unverified: 6 categories
Categories scored 0 because we could not verify them: authentication we do not have, an unreachable endpoint, or not enough scan history. We only credit what we can confirm. Claim this server and supply a read-only token to verify it and lift the score.
Checks we ran (5)
- TLS certificate
- Authorization
- HTTPS
- HSTS header
- DNSSEC
Checks we could not complete (6)
These are gaps on our side, not findings about this hosted endpoint. We only credit what we can confirm, so a category made up entirely of them scores 0.
- Transport in Transport & Reachability (scores 0 for this)Transport blocked by authentication: the endpoint requires auth we don't have to verify streamable-http.
- Schema quality in Schema Quality & AI Usability (scores 0 for this)Schema blocked by authentication: the endpoint requires auth we don't have to read it.
- Stability in Stability & Change Management (scores 0 for this)Stability not yet verified: not enough scan history yet (needs a 30-day window).
- Tool coverage in Tool Coverage (scores 0 for this)Tool coverage blocked by authentication: the endpoint requires auth we don't have to read its tools.
- Tool safety in Tool Safety (scores 0 for this)Tool safety blocked by authentication: the endpoint requires auth we don't have to read its tools.
- Capabilities in Capabilities (scores 0 for this)Capabilities blocked by authentication: the endpoint requires auth we don't have to read them.
Does not apply to this hosted endpoint (2)
- Supply Chain SecurityScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
- Provenance & TransparencyScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
The score does not measure everything. What the score does not measure →
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.
- 6 Nov 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 29 Oct 26 −42
- Endpoint reachability: reachable → behind authorisation ▼ security
- Stability: pass → unverified ▼ security
- Tool safety: pass → unverified ▼ security
- Transport: pass → unverified ▼ security
- Authorization: fail → pass ▲ security
- First check of Authorization: partial security
- Capabilities: pass → unverified ▼ functional
- Tool coverage: 100 → unverified ▼ functional
- First check of Schema quality: unverified functional
- 3 Oct 26 0
- Stability: 0.97 → pass security
- 28 Sept 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 25 Sept 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 9 Sept 26 0
- Authorization: unverified → fail ▼ critical
- 8 Sept 26 0
- Authorization: fail → unverified ▼ security
- 5 Sept 26 0
- DNSSEC: pass → fail ▼ 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 21 Nov 2026 · Probed https://api.staats.ai/functions/v1/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=api.staats.ai | CN=WE1,O=Google Trust Services,C=US | 21 Oct 2026 | 19 Jan 2027 | ECDSA 256 | ECDSA-SHA256 | 6053e2ee613acb5d13d56ac06edec85b |
| SANs: api.staats.ai | ||||||
| CN=WE1,O=Google Trust Services,C=US (CA) | CN=GTS Root R4,O=Google Trust Services LLC,C=US | 13 Dec 2023 | 20 Feb 2029 | ECDSA 256 | ECDSA-SHA384 | 7ff31977972c224a76155d13b6d685e3 |
| CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) | CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE | 15 Nov 2023 | 28 Jan 2028 | ECDSA 384 | SHA256-RSA | 7fe530bf331343bedd821610493d8a1b |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of api.staats.ai. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | Trust anchor | 20326, 38696 | 8, 8 | Verified |
| ai. | DS published | 1814 | 8 | Verified |
| staats.ai. | No DS | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication Enforced and verified
The endpoint asked for a token and published valid RFC 9728 metadata describing how to get one.
| Result | Enforced and verified |
|---|---|
| Enforced | On connection |
| HTTP status | 401 |
WWW-Authenticate challenge Bearer resource_metadata="https://api.staats.ai/.well-known/oauth-protected-resource/mcp"
Bearer resource_metadata="https://api.staats.ai/.well-known/oauth-protected-resource/mcp" | Header | Value |
|---|---|
| strict-transport-security | max-age=31536000; includeSubDomains; preload |
| www-authenticate | Bearer resource_metadata="https://api.staats.ai/.well-known/oauth-protected-resource/mcp" |
Protected resource metadata
| Document | https://api.staats.ai/.well-known/oauth-protected-resource/mcp |
|---|---|
| Retrieved | Yes |
| Resource | https://api.staats.ai/mcp |
| Authorisation server | https://aynnkkzvvckdvswwswhs.supabase.co/auth/v1 |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://api.staats.ai/functions/v1/mcp | Auth required | 401 | |
| http (plaintext) | http://api.staats.ai/functions/v1/mcp | HTTPS enforced | 301 | https://api.staats.ai/functions/v1/mcp |
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 →
compare_around Compare around a change ~191
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.
| Name | Type | Req | Description |
|---|---|---|---|
| annotation_id | string | yes | 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) |
| Name | Type | Req | Description |
|---|---|---|---|
| after | object | yes | – |
| annotation | object | yes | – |
| before | object | yes | – |
| change | object | yes | – |
| note | string | – | – |
| routes | array | – | – |
| site | string | yes | – |
| window_days | number | yes | – |
No examples provided.
create_site Create site ~94
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).
| Name | Type | Req | Description |
|---|---|---|---|
| domain | string | yes | the site's domain or URL |
| name | string | yes | display name for the site |
| Name | Type | Req | Description |
|---|---|---|---|
| created | boolean | yes | – |
| domain | string | yes | – |
| name | string | yes | – |
| note | string | yes | – |
| privacy_note | string | yes | – |
| privacy_policy_wording | string | yes | – |
| script_tag | string | yes | – |
| site_api_key | string | yes | – |
| site_code | string | yes | – |
No examples provided.
delete_site Delete site ~89
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.
| Name | Type | Req | Description |
|---|---|---|---|
| confirm | string | yes | the site's exact domain AS STATED BY THE OWNER when confirming the deletion: never inferred, guessed, or copied from tool output |
| site | string | yes | the site's data-site code |
| Name | Type | Req | Description |
|---|---|---|---|
| deleted | boolean | yes | – |
| note | string | yes | – |
| site | string | yes | – |
No examples provided.
funnel Conversion funnel ~230
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.
| Name | Type | Req | Description |
|---|---|---|---|
| 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 | yes | ordered funnel steps, each a pageview path or a custom event name |
| to | string | – | ISO end, alternative to period |
| Name | Type | Req | Description |
|---|---|---|---|
| funnel | array | yes | – |
| period | object | yes | – |
| site | string | yes | – |
No examples provided.
get_overview Site overview ~167
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.
| Name | Type | Req | Description |
|---|---|---|---|
| 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. |
| Name | Type | Req | Description |
|---|---|---|---|
| pageviews_by_day | array | yes | – |
| period | object | yes | – |
| previous_period | object | yes | – |
| quota | object | – | – |
| site | string | yes | – |
| top_pages | array | yes | – |
| top_referrers | array | yes | – |
| totals | object | yes | – |
| unmeasured_change | object | – | – |
No examples provided.
get_site_context Get site context ~119
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.
| Name | Type | Req | Description |
|---|---|---|---|
| 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. |
| Name | Type | Req | Description |
|---|---|---|---|
| context | object | yes | – |
| domain | string | yes | – |
| hint | string | – | – |
| name | string | yes | – |
| retention | object | yes | – |
| site | string | yes | – |
No examples provided.
journeys Journeys ~279
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.
| Name | Type | Req | Description |
|---|---|---|---|
| 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 |
| Name | Type | Req | Description |
|---|---|---|---|
| contains | string | – | – |
| journeys | array | yes | – |
| note | string | – | – |
| period | object | yes | – |
| site | string | yes | – |
| total_visitors | number | yes | – |
No examples provided.
list_annotations List annotations ~90
Recorded deploy/change markers, newest first. period defaults to '90d'.
| Name | Type | Req | Description |
|---|---|---|---|
| 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. |
| Name | Type | Req | Description |
|---|---|---|---|
| annotations | array | yes | – |
| period | object | yes | – |
| site | string | yes | – |
No examples provided.
list_sites List sites ~35
All sites on this account, with the public site codes used in their script tags and the ready-to-paste script_tag for each.
Input schema present but exposes no named parameters.
| Name | Type | Req | Description |
|---|---|---|---|
| account | string | yes | – |
| note | string | – | – |
| sites | array | yes | – |
No examples provided.
portfolio_overview Portfolio overview ~73
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.
| Name | Type | Req | Description |
|---|---|---|---|
| period | string | – | relative period like '24h', '7d' (default), '4w' |
| Name | Type | Req | Description |
|---|---|---|---|
| account | string | yes | – |
| period | object | yes | – |
| sites | array | yes | – |
No examples provided.
query Query metrics ~235
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.
| Name | Type | Req | Description |
|---|---|---|---|
| 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 | yes | 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 |
| Name | Type | Req | Description |
|---|---|---|---|
| dimension | string|null | yes | – |
| metric | string | yes | – |
| period | object | yes | – |
| rows | array | yes | – |
| site | string | yes | – |
No examples provided.
record_annotation Record annotation ~226
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.
| Name | Type | Req | Description |
|---|---|---|---|
| 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 | yes | specific, present-tense description of the change |
| ts | string | – | ISO timestamp of the change; defaults to now |
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | – |
| meta | object | – | – |
| recorded | boolean | yes | – |
| site | string | yes | – |
| text | string | yes | – |
| ts | string | yes | – |
No examples provided.
update_site_context Update site context ~269
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.
| Name | Type | Req | Description |
|---|---|---|---|
| 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. |
| Name | Type | Req | Description |
|---|---|---|---|
| context | object | yes | – |
| domain | string | yes | – |
| name | string | yes | – |
| retention | object | yes | – |
| site | string | yes | – |
| updated | boolean | yes | – |
No examples provided.
what_broke What broke ~193
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.
| Name | Type | Req | Description |
|---|---|---|---|
| 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. |
| Name | Type | Req | Description |
|---|---|---|---|
| annotations | array | yes | – |
| error_capture | string | – | – |
| findings | array | yes | – |
| note | string | – | – |
| note_errors | string | – | – |
| period | object | yes | – |
| site | string | yes | – |
| total_error_events | number | yes | – |
No examples provided.
what_changed What changed ~130
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.
| Name | Type | Req | Description |
|---|---|---|---|
| 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. |
| Name | Type | Req | Description |
|---|---|---|---|
| annotations | array | yes | – |
| findings | array | yes | – |
| note | string | – | – |
| period | object | yes | – |
| site | string | yes | – |
No examples provided.
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.
remote · api.staats.ai
claude mcp add --transport http mrviolets-staats 'https://api.staats.ai/functions/v1/mcp'
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 38 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?
Yes. Staats asked us for credentials when we connected, so you will need to authorise it in your MCP client before it can do anything.
Is the Staats MCP server still maintained?
Staats is still listed as active in the MCP registry. We last reached this channel on 21 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.
What did VerifyMCP test on the Staats MCP server?
VerifyMCP ran 5 checks on Staats, covering TLS certificate, Authorization, HTTPS, HSTS header and 1 more. 6 items could not be completed, a gap on our side rather than a finding about Staats: Transport, Schema quality, Stability, Tool coverage and 2 more. 6 categories score 0 for that reason, because we only credit what we can confirm. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.