@mnicole-dev/updown-mcp-server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| UPDOWN_API_KEY | Yes | Your Updown.io API key. Get it from https://updown.io/settings/edit |
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 |
|---|---|
| list-checksA | List all monitoring checks in your Updown.io account. |
| get-checkA | Get details for a single monitoring check, optionally including metrics. |
| create-checkC | Create a new monitoring check. |
| update-checkC | Update an existing monitoring check. |
| delete-checkA | Delete a monitoring check. |
| get-check-downtimesB | Get the downtime history for a monitoring check. |
| get-check-metricsA | Get performance metrics for a monitoring check over a time range. |
| list-nodesA | List all Updown.io monitoring nodes (global probe locations). |
| list-recipientsA | List all alert recipients configured in your Updown.io account. |
| create-recipientB | Create a new alert recipient. |
| delete-recipientC | Delete an alert recipient. |
| list-status-pagesA | List all public status pages in your Updown.io account. |
| create-status-pageC | Create a new public status page. |
| update-status-pageC | Update an existing status page. |
| delete-status-pageB | Delete a status page. |
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 15 tools
Each tool clearly targets a distinct resource and action: checks, nodes, recipients, and status pages each have their own list/get/create/update/delete where applicable, with no overlapping purposes. The specialized check metrics and downtimes tools are unambiguous subsets of check data.
All tool names follow a consistent kebab-case verb-noun pattern (e.g., list-checks, create-status-page). The pattern is predictable across all resources, with compound names like get-check-downtimes extending the same convention.
15 tools is within the well-scoped 3-15 range for a domain-specific server. Each tool maps to a real operation on the Updown.io API, and the count feels right for covering the main resources without unnecessary bloat.
Checks and status pages have full CRUD coverage, plus additional check-specific operations. Recipients lack an update operation, but since recipients are likely simple contact addresses, create/delete/list may be sufficient. Overall the surface covers the core domain well with only minor gaps.