MCP server health, State of MCP census
Husk
io.github.husk-security/husk
Local-first defensive scanner for vulnerable dependencies, leaked secrets, and risky agent configs
Checks
The exact rows akashi check io.github.husk-security/husk 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 1d ago |
| package npm | pass | published (0.1.2) |
| package cargo | skip | husk-sec not keyless-probeable |
| at least one live entrypoint | pass | 2 alive |
| license present | pass | MIT |
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
Packages
- npm husk-sec · published(0.1.2)
- cargo husk-sec · unprobed
Remote endpoints
No remote endpoint declared.
server.json
validagainst its declared schema
One of 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. Run the same check locally, any time, with no key:
$ akashi check io.github.husk-security/huskInstall 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?
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.husk-security/husk --badge.
Open data, CC BY 4.0. How this census works - denominator, tiers, and what each check does.