MCP server health, State of MCP census

Core

to.unified/core

Unified.to MCP server — one API for 500+ B2B SaaS integrations across 28+ categories

healthy checked 2026-07-22 · 4/6 checks passed · keyless

Checks

The exact rows akashi check to.unified/core 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	skip	no repository declared
remote reachable	pass	HTTP 400 via initialize
MCP conformance	warn	endpoint up (HTTP 400) but did not accept an initialize over this transport
at least one live entrypoint	pass	1 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

No packages declared.

Remote endpoints

https://mcp-api.unified.to/mcp
streamable-http · reachable· HTTP 400· unverified

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 to.unified/core

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 to.unified/core --badge.

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