MCP server health, State of MCP census
Resume Optimizer
io.github.vpatser1/resume-optimizer
Resume analysis, ATS compatibility checks, bullet improvements, job-tailored optimization
Checks
The exact rows akashi check io.github.vpatser1/resume-optimizer prints, from the 2026-09-09 census.
| Check | Status | Detail |
|---|---|---|
| registry status | pass | active |
| server.json valid | pass | validates against its declared JSON Schema |
| repo reachable | skip | no repository declared |
| package npm | pass | published (1.1.4) |
| at least one live entrypoint | pass | 1 alive |
Spec 2026-07-28 readiness
No runtime readiness verdict: this server has no keylessly reachable conformant MCP endpoint (package-only, auth-gated, or down at census time), so its behavior against the 2026-07-28 revision cannot be measured without credentials. Absence of evidence is recorded as absence, never guessed. Ecosystem numbers: the readiness report.
Evidence
Repository
No repository declared.
Packages
- npm resume-optimizer · published(1.1.4)
Remote endpoints
No remote endpoint declared.
server.json
validagainst its declared schema
One of 29522 servers in the 2026-09-09 State of MCP census: 23538 healthy (79.7%), 4664 degraded (15.8%), 1162 dead (3.9%), 158 unknown (0.5%).
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.vpatser1/resume-optimizerInstall 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.vpatser1/resume-optimizer --badge.
Open data, CC BY 4.0. How this census works - denominator, tiers, and what each check does.