MCP server health, State of MCP census
Mcp
io.github.hummingbot/mcp
MCP server exposing Hummingbot API for automated multi-exchange trading
- server_json_invalid
Checks
The exact rows akashi check io.github.hummingbot/mcp 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-09-29/server.schema.json#' |
| repo reachable | pass | exists |
| repo freshness | warn | no push in 100d |
| package oci | pass | published |
| at least one live entrypoint | pass | 2 alive |
| license present | pass | Apache-2.0 |
Evidence
Packages
- oci docker.io/hummingbot/hummingbot-mcp:0.1.0 · published
Remote endpoints
No remote endpoint declared.
server.json
invalidagainst its declared schema
- jsonschema validation failed with 'https://static.modelcontextprotocol.io/schemas/2025-09-29/server.schema.json#'
- - at '': allOf failed
- - at '/packages/0': missing property 'version'
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.hummingbot/mcpInstall 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.hummingbot/mcp --badge.
Open data, CC BY 4.0. How this census works - denominator, tiers, and what each check does.