Skip to content

Stackpulse MCP server

app.stackpulse/mcpstackpulse.appstreamable-httpv1.0.0Scanned

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

16 tools: 1 can delete or cancel things, 7 change things and 8 only read.

Tools: 1 delete, 0 irreversible, 7 write, 8 read.
  • Reads private data · 0
  • Reads text others write · 6
  • Can send data out · 1
  • No findings

Tools listed without sign-in. Remote posture

With Anlyon

1 tool here can delete or cancel things. Govern it.

  • Anlyon lists the tools and adopts none.
  • Each tool you adopt gets approvals and receipts.
  • Your agent never holds the key.
Govern this server →

A tool your agent calls directly is not routed through Anlyon and is not governed by it. Anlyon Radar only lists and labels, and these labels are the same either way.

What the Stackpulse MCP server can do

The Stackpulse MCP server is published by stackpulse.app, a domain the MCP Registry verified. It has 16 tools. It can delete or cancel things (1 tool: remove_services) and create or change data (7 tools: create_dashboard, rename_dashboard, add_services, add_monitor and 3 more). 8 tools only read.

6 tools bring in text other people can write (list_dashboards, get_stack_status, get_monitor and 3 more); 1 tool can send data out of your system (add_monitor).

None of the fixed checks matched anything in its tool definitions. That is not a safety guarantee.

Its remote endpoint lists its tools without sign-in.

Last scanned Nov 12, 2026, version 1.0.0.

Tools

Grouped by what each tool does, most consequential first. Open one for its reasons and full description; descriptions are the publisher's own words.

16 tools

Deletes or cancels 1Claude Code: deny
  • remove_servicesTakes services off a dashboard.No findings

    Why it is in this group

    • The name "remove_services" says "remove": a word for removing or ending something.
    • The server marks it destructive (destructiveHint: true).
    Description, as the server wrote it
    Takes services off a dashboard. Their history stays; adding one back shows it again.

    Annotations the server declares

    • title: Remove services
    • readOnlyHint: false
    • destructiveHint: true
    • idempotentHint: true
    • openWorldHint: false
