Serverdex live check · status history
DPO2U compliance MCP server status
● Answering599 ms handshakechecked Nov 22, 2026, 13:09 UTC
No. At the last Serverdex check (Nov 22, 2026, 13:09 UTC) the DPO2U compliance endpoint answered the MCP initialize handshake in 599 ms and listed 83 tools.
Uptime, 30 days
100%
5 days on record
Uptime, 90 days
100%
5 days on record
Answering since
Nov 18, 2026
without a failed check
Tools now
83
≈ 23k tokens of definitions
Status history
1 change on record · only changes are stored, not every check- First checked: answering
Questions
- Is DPO2U compliance down right now?
- No. At the last Serverdex check (Nov 22, 2026, 13:09 UTC) the DPO2U compliance endpoint answered the MCP initialize handshake in 599 ms and listed 83 tools.
- How is DPO2U compliance 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 DPO2U compliance?
- 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 DPO2U compliance listing · test any endpoint yourself with the MCP server health check · what changed across the registry today: MCP server changelog.