MCP server health, State of MCP census
Uptimebolt Mcp Server
io.github.clm-cloud-solutions/uptimebolt-mcp-server
AI-powered infrastructure monitoring — health, incidents, predictions, RCA, deploy safety
Checks
The exact rows akashi check io.github.clm-cloud-solutions/uptimebolt-mcp-server prints, from the 2026-07-02 census.
| Check | Status | Detail |
|---|---|---|
| registry status | pass | active |
| server.json valid | pass | validates against its declared JSON Schema |
| repo reachable | pass | exists |
| repo freshness | warn | no push in 118d |
| package npm | pass | published (1.0.12) |
| at least one live entrypoint | pass | 2 alive |
| license present | pass | MIT |
Evidence
Packages
- npm @uptimebolt/mcp-server · published(1.0.12)
Remote endpoints
No remote endpoint declared.
server.json
validagainst its declared schema
One of 14559 servers in the 2026-07-02 State of MCP census: 11582 healthy (79.6%), 2212 degraded (15.2%), 596 dead (4.1%), 169 unknown (1.2%).
Verify it yourself
This page is a static read of one dated probe. Run the same check locally, any time, with no key:
$ akashi check io.github.clm-cloud-solutions/uptimebolt-mcp-serverInstall Akashi - single Go binary, zero keys, MIT licensed.
Is this your server?
Claiming a server (an auto-refreshing badge and a verified publisher profile) is coming soon. Until then, embed the verified-on-date badge yourself with akashi check io.github.clm-cloud-solutions/uptimebolt-mcp-server --badge.
Open data, CC BY 4.0. How this census works - denominator, tiers, and what each check does.