Downdetector
Let your coding agent check whether Stripe, Vercel, or other third-party APIs are down before you burn hours debugging your own code.
Overview
Downdetector MCP is a MCP server for the Operate phase that lets agents check Downdetector for third-party service outages and status signals.
What is this MCP server?
- Query Downdetector for public outage signals on popular SaaS and infrastructure providers
- Run via stdio through npx or install the published mcpb bundle (v1.0.1)
- Fits incident triage when webhooks, OAuth, or payments suddenly fail without a deploy
- No API key in server.json—stdio MCP wiring only
- Pairs with your own logs to separate vendor incidents from application bugs
- Published server version 1.0.1
- Two distribution paths: npm stdio and mcpb v1.0.1
- Transport: stdio (primary npm package)
Community signal: 1 GitHub stars.
What problem does it solve?
When an integration breaks overnight, you cannot tell from code alone whether the provider is having an outage or you shipped a bug.
Who is it for?
Indie SaaS and API builders who depend on many external services and want fast, agent-assisted outage triage without leaving the editor.
Skip if: Teams that need private SLA metrics, synthetic monitoring, or guaranteed official vendor status APIs instead of crowd-sourced Downdetector data.
What do I get? / Deliverables
Your agent can cite current Downdetector outage context so you prioritize vendor waits, status pages, or support tickets instead of pointless hotfixes.
- Agent-callable Downdetector status and outage lookups
- Faster vendor-vs-app root-cause notes during incidents
Recommended MCP Servers
Journey fit
Outage checks belong in Operate because they answer whether production or integration failures are on your side or a vendor’s—after you are already shipping and depending on external services. Monitoring is the canonical shelf for Downdetector-style status lookups that complement uptime pings and error dashboards.
How it compares
MCP monitoring integration for outage crowdsourcing, not a hosted uptime checker or APM skill.
Common Questions / FAQ
Who is Downdetector MCP for?
Solo and small-team builders using MCP agents who ship products that rely on third-party APIs and want quick outage context during incidents.
When should I use Downdetector MCP?
Use it when errors spike after no deploy, OAuth or webhooks fail, or you need to validate whether a dependency is widely reported down before deep debugging.
How do I add Downdetector MCP to my agent?
Register the npm package `downdetector-mcp` with stdio transport and `npx` as the runtime hint, or use the v1.0.1 mcpb bundle from the GitHub release in clients that support MCPB.