MCP server health, State of MCP census
PromptGuard
co.promptguard/security
Scan prompts for injection attacks, redact PII, and audit LLM SDK usage from any MCP client
- repo_404
Checks
The exact rows akashi check co.promptguard/security prints, from the 2026-08-03 census.
| Check | Status | Detail |
|---|---|---|
| registry status | pass | active |
| server.json valid | pass | validates against its declared JSON Schema |
| repo reachable | fail | 404 (repository gone) |
| package pypi | pass | published (1.0.0) |
| package npm | pass | published (1.0.0) |
| package oci | pass | published |
| at least one live entrypoint | pass | 3 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
Packages
- pypi promptguard-mcp-server · published(1.0.0)
- npm @promptguard/mcp-server · published(1.0.0)
- oci docker.io/abhijoysarkar/promptguard-mcp-server:1.0.0 · published
Remote endpoints
No remote endpoint declared.
server.json
validagainst its declared schema
One of 19804 servers in the 2026-08-03 State of MCP census: 15974 healthy (80.7%), 2792 degraded (14.1%), 851 dead (4.3%), 187 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 co.promptguard/securityInstall 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 co.promptguard/security --badge.
Open data, CC BY 4.0. How this census works - denominator, tiers, and what each check does.