# Uptimepage (dev.uptimepage/uptimepage): tool descriptions scored

- tools/list taken: 2026-11-02 (UTC)
- From: [Official MCP Registry](https://registry.modelcontextprotocol.io/v0/servers/dev.uptimepage%2Fuptimepage/versions/latest)
- Connected to: https://mcp.uptimepage.dev/mcp
- Homepage: https://uptimepage.dev/mcp-server
- Repository: https://github.com/uptimepage/uptimepage
- Scoring rules: v2
- Tools: 41
- Average: 64.8 / 100 (Cloudy)
- Near-identical pairs: 2

This page shows how Uptimepage (dev.uptimepage/uptimepage)'s tool descriptions scored, the issues found and the names of its tools and parameters. The descriptions are the server's own: read them where the copy came from.

Forecall asked the URL this server lists in the official MCP Registry for its tools/list once, on the date above, without calling any tool. The server may have changed since.

## Across the server

- Major: 41 tools. Above 40, models choose less accurately.
- Minor: The server's instructions are 3116 characters. Claude Code reads only the first 2,048 by default (Codex 0.154.0 reads them whole). Put what the server is for first.

## Tools

- `acknowledge_incident`: 53 / 100
  - Major: Says nothing about when to use it, or when not to.
  - Minor: String arguments with no constraint or example: id.
- `get_incident_metrics`: 55 / 100
  - Major: Says nothing about when to use it, or when not to.
  - Minor: No `required` list, so every argument is optional.
- `resolve_incident`: 56 / 100
  - Major: Says nothing about when to use it, or when not to.
  - Minor: String arguments with no constraint or example: id.
  - Minor: Required identifiers whose description does not say where the value comes from: id. Name the tool or the place that returns it, or models look it up first.
- `get_maintenance`: 57 / 100
  - Major: Says nothing about when to use it, or when not to.
- `update_status_page_component`: 57 / 100
  - Major: Says nothing about when to use it, or when not to.
  - Minor: Arguments without a description: public_description, public_name, sort_order.
- `get_incident`: 58 / 100
  - Major: Says nothing about when to use it, or when not to.
- `update_status_page`: 58 / 100
  - Major: Says nothing about when to use it, or when not to.
- `get_status_page`: 60 / 100
  - Major: Says nothing about when to use it, or when not to.
- `list_monitors`: 60 / 100
  - Major: Says nothing about when to use it, or when not to.
  - Minor: No `required` list, so every argument is optional.
- `list_notification_channels`: 60 / 100
  - Major: Says nothing about when to use it, or when not to.
- `list_status_pages`: 60 / 100
  - Major: Says nothing about when to use it, or when not to.
  - Minor: No `required` list, so every argument is optional.
- `update_monitor`: 60 / 100
  - Major: Says nothing about when to use it, or when not to.
- `post_incident_update`: 61 / 100
  - Major: Says nothing about when to use it, or when not to.
  - Minor: String arguments with no constraint or example: id.
  - Minor: Required identifiers whose description does not say where the value comes from: id. Name the tool or the place that returns it, or models look it up first.
- `resume_monitor`: 61 / 100
  - Major: Says nothing about when to use it, or when not to.
- `unpublish_incident`: 61 / 100
  - Major: Says nothing about when to use it, or when not to.
- `get_org_health`: 62 / 100
  - Major: Says nothing about when to use it, or when not to.
- `get_flow_runs`: 63 / 100
- `get_flow_step_trend`: 63 / 100
- `get_monitor_history`: 63 / 100
  - Major: Says nothing about when to use it, or when not to.
- `get_org_usage`: 63 / 100
  - Major: Says nothing about when to use it, or when not to.
- `list_status_page_viewers`: 63 / 100
  - Major: Says nothing about when to use it, or when not to.
- `post_maintenance_update`: 63 / 100
  - Major: Says nothing about when to use it, or when not to.
- `set_monitor_state`: 63 / 100
  - Major: Says nothing about when to use it, or when not to.
  - Minor: Arguments without a description: state.
- `update_maintenance`: 63 / 100
  - Major: Says nothing about when to use it, or when not to.
- `list_maintenance`: 65 / 100
  - Major: Says nothing about when to use it, or when not to.
  - Minor: No `required` list, so every argument is optional.
- `list_monitor_groups`: 65 / 100
  - Major: Says nothing about when to use it, or when not to.
- `list_tags`: 65 / 100
  - Major: Says nothing about when to use it, or when not to.
- `update_monitor_group`: 65 / 100
  - Major: Says nothing about when to use it, or when not to.
- `pause_monitor`: 66 / 100
- `publish_incident`: 66 / 100
  - Major: Says nothing about when to use it, or when not to.
  - Minor: String arguments with no constraint or example: id.
- `create_status_page`: 68 / 100
- `list_incidents`: 68 / 100
  - Major: Says nothing about when to use it, or when not to.
  - Minor: No `required` list, so every argument is optional.
- `get_monitor`: 70 / 100
- `add_status_page_components`: 71 / 100
- `cancel_maintenance`: 73 / 100
- `run_check_now`: 73 / 100
  - Major: Says nothing about when to use it, or when not to.
- `list_variables`: 75 / 100
- `create_monitors`: 76 / 100
- `list_regions`: 80 / 100
- `create_maintenance`: 83 / 100
- `create_monitor`: 84 / 100
  - Minor: Arguments without a description: check.

Is your server listed here and you would rather it were not? Email support@forecall.dev, and we will take it off within 7 days.

[All scored servers](https://forecall.dev/en/servers)