Changes things 7Claude Code: ask
  • add_monitorWatches 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).Reads text others writeCan send data outNo findings

    Why it is in this group

    • The name "add_monitor" says "add": a word for a change.

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    • outboundThe input takes a URL (input.url): a request to a URL can carry data to whoever runs it.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • title: Add a URL monitor
    • readOnlyHint: false
    • destructiveHint: false
    • idempotentHint: false
    • openWorldHint: true
  • add_servicesAdds services to a dashboard by slug (search_services finds them), within the plan’s limit.No findings

    Why it is in this group

    • The name "add_services" says "add": a word for a change.
    Description, as the server wrote it
    Adds services to a dashboard by slug (search_services finds them), within the plan’s limit.

    Annotations the server declares

    • title: Add services
    • readOnlyHint: false
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
  • check_monitorChecks one of the account’s URL monitors now, as Check now does in the app, and says what it got.Reads text others writeNo findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    Description, as the server wrote it
    Checks one of the account’s URL monitors now, as Check now does in the app, and says what it got.

    Annotations the server declares

    • title: Check a URL monitor now
    • readOnlyHint: false
    • destructiveHint: false
    • idempotentHint: false
    • openWorldHint: true
  • create_dashboardMakes a dashboard with a name and, optionally, services by slug (search_services finds them), within the plan’s dashboards and services.No findings

    Why it is in this group

    • The name "create_dashboard" says "create": a word for a change.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • title: Create a dashboard
    • readOnlyHint: false
    • destructiveHint: false
    • idempotentHint: false
    • openWorldHint: false
  • pause_monitorPauses a URL monitor, e.g.No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    Description, as the server wrote it
    Pauses a URL monitor, e.g. during a deploy: an open incident ends, and no alerts go out until it’s resumed.

    Annotations the server declares

    • title: Pause a URL monitor
    • readOnlyHint: false
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
  • rename_dashboardRenames a dashboard.No findings

    Why it is in this group

    • The name "rename_dashboard" says "rename": a word for a change.
    Description, as the server wrote it
    Renames a dashboard. Its status page shares the name.

    Annotations the server declares

    • title: Rename a dashboard
    • readOnlyHint: false
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
  • resume_monitorResumes a paused URL monitor: it’s checked at once and starts fresh.No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    Description, as the server wrote it
    Resumes a paused URL monitor: it’s checked at once and starts fresh.

    Annotations the server declares

    • title: Resume a URL monitor
    • readOnlyHint: false
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
Only reads 8Show 8 read-only tools
  • get_incident_historyIncidents 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.No findings

    Why it is in this group

    • The name "get_incident_history" says "get": a word for reading.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • title: Get incident history
    • readOnlyHint: true
    • openWorldHint: false
  • get_monitorOne 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 c…Reads text others writeNo findings

    Why it is in this group

    • The name "get_monitor" says "get": a word for reading.

    What it can reach

    • untrusted-inputThe description's first sentence says "url": it reads web pages, which anyone can write.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • title: Get a URL monitor
    • readOnlyHint: true
    • openWorldHint: false
  • get_reliabilityHow 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…Reads text others writeNo findings

    Why it is in this group

    • The name "get_reliability" says "get": a word for reading.

    What it can reach

    • untrusted-inputThe description's first sentence says "url": it reads web pages, which anyone can write.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • title: Get reliability
    • readOnlyHint: true
    • openWorldHint: false
  • get_serviceOne service’s status from its official status page: what’s wrong, the components with a problem, 90 days of history and recent incidents.No findings

    Why it is in this group

    • The name "get_service" says "get": a word for reading.
    Description, as the server wrote it
    One service’s status from its official status page: what’s wrong, the components with a problem, 90 days of history and recent incidents.

    Annotations the server declares

    • title: Get a service
    • readOnlyHint: true
    • openWorldHint: false
  • get_stack_statusWhat’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.Reads text others writeNo findings

    Why it is in this group

    • The name "get_stack_status" says "get": a word for reading.

    What it can reach

    • untrusted-inputThe description's first sentence says "url": it reads web pages, which anyone can write.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • title: Get stack status
    • readOnlyHint: true
    • openWorldHint: false
  • list_dashboardsThe account’s dashboards (the ones this connection can see), with how many services and URL monitors each has and its worst status now.Reads text others writeNo findings

    Why it is in this group

    • The name "list_dashboards" says "list": a word for reading.

    What it can reach

    • untrusted-inputThe description's first sentence says "url": it reads web pages, which anyone can write.
    Description, as the server wrote it
    The account’s dashboards (the ones this connection can see), with how many services and URL monitors each has and its worst status now.

    Annotations the server declares

    • title: List dashboards
    • readOnlyHint: true
    • openWorldHint: false
  • list_outagesServices reporting a problem right now, the newest first: the 25 best-known, unless all is true or a limit is given.No findings

    Why it is in this group

    • The name "list_outages" says "list": a word for reading.
    Description, as the server wrote it
    Services reporting a problem right now, the newest first: the 25 best-known, unless all is true or a limit is given.

    Annotations the server declares

    • title: List outages
    • readOnlyHint: true
    • openWorldHint: false
  • search_servicesFinds services in the catalog of 9,700+ status pages by name, with their status now.No findings

    Why it is in this group

    • The name "search_services" says "search": a word for reading.
    Description, as the server wrote it
    Finds services in the catalog of 9,700+ status pages by name, with their status now. Use it to find a service’s slug.

    Annotations the server declares

    • title: Search services
    • readOnlyHint: true
    • openWorldHint: false

This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.

Exfil surface

Which tools read private data, which read text someone else can write, and which can send data out. One of each is a path a prompt injection can use.

No private-data, untrusted-input, outbound path in this server alone: no tool is tagged private-data.

Reads private data0
Reads files, mail, messages, databases, secrets, calendars or repositories.
Reads text others write6
Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
Can send data out1
Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.

Other servers in the same agent add their own tools to these paths. Audit your whole setup to see them together.

Remote posture

What anyone on the internet sees at the remote endpoint: an anonymous initialize and tools/list, and the public OAuth metadata.

Tools listed without sign-in

Looked at Nov 20, 2026, 18:30 UTC, unchanged since Oct 22, 2026. No credentials were sent and no tool was called. What is looked at.

Reachable
yes
HTTP status of an anonymous initialize
200
tools/list served without credentials
yes
Tools that change things, listed without credentials
8
Protocol version
2025-06-18
WWW-Authenticate on 401
not observed
resource_metadata in WWW-Authenticate
not observed
RFC 9728 protected resource metadata
https://stackpulse.app/.well-known/oauth-protected-resource/mcp
Authorization servers
https://stackpulse.app
Legacy HTTP+SSE transport
no
Dynamic client registration
yes
Client ID metadata documents
yes
  • HighThe whole server

    The endpoint served tools/list without credentials, and the list has 8 tools that change things (1 destructive, 7 write). Whether a call also works without credentials was not tested: tools are never called.

    Matched text

    https://stackpulse.app/mcp: tools/list returned 16 tools to an anonymous client, including remove_services (destructive), create_dashboard (write), rename_dashboard (write), add_services (write), add_monitor (write) and 3 more

    What this check looks for

