# Stackpulse Muse connector

From musedirectory.ai, the independent directory of Meta Muse connectors. Not affiliated with Meta.

## Stackpulse

Monitor status and uptime of 9,700+ services and your own website endpoints.

- Record: https://musedirectory.ai/connector/stackpulse
- Category: Productivity
- Developer: Stackpulse (https://stackpulse.app/mcp)
- Muse status: Extra setup. Not in Muse's Connectors list yet. Muse can still use it: its page gives you a request to paste into Muse.
- Health: Working, 838ms, checked 2026-10-29T09:16:09Z
- Endpoint: https://stackpulse.app/mcp
- Auth: No account needed; Pricing: unknown
- Screening: Screened, no issues found (2026-10-29T02:26:33Z)
- Source: Found in the official MCP Registry (app.stackpulse/mcp) https://registry.modelcontextprotocol.io/v0/servers?search=app.stackpulse%2Fmcp

Connects to Stackpulse dashboards to check real-time status of services like GitHub, AWS, Stripe and others. View incidents, outages, reliability trends, and monitor your own URLs. Requires Stackpulse Pro account.

Example request: "Check if GitHub is down right now and see the status of all services my business depends on."

How to connect: Not in Muse's Connectors list yet, but Muse can still use it. Paste this into Muse: "Use Stackpulse to help me. It is a free service with an MCP server at https://stackpulse.app/mcp. It does not need an API key. Ask me before you share anything with it." Muse asks before it shares anything with the app's site. Meta does not review apps used this way, so only use ones you trust. We tested this in the Muse app on September 24, 2026: Muse used an app's link directly this way and returned a live answer.

Tools:
- 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.
- get_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.
- list_outages: Services reporting a problem right now, the newest first: the 25 best-known, unless all is true or a limit is given.
- 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.
- 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.
- 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.
- get_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.
- 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 t
- create_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.
- rename_dashboard: Renames a dashboard. Its status page shares the name.
- add_services: Adds services to a dashboard by slug (search_services finds them), within the plan’s limit.
- remove_services: Takes services off a dashboard. Their history stays; adding one back shows it again.
- add_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.
- check_monitor: Checks one of the account’s URL monitors now, as Check now does in the app, and says what it got.
- pause_monitor: Pauses a URL monitor, e.g. during a deploy: an open incident ends, and no alerts go out until it’s resumed.
- resume_monitor: Resumes a paused URL monitor: it’s checked at once and starts fresh.

Screening checks:
- MCP handshake: pass (Answered in 279ms)
- Domain against threat feeds (Cloudflare security DNS): pass (stackpulse.app not flagged)
- Published packages against the OSV malicious-package database: n/a (No npm or PyPI package published)
- Hidden instructions or invisible characters in tool text: pass (16 tools read, nothing found)
- Inputs asking for passwords, card numbers or seed phrases: pass (None found)
- Domain and redirects: pass (No redirects off the domain)
- AI review of purpose and tool behavior: pass (No concerns)