MCP server health, State of MCP census
Linkup
so.linkup.mcp/linkup-mcp-server
Search the web in real time to get trustworthy, source-backed answers.
- remote_nonconformant
Checks
The exact rows akashi check so.linkup.mcp/linkup-mcp-server 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 | skip | no repository declared |
| remote reachable | pass | HTTP 200 via initialize |
| MCP conformance | fail | returned HTTP 200 but is not an MCP server |
| remote reachable | pass | HTTP 200 via initialize |
| MCP conformance | fail | returned HTTP 200 but is not an MCP server |
| at least one live entrypoint | pass | 2 alive |
Evidence
Repository
No repository declared.
Packages
No packages declared.
Remote endpoints
- https://mcp.linkup.so
streamable-http · reachable· HTTP 200· reachable_nonconformant
- https://mcp.linkup.so
sse · reachable· HTTP 200· reachable_nonconformant
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 so.linkup.mcp/linkup-mcp-serverInstall 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 so.linkup.mcp/linkup-mcp-server --badge.
Open data, CC BY 4.0. How this census works - denominator, tiers, and what each check does.