Delisted server, State of MCP census
flatten-mcp
io.github.shayaShav/flatten-mcp
Flatten a Claude Code or OpenAI Codex CLI session losslessly: digested bulk out, every word kept.
This server is no longer in the registry
It was present from the 2026-07 census, last seen in 2026-07-22, and absent when we ran the 2026-08-03 census. The registry publishes no removal date, so 2026-08-03 is when we observed the absence, not when it happened.
Everything below is the last observation, made on 2026-07-22. It is kept because a server leaving the registry is a dated fact, and it is not a claim about this server today. The page stays at this URL so a link to it never breaks.
Checks
The exact rows akashi check io.github.shayaShav/flatten-mcp prints, from the 2026-09-13 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 0d ago |
| package npm | pass | published (2.6.1) |
| remote reachable | pass | HTTP 200 via initialize |
| MCP conformance | pass | initialize handshake ok |
| tools/list | pass | 2 tools: flatten_messages, unflatten_messages |
| at least one live entrypoint | pass | 3 alive |
| license present | pass | MIT |
| spec 2026-07-28 | warn | needs-migration: no server/discover, routing headers not enforced |
Spec 2026-07-28 readiness
Verdict: needs-migration(no server/discover; routing headers not enforced). Measured against the 2026-07-28 specification (ruleset 2026-07-28-rc, compiled from the draft and re-diffed against the final text with no verdict-bearing rule changed) with read-only, keyless calls; see the ecosystem readiness report for how this server compares.
| Accepts handshake-free calls | yes |
| server/discover implemented | no |
| Session independence | yes |
| Routing headers enforced | ignored |
Advisory: no resultType on results; no cache metadata on list results; negotiates 2025-06-18.
Evidence
Packages
- npm flatten-mcp · published(2.6.1)
Remote endpoints
- https://shaya.cloud/flatten-mcp
streamable-http · reachable· HTTP 200· initialize_ok
2 tools: flatten_messages, unflatten_messages
server.json
validagainst its declared schema
Not among the 31538 servers in the 2026-09-13 State of MCP census: 25411 healthy (80.6%), 4667 degraded (14.8%), 1184 dead (3.8%), 276 unknown (0.9%).
Verify it yourself
This page is a static read of one dated probe, the last one we made. The command still runs, but the registry no longer lists this server, so expect it to resolve nothing: that failure is the finding, and it is what the record above preserves.
$ akashi check io.github.shayaShav/flatten-mcpInstall Akashi - single Go binary, zero keys, MIT licensed.
Prefer the data? This page has a machine-readable record carrying the same checks, verdict and census date, under the same methodology.
Is this your server?
If you re-publish it to the registry it will reappear in the next census and this page becomes a health report again. See every server that has left the registry.
Open data, CC BY 4.0. How this census works - denominator, tiers, and what each check does.