All servers · Markets & trading
io.github.agentwares/mcp-liveness
io.github.agentwares/mcp-liveness · v0.3.0
Measured by MCP Station
| Last check | Reachable |
|---|---|
| Checked at | — |
| Check success 7 / 30 days | — |
| First-try success 30 days | — |
| Median response | — |
| Lookups 30 days | — |
| Authentication | No auth |
| MCP version | 2025-06-18 |
| Rank score | — |
| Declared risk | Read-only (all tools declare readOnlyHint) |
| Capabilities declared | logging, tools |
| Tool definitions | 5 tools · with description 100% · input schema is an object 100% · read/destructive hints 100% |
Description written by the publisher, not verified
Does an MCP server work for a stock client? By registry name or URL. Tool drift too. Free, no key.
Connect
streamable-http · https://agentwares-mcp-liveness.vercel.app/mcp
claude mcp add --transport http mcp-liveness https://agentwares-mcp-liveness.vercel.app/mcp{
"mcpServers": {
"mcp-liveness": {
"url": "https://agentwares-mcp-liveness.vercel.app/mcp"
}
}
}Tools as reported by the server
mcp_liveness_checkMakes 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 endpointmcp_liveness_explain_outcomesReturns 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 changmcp_liveness_driftGiven 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 prommcp_liveness_check_authWalks 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. Stmcp_liveness_check_appsChecks 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,
Repository · Website · JSON · Text for agents · Registry updated 2026-10-06