Findings

Matches of fixed checks, with the text they matched.

No check matched anything in these tool definitions. That is not a safety guarantee.

History

Changes to its tool definitions and to its remote endpoint, newest first.

No change seen yet. Its tools are rescanned every day, and a remote endpoint is looked at once a week.

Install

Pinned to version 1.0.0. Values in angle brackets are yours to fill in.

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

Run in a terminal.

Claude Code permissions

Allow the reads, ask before a change or a way out, deny the deletes. Paste into .claude/settings.json.

.claude/settings.json
{
  "permissions": {
    "allow": [
      "mcp__stackpulse__search_services",
      "mcp__stackpulse__get_service",
      "mcp__stackpulse__list_outages",
      "mcp__stackpulse__list_dashboards",
      "mcp__stackpulse__get_stack_status",
      "mcp__stackpulse__get_incident_history",
      "mcp__stackpulse__get_monitor",
      "mcp__stackpulse__get_reliability"
    ],
    "ask": [
      "mcp__stackpulse__create_dashboard",
      "mcp__stackpulse__rename_dashboard",
      "mcp__stackpulse__add_services",
      "mcp__stackpulse__add_monitor",
      "mcp__stackpulse__check_monitor",
      "mcp__stackpulse__pause_monitor",
      "mcp__stackpulse__resume_monitor"
    ],
    "deny": [
      "mcp__stackpulse__remove_services"
    ]
  }
}

Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. A read that can send data out (it takes a URL, say) asks first too. It assumes the server is installed as stackpulse. Review it before you use it.

Capability tags behind 6 rules
  • mcp__stackpulse__list_dashboards untrusted-input
  • mcp__stackpulse__get_stack_status untrusted-input
  • mcp__stackpulse__get_monitor untrusted-input
  • mcp__stackpulse__get_reliability untrusted-input
  • mcp__stackpulse__add_monitor untrusted-input, outbound
  • mcp__stackpulse__check_monitor untrusted-input

Pin

Keep the decision: fail CI when the tools change, follow every change, or show a badge.

Pin in CI

Fail a build when the tools you reviewed are not the tools the server serves today.

curl -s "https://radar.anlyon.com/api/v1/servers/app.stackpulse/mcp/verify?hash=02efa15f0e7d6908749f2890f18cb82c2ae7ff2faa599df7139a7b66413e4589" | jq -e '.changed == false'

Pinned hash 02efa15f0e7d, from Nov 12, 2026, 03:18 UTC.

Watch

Get told when its tools change: a new tool, a new description, a new class.

https://radar.anlyon.com/servers/app.stackpulse/mcp/changes.xml

An Atom feed. Works in any feed reader or Slack's RSS app.

Badge

Anlyon Radar badge for app.stackpulse/mcp
[![Anlyon Radar](https://radar.anlyon.com/badge/app.stackpulse/mcp.svg)](https://radar.anlyon.com/servers/app.stackpulse/mcp)

Source: MCP Registry. Synced Oct 21, 2026, 17:45 UTC.

Stackpulse MCP server: questions and answers

Answered from the scan above, not from the publisher's description.

Is the Stackpulse MCP server safe?

No scan can promise that. What its definitions show: 16 tools, 8 of which can change, send or delete something, and 0 findings from fixed checks. Allow the reads, ask before each change, and deny the deletes; the permissions block on this page does that.

Can the Stackpulse MCP server delete data?

Yes. 1 tool can delete, cancel or revoke something: remove_services.

Can the Stackpulse MCP server do things that cannot be undone?

No tool is classed as irreversible: none of them sends, pays, publishes or merges, going by their definitions.

What tools does the Stackpulse MCP server have?

16 tools: 1 destructive, 7 write, 8 read. remove_services, create_dashboard, rename_dashboard, add_services, add_monitor, check_monitor, pause_monitor, resume_monitor and 8 more.

Does the Stackpulse MCP server need sign-in or OAuth?

Its remote endpoint listed its tools to an anonymous client, without sign-in.

Does the Stackpulse MCP server send data to outside services?

1 tool can carry data out (it sends, posts or publishes, or takes a recipient, channel or URL): add_monitor.

Has the Stackpulse MCP server changed its tools?

Not since Anlyon Radar started tracking it. Last scanned Nov 12, 2026.