downdetector-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| downdetectorA | Get current status and outage reports for a service from Downdetector |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 1 tool
With only one tool, there is no possibility of confusion between tools. The tool's purpose is clearly described.
The single tool name 'downdetector' is consistent by default; no naming conflicts exist.
A single tool is too few for a service monitoring domain like Downdetector, which typically requires multiple operations (e.g., listing services, historical data). The count feels thin.
The server only provides a single status check, missing other essential operations such as listing monitored services, viewing historical outages, or managing alerts. This is a significant gap.