MCP Registry Validator — Check Endpoints Actually Resolve

Ingested from the official MCP Registry

FastDrop pulled this entry from the official MCP Registry as io.github.operatorsheets/mcp-uptime and probed the endpoint. The maker did not submit it, so the outbound link is not endorsed and the description is not theirs.

If this is your server, claim the listing to edit it and take ownership. The registry index lists everything else still awaiting a probe.

Tools this endpoint exposes

Read directly from the endpoint on 30 Sept 2026. Not supplied by the maker.

• check_mcp_endpoint

  Probe an MCP endpoint right now: is it alive, which transport it speaks, how many tools it exposes, and whether its tool schema changed since the last check. Use before depending on a third-party MCP

• get_uptime

  Uptime history for an MCP endpoint over the last N days (max 30), with incident windows. Reads stored history; does not probe.

• get_known_tools

  The tool list last observed at an MCP endpoint, with the timestamp of the most recent schema change. Reads stored history; does not probe.

• check_schema_drift

  Probe an MCP endpoint and diff its tool schema against the last stored snapshot: tools added, removed, or whose description/inputSchema changed. Schema drift fails quietly mid-run, which is why it is

Is this tool yours?

Claim this listing and we’ll verify ownership before handing it over.