MCP server health, State of MCP census
Patchistry Mcp Server
io.github.patchistry/patchistry-mcp-server
DTC modular hat brand MCP server. 6 tools for AI agents: catalog, curated builds, shipping.
Checks
The exact rows akashi check io.github.patchistry/patchistry-mcp-server 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 16d ago |
| package npm | pass | published (0.3.1) |
| remote reachable | pass | HTTP 200 via initialize |
| MCP conformance | pass | initialize handshake ok |
| tools/list | pass | 6 tools: list_canvases, list_patches, get_curated_build, recommend_build, get_shipping_policy, get_contact |
| at least one live entrypoint | pass | 3 alive |
| license present | pass | MIT |
Evidence
Packages
- npm patchistry-mcp-server · published(0.3.1)
Remote endpoints
- https://patchistry-mcp-server.vercel.app/rpc
streamable-http · reachable· HTTP 200· initialize_ok
6 tools: list_canvases, list_patches, get_curated_build, recommend_build, get_shipping_policy, get_contact
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.patchistry/patchistry-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.patchistry/patchistry-mcp-server --badge.
Open data, CC BY 4.0. How this census works - denominator, tiers, and what each check does.