Healthchecks vs Statuscraft — MCP Server Comparison | AllMCPs
Side-by-Side Model Context Protocol Comparison
Healthchecks vs Statuscraft
In-depth architectural comparison of the Healthchecks and Statuscraft MCP servers. Compare execution transports, security boundaries, tool capabilities, quality scores, and ready-to-paste client installation snippets for Claude, Cursor, Windsurf, and VS Code.
At a Glance & Executive Verdict
Healthchecks
Monitoring · Local stdio
Quality: 55/100 (Good) | Auth: No auth required
Statuscraft
Monitoring · Local stdio
Quality: 57/100 (Good) | Auth: No auth required
Verdict Summary: Choose Healthchecks if you need specialized Monitoring tools running via a local process. Choose Statuscraft if your workspace requires Monitoring integration with local subprocess execution. Both servers can be configured concurrently in your client's mcpServers manifest.
Which MCP Server Should You Choose?
Choose Healthchecks when:
You need dedicated capabilities in the Monitoring domain.
You prefer local stdio subprocess transport architecture.
Your security boundary fits: No auth required (Free / Open Source).
Healthchecks is categorized under Monitoring and uses a local stdio subprocess. In contrast, Statuscraft belongs to Monitoring using local stdio subprocess. Select Healthchecks when you need capabilities focused on monitoring and Statuscraft when you require tools for monitoring.
Creates a check. Notifies every integration unless `channels` says otherwise
update_check
Changes the given fields. `channels` replaces the list rather than adding to it; an empty list is refused
pause_check
Stops the check expecting pings — and alerting. `resume_check` puts it back
resume_check
Puts a paused check back into the `new` state
Statuscraft Tools (5)
get_status
Check the live status of a specific service (e.g. 'github', 'openai', 'stripe'). Returns operational/degraded/partial_outage/major_outage/maintenance.
get_all_status
Check the live status of ALL tracked services at once. Returns a summary grouped by status — useful for a quick health check across the stack.
list_services
List services tracked by StatusCraft, with their IDs and tags. Use this to discover service IDs for get_status. Supports name/ID search and tag filtering. Results are paginated (100 per page) — pass page to get more.
check_multiple
Check the live status of a specific list of services in parallel. Faster than calling get_status repeatedly.
refresh_status
Force a fresh live fetch for one or all services, bypassing the 60-second cache. Use this when you need the absolute latest status — e.g. during an active incident or immediately after a known outage ends.
Inspect, create and adjust Healthchecks cron and uptime checks, and read why one failed
MCP server that checks the live status of 3831 software services in real time. Ask your AI agent "is GitHub down?" or "what's wrong with Sentry?" — and get a live answer pulled directly from official status pages, including full incident detail when something is broken. npx -y github:jabbawocky/statuscraft