MCP server health, State of MCP census
Kamy
dev.kamy/kamy
Document API for AI-native software: render PDFs, e-sign, PAdES-seal, and verify.
Checks
The exact rows akashi check dev.kamy/kamy 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 49d ago |
| remote reachable | pass | HTTP 200 via initialize |
| MCP conformance | pass | initialize handshake ok |
| tools/list | pass | 12 tools: list_templates, render_pdf, extract_document, ask_kamy, install_sdk, generate_integration_code, create_signature_request, list_signature_requests, ... |
| at least one live entrypoint | pass | 2 alive |
| license present | pass | MIT |
Evidence
Packages
No packages declared.
Remote endpoints
- https://mcp.kamy.dev/mcp
streamable-http · reachable· HTTP 200· initialize_ok
12 tools: list_templates, render_pdf, extract_document, ask_kamy, install_sdk, generate_integration_code, create_signature_request, list_signature_requests, ...
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 dev.kamy/kamyInstall 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 dev.kamy/kamy --badge.
Open data, CC BY 4.0. How this census works - denominator, tiers, and what each check does.