Does an MCP server work for a stock client? By registry name or URL. Tool drift too. Free, no key.
| Endpoint | https://agentwares-mcp-liveness.vercel.app/mcp (streamable-http) |
|---|---|
| Registry version | 0.3.0 |
| Now | 5 tools · grade D (57) · pin ts_82b8f2d07492d70f0d9dbf6d507ac067 · protocol 2025-06-18 |
| First / last listed | 2026-11-04 04:18 UTC / 2026-11-04 04:18 UTC |
| Grade over time | 2026-11-04: D (57), 5 tools |
Is this your server? Own a server? ToolFit hosted watch re-checks it every 24 h ($0.25 per 30 days) or 6 h ($0.60) and sends you an HMAC-signed webhook when its tools or grade change: POST https://api.youraitools.co/toolfit/v1/watch. To opt out, see About & opt-out.
Tools: mcp_liveness_check mcp_liveness_explain_outcomes mcp_liveness_drift mcp_liveness_check_auth mcp_liveness_check_apps
mcp_liveness_check | Makes one handshake with an MCP server's endpoint — `server/discover` at protocol revision
2026-07-28, then `initialize` for a server on the older revision — with no credential, and
reports what a stock client gets. The server is named either by its exact official-registry
`name`, or by its endpoint `url` when it is not in the registry or is listed under another
name; exactly one of the two is acc params: name, url, skipCredentialCheck |
mcp_liveness_explain_outcomes | Returns the six outcomes this server can report — usable, needs_credential, charged, unreachable, local_only and not_listed — what each means for an agent choosing a server from the registry, and the usual next move for each. A static reference: it makes no network request and its answer never changes between calls. params: none |
mcp_liveness_drift | Given a server's exact name in the official MCP registry, reports which of its tools were
added, removed, or had their description, input schema or output schema change between
a named month and the latest monthly snapshot.
Useful when a server that worked before behaves differently now, when a prompt or an
integration written against its tools has started failing, or before relying on a cached
t params: name*, since |
mcp_liveness_check_auth | Walks a remote MCP server's OAuth sign-in chain from outside, with no credential and no
client registration, and returns the first step that breaks, whose it is (`server`,
`identity_provider`, or `client` for a known client bug, with its issue URL), the fix, and
the spec section that requires it.
Steps, in order: one unauthenticated request (it must answer 401 with a WWW-Authenticate
challenge); params: url*, client |
mcp_liveness_check_apps | Checks a remote MCP server's MCP Apps UI (SEP-1865 `ui://` resources) from outside, with no
credential and without calling any tool, and returns the first step that stops the view
rendering, whose it is (`server`, or `host` for a known host bug with its issue URL), the
fix, and the source (the spec, or the host's published page, with the date read).
It opens the server as an MCP Apps host would, params: url*, host |
Entries describe changes in tool definitions. They are not statements about a server, its quality or its author. The grade measures how the tool definitions fit model providers (token cost, schema compatibility, confusable names) as scored by the ToolFit engine at the time of the listing. JSON: append .json. Opt-out: how or hello@youraitools.co.