MCP server health, State of MCP census
Mcp Server
io.github.sudzikcoin/mcp-server
Pay-per-call x402 tools: crypto market pulse, wallet reputation, token check, endpoint search.
- server_json_invalid
Checks
The exact rows akashi check io.github.sudzikcoin/mcp-server prints, from the 2026-07-02 census.
| Check | Status | Detail |
|---|---|---|
| registry status | pass | active |
| server.json valid | fail | jsonschema validation failed with 'https://static.modelcontextprotocol.io/schemas/2025-07-09/server.schema.json#' |
| repo reachable | warn | probe error: http2: response body closed |
| package npm | pass | published (0.2.2) |
| at least one live entrypoint | pass | 1 alive |
Evidence
Packages
- npm @suverselabs/mcp-server · published(0.2.2)
Remote endpoints
No remote endpoint declared.
server.json
invalidagainst its declared schema
- jsonschema validation failed with 'https://static.modelcontextprotocol.io/schemas/2025-07-09/server.schema.json#'
- - at '': allOf failed
- - at '/packages/0': validation failed
- - at '/packages/0': missing property 'registry_type'
- - at '/packages/0': additional properties 'registryType', 'registryBaseUrl' not allowed
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.sudzikcoin/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.sudzikcoin/mcp-server --badge.
Open data, CC BY 4.0. How this census works - denominator, tiers, and what each check does.