Model Context Protocol server for Rollbar
Nothing to run from here
Stackpulse 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.
16
tools declared
—
trust score
remote
at its publisher
—
calls last 7d
What it does
8,900+ services' status, and your Stackpulse dashboards and URL monitors. Needs Pro.
Quickstart
# 1 — add it to Claude Code
claude mcp add --scope user --transport http stackpulse-mcp https://stackpulse.app/mcp
# 2 — ask your agent for something these tools do
# search_services, get_service, list_outages and 13 more
Stackpulse costs nothing on mcprush: there is no plan to choose here, no cap to set and nothing mcprush can bill you for.
Publishernot claimed
STAll 1 server
stackpulse1 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 stackpulse-mcp https://stackpulse.app/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
16 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.
Finds services in the catalog of 9,700+ status pages by name, with their status now. Use it to find a service’s slug.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| query | string | yes | A name, e.g. "github" or "aws" |
One service’s status from its official status page: what’s wrong, the components with a problem, 90 days of history and recent incidents.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| slug | string | yes | The service’s slug, e.g. "github"; search_services finds it |
Services reporting a problem right now, the newest first: the 25 best-known, unless all is true or a limit is given.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| all | boolean | no | Every service in the catalog with a problem (often around 300), not only the best-known |
| limit | integer | no | How many to list, the newest first; 25 by default |
The account’s dashboards (the ones this connection can see), with how many services and URL monitors each has and its worst status now.
No parameter schema on file.
What’s going on now on a dashboard: a summary, then every service and URL monitor with a problem, with when the problem began and when its current status did. A URL monitor that’s down lists what started around then. Without a dashboard, every dashboard.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| dashboard | string | no | A dashboard’s name or id; every dashboard when left out |
| include | string | no | "all" for every item, not only the ones with problems |
Incidents on a dashboard in a window: the ones that started in it (with what else started at the same time) and the ones already going on. As far back as the plan’s history goes.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| dashboard | string | yes | A dashboard’s name or id |
| from | string | no | The window’s start, ISO 8601 |
| to | string | no | The window’s end, ISO 8601; now when left out |
| days | number | no | Without from: how many days back from to, 7 by default |
One of the account’s URL monitors: its status, its uptime over the last 30 days (or since it started) with the failed checks apart, response times, its certificate and its latest checks.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| monitor | string | yes | The monitor’s name, address or id |
How reliable a dashboard’s services and URL monitors were over 7, 30 or 90 days: the least reliable first, with the share of time without a reported problem (minor issues count, so one long minor issue makes it low), time in each severity, incidents and recovery, and what tends to break together.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| dashboard | string | yes | A dashboard’s name or id |
| days | no | 7, 30 (the default) or 90 |
Makes a dashboard with a name and, optionally, services by slug (search_services finds them), within the plan’s dashboards and services. Answers with its address.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| name | string | yes | The dashboard’s name, e.g. "Checkout" |
| services | array | no | Slugs to start with, e.g. ["stripe", "shopify"] |
Renames a dashboard. Its status page shares the name.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| dashboard | string | yes | A dashboard’s name or id |
| name | string | yes | Its new name |
Adds services to a dashboard by slug (search_services finds them), within the plan’s limit.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| dashboard | string | yes | A dashboard’s name or id |
| services | array | yes | Slugs, e.g. ["github", "vercel"] |
Takes services off a dashboard. Their history stays; adding one back shows it again.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| dashboard | string | yes | A dashboard’s name or id |
| services | array | yes | Slugs, e.g. ["heroku"] |
Watches a website or API endpoint on a dashboard: checks the address once first, and refuses what the app refuses (private addresses, other ports, past the plan). Without a name, the page’s title names it. Headers and request bodies stay in the app.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| dashboard | string | yes | A dashboard’s name or id |
| url | string | yes | The address to watch, e.g. "https://shop.example.com" |
| name | string | no | What to call it; the page’s title when left out |
Checks one of the account’s URL monitors now, as Check now does in the app, and says what it got.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| monitor | string | yes | The monitor’s name, address or id |
Pauses a URL monitor, e.g. during a deploy: an open incident ends, and no alerts go out until it’s resumed.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| monitor | string | yes | The monitor’s name, address or id |
Resumes a paused URL monitor: it’s checked at once and starts fresh.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| monitor | string | yes | The monitor’s name, address or id |
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 Stackpulse 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. 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.0.
1.0.0
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 Stackpulse 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.