MCP server health, State of MCP census
Injection Detector
io.github.viridis-security/injection-detector
Formally-verified injection/exfiltration detector for AI agents (MCP-02).
Checks
The exact rows akashi check io.github.viridis-security/injection-detector 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 32d ago |
| remote reachable | pass | HTTP 200 via initialize |
| MCP conformance | pass | initialize handshake ok |
| tools/list | pass | 1 tool: detect_injection |
| at least one live entrypoint | pass | 2 alive |
| license present | pass | Apache-2.0 |
Evidence
Packages
No packages declared.
Remote endpoints
- https://mcp.viridis-security.com/mcp
streamable-http · reachable· HTTP 200· initialize_ok
1 tools: detect_injection
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.viridis-security/injection-detectorInstall 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.viridis-security/injection-detector --badge.
Open data, CC BY 4.0. How this census works - denominator, tiers, and what each check does.