MCP server health, State of MCP census

Releases

sh.releases/mcp

An agent-friendly API for product changelogs. A unified registry via CLI, API, or MCP.

degraded checked 2026-07-02 · 6/7 checks passed · keyless

repo_404

Checks

The exact rows akashi check sh.releases/mcp 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	fail	404 (repository gone)
remote reachable	pass	HTTP 200 via initialize
MCP conformance	pass	initialize handshake ok
tools/list	pass	16 tools: search, get_latest_releases, list_catalog, get_catalog_entry, list_organizations, get_organization, lookup_domain, list_collections, ...
at least one live entrypoint	pass	1 alive

Evidence

Repository

github · missing· HTTP 404

https://github.com/buildinternet/releases

Packages

No packages declared.

Remote endpoints

https://mcp.releases.sh/mcp
streamable-http · reachable· HTTP 200· initialize_ok

16 tools: search, get_latest_releases, list_catalog, get_catalog_entry, list_organizations, get_organization, lookup_domain, list_collections, ...

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 sh.releases/mcp

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 sh.releases/mcp --badge.

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