MCP server health, State of MCP census
operant-mcp
io.github.saagpatel/operant-mcp
Read-only MCP server for the OPERANT AI operating-agent calibration benchmark.
Checks
The exact rows akashi check io.github.saagpatel/operant-mcp 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 | warn | probe error: http2: response body closed |
| package npm | pass | published (0.1.0) |
| remote reachable | pass | HTTP 200 via initialize |
| MCP conformance | pass | initialize handshake ok |
| tools/list | pass | 5 tools: get_results, compare_models, get_methodology, list_cases, get_case |
| at least one live entrypoint | pass | 2 alive |
Evidence
Packages
- npm saagar-operant-mcp · published(0.1.0)
Remote endpoints
- https://operant-mcp.saagar210.workers.dev/mcp
streamable-http · reachable· HTTP 200· initialize_ok
5 tools: get_results, compare_models, get_methodology, list_cases, get_case
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.saagpatel/operant-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.saagpatel/operant-mcp --badge.
Open data, CC BY 4.0. How this census works - denominator, tiers, and what each check does.