mcp-uptime-kuma

Get Status Page

getStatusPage

Fetch a published status page by its slug to get the full configuration, including ordered groups, monitors, and active incidents.

Instructions

Returns the full configuration of a status page by slug, including the ordered list of groups, the monitors inside each group, and active incidents. Only works for published status pages (fetches the public /api/status-page/{slug} endpoint).

Input Schema

TableJSON Schema

Name	Required	Description	Default
`slug`	Yes	The status page slug (the URL-safe identifier)

Output Schema

TableJSON Schema

Name	Required	Description
`ok`	Yes
`msg`	No
`config`	No
`incidents`	No	Active incidents on the status page
`publicGroupList`	No	Ordered groups with their monitorList

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedv0.11.15Sep 9, 2026
- changedOutput schema / properties / incidents / items / additionalProperties
```
Previous value: -{}New value: +true
```
- changedOutput schema / properties / publicGroupList / items / additionalProperties
```
Previous value: -{}New value: +true
```

Changed2 schema fields changedv0.11.9Aug 21, 2026

changedInput schema / $schema

Previous value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"

changedOutput schema / $schema

Previous value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"

First observedv0.0.0-devAug 7, 2026

TDQS

A4/5.0

Behavior4/5

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

With no annotations provided, the description carries the full behavioral burden. It discloses that the tool fetches a public endpoint, only works for published status pages, and returns a specific configuration structure. It does not detail failure behavior for unpublished slugs, but the constraints and read-only nature are clearly conveyed.

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?

The description is two sentences with no filler. The primary purpose is front-loaded, and the endpoint constraint is efficiently appended in a parenthetical. Every sentence earns its place.

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

Completeness4/5

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

For a single-parameter read tool with an output schema present, the description is largely complete: it names the endpoint, states the published-page restriction, and summarizes the response contents. It could explicitly mention the outcome for unpublished or invalid slugs, but this is a minor gap given the existing structure.

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?

The schema already documents the single slug parameter at 100% coverage, including its URL-safe identifier nature. The description references 'by slug' but adds no meaningful new semantic detail beyond what the schema provides, so the baseline score of 3 is appropriate.

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

Purpose5/5

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

The description clearly states a specific verb and resource: it returns the full configuration of a single status page by slug. It also enumerates what the response contains (groups, monitors, incidents), which distinguishes it from sibling tools like listStatusPages or updateStatusPage.

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?

The description provides important context by noting that it only works for published status pages and fetches the public endpoint. However, it does not explicitly state when to prefer this tool over alternatives such as listStatusPages or getMonitorSummary, leaving the usage decision mostly implicit.

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