Serverdex live check · status history

SolvingHealth federal health data MCP server status

● Answering163 ms handshakechecked Nov 22, 2026, 07:08 UTC

No. At the last Serverdex check (Nov 22, 2026, 07:08 UTC) the SolvingHealth federal health data endpoint answered the MCP initialize handshake in 163 ms and listed 12 tools.

Uptime, 30 days
100%
2 days on record
Uptime, 90 days
100%
2 days on record
Answering since
Nov 21, 2026
without a failed check
Tools now
12
≈ 1.8k tokens of definitions

Status history

1 change on record · only changes are stored, not every check
  1. First checked: answering

Questions

Is SolvingHealth federal health data down right now?
No. At the last Serverdex check (Nov 22, 2026, 07:08 UTC) the SolvingHealth federal health data endpoint answered the MCP initialize handshake in 163 ms and listed 12 tools.
How is SolvingHealth federal health data checked?
Serverdex calls the server's hosted endpoint about once a day with a plain MCP initialize followed by tools/list, with no credentials, and records only changes: a status flip or a change in the tool list. Uptime is time-weighted from those changes, so a server checked for less than a day shows no percentage.
What does "needs sign-in" mean for SolvingHealth federal health data?
The endpoint is reachable and speaks HTTP, but returns 401 or 403 until a key or OAuth sign-in is supplied. The server is up; the Serverdex check cannot read its tools without an account.

Back to the SolvingHealth federal health data listing · test any endpoint yourself with the MCP server health check · what changed across the registry today: MCP server changelog.