ZBS Index What actually exists in applied AI, with the source next to it

mcp server

MCP Registry Validator — Check Endpoints Actually Resolve

Check an MCP endpoint resolves: liveness, live tool list, schema drift. Free.

Description as published by the maintainer. Source

  • version 0.2.1
  • active

active — Registry entry last updated 2026-08-01.

What this server can do

4 functions, named and described by the server itself. Parameter names are shown because they say more about what a function does than its name usually does.

check_mcp_endpoint(url, include_tools)
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 server. Required: url.
check_schema_drift(url)
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 worth checking. Required: url.
get_known_tools(url)
The tool list last observed at an MCP endpoint, with the timestamp of the most recent schema change. Reads stored history; does not probe. Required: url.
get_uptime(url, days)
Uptime history for an MCP endpoint over the last N days (max 30), with incident windows. Reads stored history; does not probe. Required: url.

Last successful function declaration observed on . Source: https://mcp-uptime.theopslog.workers.dev/mcp. We list what the server declared; we do not call any of these functions.

Endpoint status observed on . Source: https://mcp-uptime.theopslog.workers.dev/mcp.

Signals

These are separate measurements of different things. They are deliberately not combined into one score, because a popularity number that mixes website traffic with saves and stars cannot be checked or acted on.

Signal Value What it measures Window Observed Source
Latest published version 0.2.1 Latest version string the maintainer published to the registry. as of fetch Model Context Protocol
Registry record last updated 2026-08-01 When the registry record was last updated by its maintainer. point in time Model Context Protocol
First listed in the MCP Registry 2026-08-01 Date this server was first published to the official MCP Registry. Not a usage or quality measure. point in time Model Context Protocol
mcp tools declared 4 tools Number of functions the server itself declared when asked to list them. This is what the server offers an agent, not a measure of how well any of them work. as of probe mcp-uptime.theopslog.workers.dev
mcp endpoint status ok The server listed 4 functions when asked. as of probe mcp-uptime.theopslog.workers.dev

Where to get it

This record as data

Every field on this page, with its source and observation date, is in the catalog JSON. Fetch the whole kind at once instead of parsing this HTML.

GET /api/v1/entries/mcp_server.json

Sources

  1. Tools declared by the MCP server at https://mcp-uptime.theopslog.workers.dev/mcp — mcp-uptime.theopslog.workers.dev, observed , trust tier 1.
  2. Official MCP Registry — Model Context Protocol, observed , trust tier 1.