MCP server health, State of MCP census
0nMCP — Universal AI API Orchestrator
io.github.0nork/0nMCP
Universal AI API Orchestrator — 1,554 tools, 96 services. One install.
- repo_404
Checks
The exact rows akashi check io.github.0nork/0nMCP 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 (4.11.0) |
| remote reachable | pass | HTTP 200 via initialize |
| MCP conformance | pass | initialize handshake ok |
| tools/list | pass | 17 tools: search_contacts, create_contact, get_contact, update_contact, add_contact_tags, add_contact_note, search_conversations, send_message, ... |
| at least one live entrypoint | pass | 2 alive |
Evidence
Packages
- npm 0nmcp · published(4.11.0)
Remote endpoints
- https://0nmcp.com/api/mcp
streamable-http · reachable· HTTP 200· initialize_ok
17 tools: search_contacts, create_contact, get_contact, update_contact, add_contact_tags, add_contact_note, search_conversations, send_message, ...
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.0nork/0nMCPInstall 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.0nork/0nMCP --badge.
Open data, CC BY 4.0. How this census works - denominator, tiers, and what each check does.