# Stackpulse (remote · stackpulse.app)

8,900+ services' status, and your Stackpulse dashboards and URL monitors. Needs Pro.

- Trust score: 69/100 (medium)
- Change this week: +3
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-10-23

## Components

- remote · `stackpulse.app`: 69/100 (this document), [markdown](https://verifymcp.io/servers/app-stackpulse-mcp/stackpulse.md), [page](https://verifymcp.io/servers/app-stackpulse-mcp/stackpulse)

## Channel facts

- Endpoint: `https://stackpulse.app/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `1.0.0`

## Trust breakdown

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. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-10-23.

- **Endpoint Security**: 57/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - Authorisation check failed: no authorisation is required to call this server, and it exposes a tool marked destructive (remove_services).
  - HTTPS is enforced; there's no plaintext access path.
  - HSTS check failed: the Strict-Transport-Security header is absent.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 74/100
  - AI-judged instruction clarity (good).
  - Tool/resource definitions use about 1254 tokens (~78/item across 16 items; 16 tools + 0 resources), lean.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 37/100
  - Stability observed for 11 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
  - Structured output schemas are declared (100% of tools); any adoption earns full credit.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - All 1 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation.
  - An AI judge read all 17 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a current MCP spec version (2026-07-28).

## Install

### 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.

### Claude

```bash
claude mcp add --transport http app-stackpulse-mcp 'https://stackpulse.app/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "app-stackpulse-mcp": {
      "url": "https://stackpulse.app/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "app-stackpulse-mcp": {
      "type": "http",
      "url": "https://stackpulse.app/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.app-stackpulse-mcp]
url = "https://stackpulse.app/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "app-stackpulse-mcp": {
      "type": "remote",
      "url": "https://stackpulse.app/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add app-stackpulse-mcp --url 'https://stackpulse.app/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  app-stackpulse-mcp:
    url: "https://stackpulse.app/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "app-stackpulse-mcp": {
      "Transport": "http",
      "Url": "https://stackpulse.app/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add app-stackpulse-mcp -t streamable-http -u 'https://stackpulse.app/mcp'
```

### Other

```json
{
  "mcpServers": {
    "app-stackpulse-mcp": {
      "type": "http",
      "url": "https://stackpulse.app/mcp"
    }
  }
}
```

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-10-22 (score 69, +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.

### 2026-10-20 (score 68, +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.

### 2026-10-17 (score 67, +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.

### 2026-10-15 (score 66, +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.

### 2026-10-13 (score 65, +1)

- [functional improvement] Stability: unverified → 0.03

### 2026-10-12 (score 64)

First indexed and scored.

## MCP tools (16)

### `search_services` (~57 tokens)

Search services

Finds services in the catalog of 9,700+ status pages by name, with their status now. Use it to find a service’s slug.

Input parameters:

- `query` (string, required): A name, e.g. "github" or "aws"

Output parameters:

- `query` (string)
- `services` (array)

### `get_service` (~59 tokens)

Get a service

One service’s status from its official status page: what’s wrong, the components with a problem, 90 days of history and recent incidents.

Input parameters:

- `slug` (string, required): The service’s slug, e.g. "github"; search_services finds it

Output parameters:

- `checkedAt`
- `checkedEverySeconds` (number|null)
- `components` (array): The components that aren’t online
- `componentsTotal` (number): How many components the page lists
- `incidents` (array)
- `last90Days` (object)
- `name` (string)
- `since`
- `slug` (string)
- `status` (string)
- `statusPage` (string)
- `summary` (string)
- `text` (string)
- `url` (string)

### `list_outages` (~82 tokens)

List outages

Services reporting a problem right now, the newest first: the 25 best-known, unless all is true or a limit is given.

Input parameters:

- `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

Output parameters:

- `services` (array)
- `total` (number): How many report a problem, of which services lists `limit`

### `list_dashboards` (~36 tokens)

List dashboards

The account’s dashboards (the ones this connection can see), with how many services and URL monitors each has and its worst status now.

Output parameters:

- `dashboards` (array)

### `get_stack_status` (~101 tokens)

Get stack status

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.

Input parameters:

- `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

Output parameters:

- `dashboards` (array)

### `get_incident_history` (~123 tokens)

Get incident history

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.

Input parameters:

- `dashboard` (string, required): 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

Output parameters:

- `alreadyGoing` (array)
- `dashboard` (object)
- `from` (string): ISO 8601
- `note` (string)
- `started` (array)
- `to` (string): ISO 8601

### `get_monitor` (~64 tokens)

Get a URL monitor

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.

Input parameters:

- `monitor` (string, required): The monitor’s name, address or id

Output parameters:

- `blockedSince`
- `certificate`
- `changes` (array)
- `days` (array)
- `display` (string)
- `id` (string)
- `last30Days` (object)
- `lastChecks` (array): The last 10 checks, newest first
- `name` (string)
- `notChecked` (boolean)
- `responseMs` (number|null): The median response time of the last 5 checks that answered, in ms
- `since`
- `status` (string): up, slow, down, paused or checking
- `text` (string)

### `get_reliability` (~105 tokens)

Get reliability

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.

Input parameters:

- `dashboard` (string, required): A dashboard’s name or id
- `days`: 7, 30 (the default) or 90

Output parameters:

- `breaksTogether` (array)
- `dashboard` (object)
- `days` (number)
- `medianRecoveryMinutes` (number|null)
- `services` (array)

### `create_dashboard` (~79 tokens)

Create a dashboard

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.

Input parameters:

- `name` (string, required): The dashboard’s name, e.g. "Checkout"
- `services` (array): Slugs to start with, e.g. ["stripe", "shopify"]

Output parameters:

- `added` (array)
- `id` (string)
- `name` (string)
- `notFound` (array)
- `services` (number)
- `url` (string): The dashboard in the app

### `rename_dashboard` (~43 tokens)

Rename a dashboard

Renames a dashboard. Its status page shares the name.

Input parameters:

- `dashboard` (string, required): A dashboard’s name or id
- `name` (string, required): Its new name

Output parameters:

- `id` (string)
- `name` (string)
- `previousName` (string)

### `add_services` (~59 tokens)

Add services

Adds services to a dashboard by slug (search_services finds them), within the plan’s limit.

Input parameters:

- `dashboard` (string, required): A dashboard’s name or id
- `services` (array, required): Slugs, e.g. ["github", "vercel"]

Output parameters:

- `added` (array)
- `already` (array)
- `notFound` (array)
- `services` (number)

### `remove_services` (~54 tokens)

Remove services

Takes services off a dashboard. Their history stays; adding one back shows it again.

Input parameters:

- `dashboard` (string, required): A dashboard’s name or id
- `services` (array, required): Slugs, e.g. ["heroku"]

Output parameters:

- `notOnDashboard` (array)
- `removed` (array)
- `services` (number)

### `add_monitor` (~114 tokens)

Add a URL monitor

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.

Input parameters:

- `dashboard` (string, required): A dashboard’s name or id
- `name` (string): What to call it; the page’s title when left out
- `url` (string, required): The address to watch, e.g. "https://shop.example.com"

Output parameters:

- `dashboard` (object)
- `display` (string)
- `id` (string)
- `name` (string)
- `test` (object): The check before it was added

### `check_monitor` (~47 tokens)

Check a URL monitor now

Checks one of the account’s URL monitors now, as Check now does in the app, and says what it got.

Input parameters:

- `monitor` (string, required): The monitor’s name, address or id

Output parameters:

- `check`
- `checked` (boolean)
- `monitor` (object)

### `pause_monitor` (~51 tokens)

Pause a URL monitor

Pauses a URL monitor, e.g. during a deploy: an open incident ends, and no alerts go out until it’s resumed.

Input parameters:

- `monitor` (string, required): The monitor’s name, address or id

Output parameters:

- `blockedSince`
- `certificate`
- `changes` (array)
- `days` (array)
- `display` (string)
- `id` (string)
- `last30Days` (object)
- `lastChecks` (array): The last 10 checks, newest first
- `name` (string)
- `notChecked` (boolean)
- `responseMs` (number|null): The median response time of the last 5 checks that answered, in ms
- `since`
- `status` (string): up, slow, down, paused or checking
- `text` (string)

### `resume_monitor` (~39 tokens)

Resume a URL monitor

Resumes a paused URL monitor: it’s checked at once and starts fresh.

Input parameters:

- `monitor` (string, required): The monitor’s name, address or id

Output parameters:

- `blockedSince`
- `certificate`
- `changes` (array)
- `days` (array)
- `display` (string)
- `id` (string)
- `last30Days` (object)
- `lastChecks` (array): The last 10 checks, newest first
- `name` (string)
- `notChecked` (boolean)
- `responseMs` (number|null): The median response time of the last 5 checks that answered, in ms
- `since`
- `status` (string): up, slow, down, paused or checking
- `text` (string)

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/app-stackpulse-mcp/stackpulse#diagnostics

## Score history

- 2026-10-23: 69
- 2026-10-22: 69
- 2026-10-21: 68
- 2026-10-20: 68
- 2026-10-19: 67
- 2026-10-18: 67
- 2026-10-17: 67
- 2026-10-16: 66
- 2026-10-15: 66
- 2026-10-14: 65
- 2026-10-13: 65
- 2026-10-12: 64

## Common questions

### 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.

## Links

- Remote endpoint: https://stackpulse.app/mcp
- Website: https://stackpulse.app/mcp
- Changelog RSS feed: https://verifymcp.io/servers/app-stackpulse-mcp/stackpulse.xml
- Changelog JSON feed: https://verifymcp.io/servers/app-stackpulse-mcp/stackpulse.json
- HTML version of this page: https://verifymcp.io/servers/app-stackpulse-mcp/stackpulse