Model Context Protocol server for Rollbar
Nothing to run from here
Staats is installed from its publisher's own source and answers where it runs, so this marketplace is not in the path of a single call. There is no address here to send one to, and a panel that pretended otherwise would be showing you an answer we made up. Install it and call it from your own client — the Installation tab has the entry for each one.
15
tools declared
—
trust score
remote
at its publisher
—
calls last 7d
What it does
Cookieless web analytics your coding agent reads: traffic answers, deploy impact, what broke.
Quickstart
# 1 — add it to Claude Code
claude mcp add --scope user --transport http staats-mcp https://api.staats.ai/functions/v1/mcp
# 2 — ask your agent for something these tools do
# get_site_context, update_site_context, what_changed and 12 more
Staats costs nothing on mcprush: there is no plan to choose here, no cap to set and nothing mcprush can bill you for.
Publishernot claimed
MRAll 1 server
MrViolets1 server
1 category
Collected from a public index. Nobody has claimed this account, so nothing here was written by its author — claim it if it is yours.
Installation
Where are you running it?
Every route below installs the same thing and ends at the same approval screen. Nothing here runs on your machine and nothing runs on ours: this server answers at its publisher’s own address, and what you install is the connection straight to it.
Claude Codedeclared by this listing
This is a public server: it answers at its publisher’s own address and this marketplace is not in the path. Claude Code registers it in one command; --scope user makes it available in every project. The transport below is http, as the publisher's own manifest declares it.
claude mcp add --scope user --transport http staats-mcp https://api.staats.ai/functions/v1/mcpReconnect, or start a new session, and the tools appear in the model’s tool list.
Free on mcprush, and it answers at its publisher’s own address: this marketplace is not in the path, so there is no key of ours to hold and no card to add.
What it writes
One config entry pointing straight at the publisher’s own address — this marketplace is not in the path, and nothing from this listing executes on your machine.
What you approve
15 tools, with what each one reads, writes and reaches shown before you agree — the same list on every route above. Read the tool surface.
Tool surface
What the model actually sees. Descriptions are diffed on every release — see version history.
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| site | string | no | 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. |
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| site | string | no | 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. |
| description | no | what the site is; null deletes | |
| goals | no | what the owner wants from it; null deletes | |
| audience | no | who the site is for; null deletes | |
| notes | no | open agenda items to check at session start; null deletes | |
| events | object | no | map of event name -> one-line meaning; record one whenever you add tracking. null deletes an entry. |
| funnel | no | the site's canonical conversion steps, same shape as the funnel tool's steps. null clears it. | |
| name | string | no | update the site's display name |
| domain | string | no | update the site's domain |
| retention_days | integer | no | 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 th |
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| site | string | no | 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. |
| period | string | no | relative period like '24h', '7d' (default), '4w' |
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 succe
| Parameter | Type | Required | Notes |
|---|---|---|---|
| site | string | no | 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. |
| period | string | no | relative period like '24h', '7d' (default), '4w' |
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| site | string | no | 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. |
| period | string | no | relative period like '24h', '7d' (default), '4w' |
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| site | string | no | 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. |
| metric | string | yes | what to count |
| dimension | string | no | group results by this dimension; omit for a single total |
| filters | object | no | equality filters, dimension name -> exact value |
| period | string | no | relative period like '24h', '7d' (default), '4w' |
| from | string | no | ISO start, alternative to period |
| to | string | no | ISO end, alternative to period |
| limit | integer | no | max rows returned (default 50) |
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 f
| Parameter | Type | Required | Notes |
|---|---|---|---|
| site | string | no | 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 |
| period | string | no | relative period like '24h', '7d' (default), '4w' |
| from | string | no | ISO start, alternative to period |
| to | string | no | ISO end, alternative to period |
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
| Parameter | Type | Required | Notes |
|---|---|---|---|
| site | string | no | 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. |
| contains | string | no | only routes that include this path or #event step |
| limit | integer | no | max routes returned (default 20) |
| period | string | no | relative period like '24h', '7d' (default), '4w' |
| from | string | no | ISO start, alternative to period |
| to | string | no | ISO end, alternative to period |
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 tra
| Parameter | Type | Required | Notes |
|---|---|---|---|
| site | string | no | 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 | no | ISO timestamp of the change; defaults to now |
| commit | string | no | git commit hash of the deploy (7-40 hex chars) |
| routes | array | no | route prefixes the change touched, e.g. ['/docs', '/pricing'] ('/docs' covers '/docs/*') |
Recorded deploy/change markers, newest first. period defaults to '90d'.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| site | string | no | 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. |
| period | string | no | relative period like '7d', '90d' (default) |
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 dat
| Parameter | Type | Required | Notes |
|---|---|---|---|
| site | string | no | 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. |
| annotation_id | string | yes | the annotation to measure around, from record_annotation or list_annotations |
| window_days | integer | no | days on each side of the annotation (default 7) |
All sites on this account, with the public site codes used in their script tags and the ready-to-paste script_tag for each.
No parameter schema on file.
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).
| Parameter | Type | Required | Notes |
|---|---|---|---|
| name | string | yes | display name for the site |
| domain | string | yes | the site's domain or URL |
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| site | string | yes | the site's data-site code |
| 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 |
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| period | string | no | relative period like '24h', '7d' (default), '4w' |
Free
$0 forever
- Every tool — any call limit is its publisher’s, not ours
- No card, and mcprush charges nothing for it
- Runs at its publisher’s own address — this marketplace is not in the path
- Nothing to cap, because mcprush bills nothing
What counts against your monthly calls
| Tool | Unit | Calls used | Out of the allowance |
|---|
Nothing here is billable: mcprush charges nothing to install Staats or to call it, at any volume.
Call allowance · this installenforced at the gateway
Monthly allowance, in calls
—
—
Alert at 80% · then the tool returns a normal MCP error
Used this month: —
—Grade not published
No rule-by-rule report on file for this release
Two independent axes, because powerful and malicious are different questions. The grade is threat only. The capability level is blast radius, and it is never a penalty on the grade — it is priced as one subtract-only term in the score, where you can see it.
This listing is an address its publisher runs, and you connect to it directly — this marketplace is not in the path. The scanner reads packages and public source, and an address is neither: the repository linked on this page is where this record was collected from, not a copy of what the address serves, so it is not graded in its place. So there is no grade — not a withheld one, an unmeasured one.
Release history
This is an address its publisher runs: which release it serves is theirs to choose, so there is nothing here to pin. The history below is for reading; the current release on file is 1.0.1.
1.0.1
undated
latestNo release note was published with this version.
—
no reviews yet
Who can review
One review per account, from a signed-in account that does not publish this listing. Nothing else is asked — you can say what you think before you install it. Publishers can reply once per review, and a review can be edited or deleted by whoever wrote it.
Sign in to write one
Any signed-in account that does not publish Staats can review it, once — before installing it or after. A review from an account that has installed it is marked as one.
No reviews yet
Nobody has reviewed this listing. The rating on the card is the mean of the reviews written here and nothing else, so there is no rating until somebody writes the first — which takes a signed-in account that does not publish it, and nothing else.