Skip to main content
All down.guide integration capabilities

​
About

This is an MCP connector that gives the Sazabi agent tools from down.guide’s hosted MCP server (mcp.down.guide/mcp). down.guide is a free outage feed that reads about 400 providers’ official status pages. The server exposes seven read-only tools: get_provider (one provider’s live state and a one-line verdict, to answer “is X down?”), list_feed (the newest incidents across providers), get_incident (one incident’s updates, as the provider posted them), search (past and present incidents and providers), check_stack (which providers a manifest or lockfile depends on, and whether any has a problem now), check_dependency (the providers behind one package, API host, or environment variable) and get_leaderboard (the Down Index). The server needs no authentication. down.guide is on by default in every project. Sazabi adds it automatically, so there is nothing to connect, no credentials to enter, and no per-project setup. It is managed by Sazabi: it cannot be renamed or disconnected. What the agent can do:
  • Check whether a provider is down, with its live state and a one-line verdict
  • Browse recent and past incidents across providers
  • Read an incident’s updates exactly as the provider posted them
  • Check a project’s manifest or dependencies for live provider problems
What stays read-only: down.guide also has tools that send feedback or outage reports to down.guide. Sazabi blocks them, so the agent never reports anything on your behalf. check_stack sends the manifest contents it is given to down.guide.

​
Prerequisites

  • None. down.guide is on by default in every project and its MCP server is public.

​
Set up in the dashboard

There is nothing to set up. Find down.guide in Settings > MCP connectors, where it appears as connected and managed by Sazabi.

​
Set up with the CLI

There is nothing to set up with the CLI either. With the Sazabi CLI installed and authenticated (see sazabi mcp-connectors reference), list the project’s connectors to see down.guide:

​
Verify

Open Settings > MCP connectors and confirm down.guide is listed as connected and managed by Sazabi. Then, in a thread, ask the agent whether a provider is down, for example “is GitHub down?”, and confirm it answers with that provider’s current state from down.guide.

​
Troubleshooting

down.guide is not listed — Sazabi can turn the default off for every project at once if the down.guide server has problems. Check back later or contact Sazabi support. The agent says a provider’s state is unknown — down.guide reports not_reporting when it cannot read a provider’s status page, and has no entry for providers it does not cover. The agent should say so instead of calling the provider healthy; check the provider’s own status page.

​
Further reading

Agent tools

How the agent uses connector tools.

MCP connectors

Browse the connector catalog.