mcp-registry/dev.uptimepage/uptimepage · v1.4.0
As of 2026-10-17 19:31 UTC, the Uptimepage MCP server is up with a Glimind reliability score of 90/100 (grade A). Over the last 30 days it answered 99.9% of Glimind's liveness checks. It had 6 outages in 90 days, with a median recovery of 6 minutes.
Monitor uptime and incidents, run checks, and publish status updates from your Uptimepage org.
Claude Code
claude mcp add --transport http uptimepage-mcp-server https://mcp.uptimepage.dev/mcp
Claude Desktop · Windsurf · Cline (mcpServers JSON)
{
"mcpServers": {
"uptimepage-mcp-server": {
"type": "http",
"url": "https://mcp.uptimepage.dev/mcp"
}
}
}
Third-party server, listed as discovered. Review its source before installing.
2 tool definition(s) exceed ~1,200 tokens each (largest: create_monitors, ~3,221).
Move long reference material out of descriptions (link a doc or expose a resource), drop repeated examples, and collapse large enums. Trimming these to ~600 tokens saves ~5,154 tokens every session.
6 parameter(s) across 3 tool(s) have no description.
Add a "description" to each parameter with its format and an example ("ISO 8601 date, e.g. 2026-10-17"). This is the commonest cause of wrong arguments on the first call.
Loading this server's tool list costs an agent ~17,047 tokens before any work — more than 95% of MCP servers.
Split rarely-used tools into a separate server or a toolset the client can enable, or expose one "search tools" entry point. Many agents load every connected server's tools into every request.
Handshake + tools/list takes ~2,107 ms.
Serve tools/list from memory, keep the process warm, and host close to your users. Every new agent session pays this before its first call.
In the last 30 days: 0 tool(s) removed and 16 schema change(s).
Add new tools or optional parameters instead of renaming or removing; deprecate first (say so in the description) and remove later. Agents cache tool contracts.
Get an email or webhook when this server's readiness drops by 10+ points, tool-poisoning text appears, or a tool breaks:
curl -X POST https://glimind.com/v1/subscriptions -H 'content-type: application/json' -d '{"tools":["mcp-registry/dev.uptimepage/uptimepage"],"email":"[email protected]"}'Agents: watch_tool({"toolId": "mcp-registry/dev.uptimepage/uptimepage"}) over MCP.
create_monitors ~3,221 tokenscreate_monitor ~3,133 tokensupdate_monitor ~1,105 tokensupdate_status_page ~894 tokenscreate_status_page ~885 tokensStatic checks of the advertised tools/list (schema, descriptions, annotations, tool-poisoning patterns, names, size) plus observed protocol, uptime, latency and contract changes. Read-only: no tool is ever called. Weights: schema 15, docs 20, safety 15, efficiency 15, compatibility 15, protocol 5, reliability 10, stability 5. Token counts are estimates (~3.6 characters per token).
Operator? Fix these, then re-check live. Embed the readiness badge:
[](https://glimind.com/server/mcp-registry%2Fdev.uptimepage%2Fuptimepage?ref=badge)
<a href="https://glimind.com/server/mcp-registry%2Fdev.uptimepage%2Fuptimepage?ref=badge"><img src="https://glimind.com/v1/readiness/badge/mcp-registry%2Fdev.uptimepage%2Fuptimepage.svg" alt="MCP agent-readiness"></a>
.. image:: https://glimind.com/v1/readiness/badge/mcp-registry%2Fdev.uptimepage%2Fuptimepage.svg :target: https://glimind.com/server/mcp-registry%2Fdev.uptimepage%2Fuptimepage?ref=badge :alt: MCP agent-readiness
Glimind records every version of this server's tool definitions in a signed, append-only transparency log. Current manifest sha256:2ee15b570e2dae02…, first seen 2026-10-17, included at leaf 14630 of 18,259. Version history · verify what your client received.
Compare: most reliable incident servers · most reliable status servers · most reliable devops servers · most reliable monitor servers · most reliable monitoring servers
Glimind tells agents whether a server is up right now and how to call it, then fails over to a live alternative when it isn't.
Claude Code
claude mcp add --transport http glimind https://glimind.com/mcp
Claude Desktop · Windsurf · Cline (mcpServers JSON)
{
"mcpServers": {
"glimind": {
"type": "http",
"url": "https://glimind.com/mcp"
}
}
}
As of 2026-10-17 19:31 UTC, the Uptimepage MCP server is up with a Glimind reliability score of 90/100 (grade A). Over the last 30 days it answered 99.9% of Glimind's liveness checks. It had 6 outages in 90 days, with a median recovery of 6 minutes.
Uptimepage MCP server advertises 39 tools, including acknowledge_incident, add_status_page_components, cancel_maintenance, create_maintenance, create_monitor.
Point your MCP client at this streamable-http endpoint: https://mcp.uptimepage.dev/mcp
Glimind scanned all 39 tool definitions for tool-poisoning patterns — hidden or invisible characters, instructions that override the model, concealment from the user, requests to read credential or MCP config files, conversation exfiltration and cross-tool shadowing — and found none. This checks what the server tells the model, not what its code does; review the source before granting access to sensitive data.
Status page: 90-day uptime, every outage and how long it lasted.
Claim this listing to get the Verified operator marker, a remediation checklist and owner analytics, or embed the live badge from any of the tool pages above. Maintainers: alerts, deploy attestation and monthly reports.
Status is an automated estimate from Glimind's liveness checks (handshake and tool listing only; no tool is ever called) and may lag or differ from your network. Glimind is not affiliated with this server or its operator. Operator? Request a correction or opt out at https://glimind.com/opt-out.