downdetector-mcp

downdetector

Check real-time service status and outage reports for any online service. Identify if a service is down or experiencing issues.

Instructions

Get current status and outage reports for a service from Downdetector

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "serviceName": "<serviceName>"
    },
    "name": "downdetector"
  }
}

Input Schema

Name	Required	Description	Default
`domain`	No	Optional domain for the service (e.g., "co.uk", "it", "fr"). Try to use this if you know the country the user is based in. Default: "com"
`serviceName`	Yes	The name of the service to check (e.g., "steam", "netflix", "twitter", "claude-ai")

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.1Jul 29, 2026

TDQS

A3.5/5.0

Behavior3/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

No annotations are provided, so the description must fully disclose behavioral traits. It indicates a read-only operation ('Get'), but does not mention potential limitations, authentication requirements, or rate limits. The description is minimally transparent.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Single sentence that is front-loaded with the purpose. Every word earns its place; no filler. Excellent conciseness.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given no output schema, the description could mention return value structure or behavior (e.g., returns JSON). Without that, completeness is adequate but not thorough for a tool with no additional schema coverage.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Input schema has 100% coverage with clear parameter descriptions. The tool's description adds no additional information beyond the schema. Baseline score of 3 is appropriate as the schema does the heavy lifting.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

Description clearly states the verb 'Get', resource 'status and outage reports', and the source 'Downdetector'. It avoids tautology and gives a specific purpose, distinguishing it within any sibling context.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

No explicit guidance on when to use vs alternatives. The description implies usage for checking service status, but lacks exclusions or alternative tool references. With no sibling tools provided, the baseline for guidance is limited.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server

Other Tools

downdetectorA