Stackpulse
REMOTE · STACKPULSE.APP
8,900+ services' status, and your Stackpulse dashboards and URL monitors. Needs Pro.
Available components
Last scanned (2 hours ago)
Scores higher than 59% of remote servers
Reachable. Last reached 23 Oct 2026.
Category Monitoring and Observability
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 Security57
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation check failed: no authorisation is required to call this server, and it exposes a tool marked destructive (remove_services). See how to fix → View diagnostics → Fail
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability74
- AI-judged instruction clarity (good).Pass
- Tool/resource definitions use about 1254 tokens (~78/item across 16 items; 16 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management37
- Stability observed for 11 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
- Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- All 1 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation.Pass
- An AI judge read all 17 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a current MCP spec version (2026-07-28).Pass
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.
- 22 Oct 26 +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.
- 20 Oct 26 +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.
- 17 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 13 to 17. That category is still filling its 30-day observation window: 4 days of observed history at the previous scan, 5 at this one. The score rises as the window fills, whether or not the server changes.
- 15 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 7 to 10. That category is still filling its 30-day observation window: 2 days of observed history at the previous scan, 3 at this one. The score rises as the window fills, whether or not the server changes.
- 13 Oct 26 +1
- Stability: unverified → 0.03 ▲ functional
- 12 Oct 26 64
First indexed and scored.
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 23 Oct 2026 · Probed https://stackpulse.app/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=stackpulse.app | CN=YE1,O=Let's Encrypt,C=US | 26 Sept 2026 | 25 Dec 2026 | ECDSA 256 | ECDSA-SHA384 | 543730ba25483f8a47c770300881d02a130 |
| SANs: *.stackpulse.app, stackpulse.app | ||||||
| CN=YE1,O=Let's Encrypt,C=US (CA) | CN=Root YE,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | ECDSA 384 | ECDSA-SHA384 | 5ddd70dd31f801c85c186a7a04b80afe |
| CN=Root YE,O=ISRG,C=US (CA) | CN=ISRG Root X2,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | ECDSA-SHA384 | 872165fc34b6e5fba8add5b3705fb53a |
| CN=ISRG Root X2,O=Internet Security Research Group,C=US (CA) | CN=ISRG Root X1,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | SHA256-RSA | 6c8f1dc727c7117f7baf853ac980f9cd |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of stackpulse.app. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| app. | present | 23684 | 8 | Verified |
| stackpulse.app. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://stackpulse.app/mcp | Verified | 200 | |
| http (plaintext) | http://stackpulse.app/mcp | HTTPS enforced | 301 | https://stackpulse.app/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 →
add_monitor Add a URL monitor ~114
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.
| Name | Type | Req | Description |
|---|---|---|---|
| dashboard | string | yes | A dashboard’s name or id |
| name | string | – | What to call it; the page’s title when left out |
| url | string | yes | The address to watch, e.g. "https://shop.example.com" |
| Name | Type | Req | Description |
|---|---|---|---|
| dashboard | object | yes | – |
| display | string | yes | – |
| id | string | yes | – |
| name | string | yes | – |
| test | object | yes | The check before it was added |
No examples provided.
add_services Add services ~59
Adds services to a dashboard by slug (search_services finds them), within the plan’s limit.
| Name | Type | Req | Description |
|---|---|---|---|
| dashboard | string | yes | A dashboard’s name or id |
| services | array | yes | Slugs, e.g. ["github", "vercel"] |
| Name | Type | Req | Description |
|---|---|---|---|
| added | array | yes | – |
| already | array | yes | – |
| notFound | array | yes | – |
| services | number | yes | – |
No examples provided.
check_monitor Check a URL monitor now ~47
Checks one of the account’s URL monitors now, as Check now does in the app, and says what it got.
| Name | Type | Req | Description |
|---|---|---|---|
| monitor | string | yes | The monitor’s name, address or id |
| Name | Type | Req | Description |
|---|---|---|---|
| check | – | yes | – |
| checked | boolean | yes | – |
| monitor | object | yes | – |
No examples provided.
create_dashboard Create a dashboard ~79
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.
| Name | Type | Req | Description |
|---|---|---|---|
| name | string | yes | The dashboard’s name, e.g. "Checkout" |
| services | array | – | Slugs to start with, e.g. ["stripe", "shopify"] |
| Name | Type | Req | Description |
|---|---|---|---|
| added | array | yes | – |
| id | string | yes | – |
| name | string | yes | – |
| notFound | array | yes | – |
| services | number | yes | – |
| url | string | yes | The dashboard in the app |
No examples provided.
get_incident_history Get incident history ~123
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.
| Name | Type | Req | Description |
|---|---|---|---|
| dashboard | string | yes | A dashboard’s name or id |
| days | number | – | Without from: how many days back from to, 7 by default |
| from | string | – | The window’s start, ISO 8601 |
| to | string | – | The window’s end, ISO 8601; now when left out |
| Name | Type | Req | Description |
|---|---|---|---|
| alreadyGoing | array | yes | – |
| dashboard | object | yes | – |
| from | string | yes | ISO 8601 |
| note | string | – | – |
| started | array | yes | – |
| to | string | yes | ISO 8601 |
No examples provided.
get_monitor Get a URL monitor ~64
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.
| Name | Type | Req | Description |
|---|---|---|---|
| monitor | string | yes | The monitor’s name, address or id |
| Name | Type | Req | Description |
|---|---|---|---|
| blockedSince | – | yes | – |
| certificate | – | yes | – |
| changes | array | yes | – |
| days | array | yes | – |
| display | string | yes | – |
| id | string | yes | – |
| last30Days | object | yes | – |
| lastChecks | array | yes | The last 10 checks, newest first |
| name | string | yes | – |
| notChecked | boolean | – | – |
| responseMs | number|null | yes | The median response time of the last 5 checks that answered, in ms |
| since | – | yes | – |
| status | string | yes | up, slow, down, paused or checking |
| text | string | yes | – |
No examples provided.
get_reliability Get reliability ~105
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.
| Name | Type | Req | Description |
|---|---|---|---|
| dashboard | string | yes | A dashboard’s name or id |
| days | – | – | 7, 30 (the default) or 90 |
| Name | Type | Req | Description |
|---|---|---|---|
| breaksTogether | array | yes | – |
| dashboard | object | yes | – |
| days | number | yes | – |
| medianRecoveryMinutes | number|null | yes | – |
| services | array | yes | – |
No examples provided.
get_service Get a service ~59
One service’s status from its official status page: what’s wrong, the components with a problem, 90 days of history and recent incidents.
| Name | Type | Req | Description |
|---|---|---|---|
| slug | string | yes | The service’s slug, e.g. "github"; search_services finds it |
| Name | Type | Req | Description |
|---|---|---|---|
| checkedAt | – | yes | – |
| checkedEverySeconds | number|null | yes | – |
| components | array | yes | The components that aren’t online |
| componentsTotal | number | – | How many components the page lists |
| incidents | array | yes | – |
| last90Days | object | yes | – |
| name | string | yes | – |
| since | – | – | – |
| slug | string | yes | – |
| status | string | yes | – |
| statusPage | string | yes | – |
| summary | string | yes | – |
| text | string | yes | – |
| url | string | yes | – |
No examples provided.
get_stack_status Get stack status ~101
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.
| Name | Type | Req | Description |
|---|---|---|---|
| dashboard | string | – | A dashboard’s name or id; every dashboard when left out |
| include | string | – | "all" for every item, not only the ones with problems |
| Name | Type | Req | Description |
|---|---|---|---|
| dashboards | array | yes | – |
No examples provided.
list_dashboards List dashboards ~36
The account’s dashboards (the ones this connection can see), with how many services and URL monitors each has and its worst status now.
Input schema present but exposes no named parameters.
| Name | Type | Req | Description |
|---|---|---|---|
| dashboards | array | yes | – |
No examples provided.
list_outages List outages ~82
Services reporting a problem right now, the newest first: the 25 best-known, unless all is true or a limit is given.
| Name | Type | Req | Description |
|---|---|---|---|
| all | boolean | – | Every service in the catalog with a problem (often around 300), not only the best-known |
| limit | integer | – | How many to list, the newest first; 25 by default |
| Name | Type | Req | Description |
|---|---|---|---|
| services | array | yes | – |
| total | number | yes | How many report a problem, of which services lists `limit` |
No examples provided.
pause_monitor Pause a URL monitor ~51
Pauses a URL monitor, e.g. during a deploy: an open incident ends, and no alerts go out until it’s resumed.
| Name | Type | Req | Description |
|---|---|---|---|
| monitor | string | yes | The monitor’s name, address or id |
| Name | Type | Req | Description |
|---|---|---|---|
| blockedSince | – | yes | – |
| certificate | – | yes | – |
| changes | array | yes | – |
| days | array | yes | – |
| display | string | yes | – |
| id | string | yes | – |
| last30Days | object | yes | – |
| lastChecks | array | yes | The last 10 checks, newest first |
| name | string | yes | – |
| notChecked | boolean | – | – |
| responseMs | number|null | yes | The median response time of the last 5 checks that answered, in ms |
| since | – | yes | – |
| status | string | yes | up, slow, down, paused or checking |
| text | string | yes | – |
No examples provided.
remove_services Remove services ~54
Takes services off a dashboard. Their history stays; adding one back shows it again.
| Name | Type | Req | Description |
|---|---|---|---|
| dashboard | string | yes | A dashboard’s name or id |
| services | array | yes | Slugs, e.g. ["heroku"] |
| Name | Type | Req | Description |
|---|---|---|---|
| notOnDashboard | array | yes | – |
| removed | array | yes | – |
| services | number | yes | – |
No examples provided.
rename_dashboard Rename a dashboard ~43
Renames a dashboard. Its status page shares the name.
| Name | Type | Req | Description |
|---|---|---|---|
| dashboard | string | yes | A dashboard’s name or id |
| name | string | yes | Its new name |
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | – |
| name | string | yes | – |
| previousName | string | yes | – |
No examples provided.
resume_monitor Resume a URL monitor ~39
Resumes a paused URL monitor: it’s checked at once and starts fresh.
| Name | Type | Req | Description |
|---|---|---|---|
| monitor | string | yes | The monitor’s name, address or id |
| Name | Type | Req | Description |
|---|---|---|---|
| blockedSince | – | yes | – |
| certificate | – | yes | – |
| changes | array | yes | – |
| days | array | yes | – |
| display | string | yes | – |
| id | string | yes | – |
| last30Days | object | yes | – |
| lastChecks | array | yes | The last 10 checks, newest first |
| name | string | yes | – |
| notChecked | boolean | – | – |
| responseMs | number|null | yes | The median response time of the last 5 checks that answered, in ms |
| since | – | yes | – |
| status | string | yes | up, slow, down, paused or checking |
| text | string | yes | – |
No examples provided.
search_services Search services ~57
Finds services in the catalog of 9,700+ status pages by name, with their status now. Use it to find a service’s slug.
| Name | Type | Req | Description |
|---|---|---|---|
| query | string | yes | A name, e.g. "github" or "aws" |
| Name | Type | Req | Description |
|---|---|---|---|
| query | string | yes | – |
| services | array | yes | – |
No examples provided.
How do I install the Stackpulse MCP server?
Stackpulse is a hosted endpoint at https://stackpulse.app/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 · stackpulse.app
claude mcp add --transport http app-stackpulse-mcp 'https://stackpulse.app/mcp'
What is the Stackpulse MCP server?
Stackpulse is an MCP server listed in the public MCP registry as app.stackpulse/mcp. 8,900+ services' status, and your Stackpulse dashboards and URL monitors. Needs Pro. This page covers its hosted endpoint (https://stackpulse.app/mcp).
Is the Stackpulse MCP server safe to use?
Stackpulse scores 69 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 Stackpulse MCP server expose?
Stackpulse exposes 16 tools: search_services, get_service, list_outages, list_dashboards, get_stack_status, and 11 more. Their descriptions and schemas cost roughly 1,113 tokens of context every time the server is loaded.
Does the Stackpulse MCP server require authentication?
No. We connected to Stackpulse without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the Stackpulse MCP server still maintained?
Stackpulse is still listed as active in the MCP registry. We last reached this channel on 23 October 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.