MCP server health, State of MCP census

Server

com.zype.mcp/server

Manage videos, playlists, analytics, and monetization for OTT streaming services.

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

repo_404

Checks

The exact rows akashi check com.zype.mcp/server 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 npm	pass	published (0.5.8)
remote reachable	pass	HTTP 401 via initialize
MCP conformance	warn	auth-gated (HTTP 401): alive, not verifiable keyless
at least one live entrypoint	pass	2 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

github · missing· HTTP 404

https://github.com/zype/zype-mcp

Packages

npm @zype-com/mcp · published(0.5.8)

Remote endpoints

https://mcp.zype.com/mcp
streamable-http · reachable· HTTP 401· auth_gated

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 com.zype.mcp/server

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 com.zype.mcp/server --badge.

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