Apistatuscheck MCP Server vs Stackpulse
A side-by-side look at the Apistatuscheck MCP Server and Stackpulse MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
S
StackpulseMonitoring · Remote HTTP/SSE8,900+ services' status, and your Stackpulse dashboards and URL monitors. Needs Pro.51GoodAuth: not declaredVerdict: choose Apistatuscheck MCP Server for monitoring work over a hosted endpoint; choose Stackpulse for monitoring over a hosted endpoint. You can also run both side by side in one mcpServers block.
Which MCP server should you choose?
Choose Apistatuscheck MCP Server when
- You need dedicated capabilities in the Monitoring domain.
- You prefer a remote HTTP/SSE transport.
- Its auth model fits you: No auth required.
- You have the keys it needs:
ASC_BASE_URL. - You want tools like
list_apis, search_apis, get_api_status.
SChoose Stackpulse when
- You need dedicated capabilities in the Monitoring domain.
- You prefer a remote HTTP/SSE transport.
- You want tools like
search_services, get_service, list_outages.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | S Stackpulse | |
|---|---|---|
| Category | Monitoring | Monitoring |
| Quality signal | 53/100 · Good | 51/100 · Good |
| Install command | Confirmed | Confirmed |
| Transport | Remote HTTP/SSE | Remote HTTP/SSE |
| Auth | No auth required | Not declared |
| Pricing | Free | Not declared |
| Required env vars | ASC_BASE_URL | None listed |
| Verified owner | Community listing | Community listing |
| GitHub stars | 1 | — |
| Directory activity | 3 views 0 installs 0 upvotes | 1 views 0 installs 0 upvotes |
| Tools | 8 | 16 |
| Full listing | View Apistatuscheck MCP Server | View Stackpulse |
Tools & capabilities
Apistatuscheck MCP Server tools 8
list_apisList the APIs and developer platforms this service monitors, optionally filtered by category. Statuses come from the most recently published monitor snapshot, not a live probe, and can be up to a day old — check monitorCheckedAt, and call get_api_status when the caller needs the status right now.search_apisFind monitored APIs by name, slug, category or description. Use this to resolve a product name the user mentioned into the slug the other tools take.get_api_statusProbe a monitored API endpoint at call time and return up/degraded/down with the response time. This is the tool to reach for when a user asks "is X down?" — it makes a real request rather than reading the hourly cache.list_down_apisEverything the most recent monitor run found down or degraded, across all categories. Returns an empty list when the monitor snapshot is missing or stale — an empty list is therefore not proof that everything is healthy; check monitorLastRun.get_uptime_historyUptime percentages, response-time stats and recorded data points for one API over a time range. History is retained for 30 days; an API added recently will have few or no data points, which reads as null percentages rather than 100%.get_incident_historyReal incidents a vendor published on its own status page, newest first, with start/end times, duration, severity, affected components and a link to the vendor’s incident page. Use this for "has X been flaky lately?" — it is the vendor’s own record, not our probes. Services without a public Statuspage endpoint return covered:false rather than an empty list.rank_reliabilityGiven several service slugs, return a scorecard ranked worst-first: incident count, total downtime minutes, mean time to resolve, and the longest incident over a window. Use this to answer "which vendor in my stack is least reliable?" — it compares services across vendors, which a vendor’s own monitoring tool cannot. Services with no archive are listed separately as uncovered instead of being ranked as flawless.list_categoriesCategory slugs and how many monitored APIs sit in each. Use the slugs with list_apis.
Stackpulse tools 16
search_servicesFinds services in the catalog of 9,700+ status pages by name, with their status now. Use it to find a service’s slug.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.list_outagesServices reporting a problem right now, the newest first: the 25 best-known, unless all is true or a limit is given.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.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. A URL monitor that’s down lists what started around then. Without a dashboard, every dashboard.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. As far back as the plan’s history goes.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 checks.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 one long minor issue makes it low), time in each severity, incidents and recovery, and what tends to break together.create_dashboardMakes 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_dashboardRenames a dashboard. Its status page shares the name.add_servicesAdds services to a dashboard by slug (search_services finds them), within the plan’s limit.remove_servicesTakes services off a dashboard. Their history stays; adding one back shows it again.- +4 more on the listing page
Ready-to-paste client configs
Paste either block (or both) into your client config, e.g. claude_desktop_config.json or ~/.cursor/mcp.json. We only show a config when the install command is confirmed.
Apistatuscheck MCP Server
{
"mcpServers": {
"shibley-apistatuscheck-mcp-server": {
"url": "https://apistatuscheck.com/api/mcp"
}
}
}
Stackpulse
{
"mcpServers": {
"stackpulse": {
"url": "https://stackpulse.app/mcp"
}
}
}
Frequently asked questions
Apistatuscheck MCP Server is categorized under Monitoring and uses a remote HTTP/SSE transport. Stackpulse belongs to Monitoring and uses a remote HTTP/SSE transport. Pick Apistatuscheck MCP Server for monitoring work and Stackpulse for monitoring.
Copy the mcpServers block from the config section on this page into your client's config (for example claude_desktop_config.json or ~/.cursor/mcp.json), then fully restart the client.
Apistatuscheck MCP Server is listed as free. Auth: no auth required. Stackpulse has no declared pricing — check the project's own site. If a server needs environment variables such as API keys, define them under the env key in your client's MCP config.
Yes. MCP clients support multiple servers: add shibley-apistatuscheck-mcp-server and stackpulse as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, Apistatuscheck MCP Server has a quality signal of 53/100 (Good) with 3 views, 0 installs and 1 GitHub stars. Stackpulse has 51/100 (Good) with 1 views, 0 installs and 0 GitHub stars.