MCP server health, State of MCP census
Hiveclaw
io.github.omiiyamu/hiveclaw
Connect AI assistants to HiveClaw — manage projects, talk to AI agents, and more.
- repo_404
- remote_5xx
Checks
The exact rows akashi check io.github.omiiyamu/hiveclaw 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 | fail | 404 (repository gone) |
| package npm | pass | published (0.1.1) |
| remote reachable | fail | server error (HTTP 503) |
| at least one live entrypoint | pass | 1 alive |
Evidence
Packages
- npm @hiveclaw/mcp-server · published(0.1.1)
Remote endpoints
- https://api.hiveclaw.ai/api/v1/mcp/remote
streamable-http · server_error· HTTP 503
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.omiiyamu/hiveclawInstall 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.omiiyamu/hiveclaw --badge.
Open data, CC BY 4.0. How this census works - denominator, tiers, and what each check does.