MCP server health, State of MCP census
A2a Trustgate
io.github.jyswee/a2a-trustgate
A2A TrustGate: 4-gate firewall that screens every AI-agent action before it runs. 49 tools.
Checks
The exact rows akashi check io.github.jyswee/a2a-trustgate prints, from the 2026-07-22 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 5d ago |
| package npm | pass | published (1.5.10) |
| remote reachable | pass | HTTP 200 via get |
| MCP conformance | skip | not evaluated |
| at least one live entrypoint | pass | 3 alive |
| license present | warn | none detected |
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 a2a-trustgate · published(1.5.10)
Remote endpoints
- https://mcp.a2ainfrastructure.com/sse
sse · reachable· HTTP 200
server.json
validagainst its declared schema
One of 18032 servers in the 2026-07-22 State of MCP census: 14367 healthy (79.7%), 2850 degraded (15.8%), 724 dead (4.0%), 91 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.jyswee/a2a-trustgateInstall 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.jyswee/a2a-trustgate --badge.
Open data, CC BY 4.0. How this census works - denominator, tiers, and what each check does.