MCP server health, State of MCP census

Schema Validate

io.github.CedricKouma/schema-validate

MCP server (stdio): validate JSON against JSON Schema (draft-07 / 2020-12) via the AgentForge API

healthy checked 2026-08-03 · 5/7 checks passed · keyless

Checks

The exact rows akashi check io.github.CedricKouma/schema-validate prints, from the 2026-08-03 census.

CheckStatusDetail
registry statuspassactive
server.json validpassvalidates against its declared JSON Schema
repo reachableskipno repository declared
package npmpasspublished (0.1.0)
remote reachablepassHTTP 401 via initialize
MCP conformancewarnauth-gated (HTTP 401): alive, not verifiable keyless
at least one live entrypointpass2 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 agentforge-schema-validate-mcp · published(0.1.0)

Remote endpoints

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 io.github.CedricKouma/schema-validate

Install 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.CedricKouma/schema-validate --badge.

Open data, CC BY 4.0. How this census works - denominator, tiers, and what each check does.