MCP server health, State of MCP census
Stacktree
ee.stacktr/publish
Publish HTML to private, unguessable, replace-in-place URLs from any MCP-compatible AI agent.
Checks
The exact rows akashi check ee.stacktr/publish 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 | pass | exists |
| repo freshness | pass | pushed 48d ago |
| package npm | pass | published (0.4.1) |
| remote reachable | pass | HTTP 401 via initialize |
| MCP conformance | warn | auth-gated (HTTP 401): alive, not verifiable keyless |
| at least one live entrypoint | pass | 3 alive |
| license present | pass | MIT |
Evidence
Packages
- npm stacktree-mcp · published(0.4.1)
Remote endpoints
- https://api.stacktr.ee/mcp
streamable-http · reachable· HTTP 401· auth_gated
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 ee.stacktr/publishInstall 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 ee.stacktr/publish --badge.
Open data, CC BY 4.0. How this census works - denominator, tiers, and what each check does.