A remote MCP server that checks whether popular developer services (such as GitHub and npm) are currently operational, degraded or down.
What you can do
Check all supported services at once and get a one-sentence summary plus per-service detail, optionally narrowed to named services. Look up the current incident state for one named service, including its normalised state, the provider's own description and a link to the status page. List every supported service slug with its human name and status page URL.
When to use it
Useful when an assistant needs to answer whether a dependency or platform is broken right now, for example during debugging or incident triage, or to confirm which providers can be checked at all.
Requirements
A remote streamable HTTP endpoint; no package, account, API key or header is declared. Network access to the endpoint is needed.
Before you install
Only a fixed list of providers is supported; arbitrary URLs are not accepted, and a provider whose status page cannot be read is reported as unknown rather than confirmed down. The registry description mentions turning OpenAPI specs into MCP servers, which does not match the listed status-checking tools.
Enable the server for the chats that should use its tools.
Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.
Use with an agent
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/ai.kaiv%2Fis-it-down/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.
Is anything I depend on broken right now?
Checks every supported provider in parallel and returns a one-sentence summary plus per-service detail. Use this first: it answers the whole question in one call. Optionally narrow with ?services=github,npm. A provider whose status page cannot be read is reported as "unknown", never as healthy.
Parametersservices
check_service_status
Check Service Status
Current incident state for one named service.
Returns the normalised state (operational, degraded, down, unknown), the provider's own description, and a link to the full status page. Use when you already know which provider you care about.
Parametersservicerequired
list_supported_services
List Supported Services
Which services can be checked.
Lists every supported slug with its human name and status page URL. The list is fixed; arbitrary URLs are not accepted.
Takes no parameters.
Version history
1
v1.0.0LatestSep 16, 2026
Score
83%
83% 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.
Reached in the last 30 daysRequired25 pts
Auth declaredRequired10 pts
Tools listedRequired15 pts
DescriptionRequired15 pts
Logo10 pts
Documentation15 pts
Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.
LicenseNot applicable
A hosted service is used under its provider's terms, so no license is expected here. This check is left out of the percentage.