Remote MCP server to run your Atako AI agents: chat, projects, files, integrations and channels.
- Passed: Handshake
- Passed: Tools listed
- Passed: Updated recently
Median latency 132 ms · Last checked
Explore
Evidence for your next connection.
Independent measurements of remote MCP servers. Every observation has a timestamp.
Read-only probesMCP server · Code & DevOps
Read status pages, incidents and monitors, and post incidents and maintenance in StatusPage.me.
1 failed · 8 not measured
Median of successful probes over 7 days
Share of countable probes over 30 days, including daily rollups. Auth challenges are excluded.
Tool definitions returned by this server
Independent monitoring
Outdated check
Last connection measurement is over 24 hours old. Current availability is unknown.
Last checked| Test area | Passed | Failed | Unmeasured |
|---|---|---|---|
ConnectionCan a client connect and discover tools? | 5 | 0 | 0 |
Reliability & speedDoes it respond consistently and quickly? | 0 | 0 | 4 |
Access & authenticationWhat is required to use this server? | 1 | 0 | 2 |
Tool qualityAre the tool definitions usable by an agent? | 3 | 1 | 0 |
Publisher identityCan the publisher be traced to its source? | 4 | 0 | 2 |
Unmeasured means there is not enough evidence to decide. How these checks work
Start using StatusPage.me MCP by usefulapi
Choose your client, copy the configuration, then enable the server in your client’s MCP settings.
Run this command in your terminal, then restart Claude Code.
Claude Code
claude mcp add --transport http statuspage-me-mcp-by-usefulapi https://statuspage-me.usefulapi.io/mcpCapabilities
Add a timeline update to an incident, optionally with a new incident state. It appears on the public page at once. API: POST /user/api/v1/incidents/{id}/updates.
DiscoveredCreate a new incident on a status page. It appears on the public page at once. With notify_subscribers true, subscribers receive a message. API: POST /user/api/v1/incidents.
DiscoveredSchedule a maintenance window on a status page, with start and end times. With notify_subscribers true, subscribers receive a message. API: POST /user/api/v1/maintenances.
DiscoveredGet one incident by id, with its status and timeline. API: GET /user/api/v1/incidents/{id}.
DiscoveredGet one maintenance window by id. API: GET /user/api/v1/maintenances/{id}.
DiscoveredGet one monitor by id, with its check settings and current state. API: GET /user/api/v1/monitors/{id}.
DiscoveredGet the availability figures (uptime and related metrics) of one monitor for a period. API: GET /user/api/v1/monitors/{id}/availability.
DiscoveredGet one status page by id, with its settings and linked monitors. API: GET /user/api/v1/status-pages/{id}.
DiscoveredList incidents, newest first, optionally for one status page or changed after a time. Use it to review recent or ongoing outages. API: GET /user/api/v1/incidents.
DiscoveredList scheduled and past maintenance windows, optionally for one status page or created after a time. API: GET /user/api/v1/maintenances.
DiscoveredList the live metrics shown on one status page. API: GET /user/api/v1/metrics?status_page_id=.
DiscoveredList the uptime monitors in the account (site, API and DNS checks) with their current state. API: GET /user/api/v1/monitors.
DiscoveredList the status pages in the account, with their names, slugs and settings. Good first call to find a status_page_id. API: GET /user/api/v1/status-pages.
DiscoveredChange the title, message, times or affected items of a maintenance window. Send only the fields to change. API: PATCH /user/api/v1/maintenances/{id}.
DiscoveredRecent measurements
| Checked | Result | Response | Tools |
|---|---|---|---|
| Connected | 63 ms | 14 |