search_services
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.
queryrequiredapp.stackpulsePublished by stackpulse.appOfficial publisherv1.0.0Updated Oct 24, 2026
8,900+ services' status, and your Stackpulse dashboards and URL monitors. Needs Pro.
Lets an assistant look up status pages for 9,700+ services and manage Stackpulse dashboards and URL monitors.
Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.
Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.
Read https://sourceweft.com/mcp/app.stackpulse%2Fmcp/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.Add this to your client's mcpServers config.
{
"mcpServers": {
"stackpulse": {
"type": "http",
"url": "https://stackpulse.app/mcp"
}
}
}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.
queryrequiredGet 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.
slugrequiredList outages
Services reporting a problem right now, the newest first: the 25 best-known, unless all is true or a limit is given.
alllimitList 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.
Takes no parameters.
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.
includedashboardGet 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.
todaysfromdashboardrequiredGet 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.
monitorrequiredGet 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.
daysdashboardrequiredCreate 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.
namerequiredservicesRename a dashboard
Renames a dashboard. Its status page shares the name.
namerequireddashboardrequiredAdd services
Adds services to a dashboard by slug (search_services finds them), within the plan’s limit.
servicesrequireddashboardrequiredRemove services
Takes services off a dashboard. Their history stays; adding one back shows it again.
servicesrequireddashboardrequiredAdd 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.
urlrequirednamedashboardrequiredCheck 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.
monitorrequiredPause 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.
monitorrequiredResume a URL monitor
Resumes a paused URL monitor: it’s checked at once and starts fresh.
monitorrequired83% of the applicable checks met
How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.
Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.
A hosted service is used under its provider's terms, so no license is expected here. This check is left out of the percentage.