mcp-liveness MCP Server
Checks whether an MCP server actually answers for a stock client, with a verdict and a one-line fix.
mcp-liveness is a Developer Tools MCP (Model Context Protocol) server: Checks whether an MCP server actually answers for a stock client, with a verdict and a one-line fix. It is listed as Proprietary and available as a hosted endpoint, so it works with no local install. It exposes 5 tools including mcp_liveness_check, mcp_liveness_explain_outcomes, mcp_liveness_drift, mcp_liveness_check_auth. Listed on MCP Collection since October 2026.
About mcp-liveness
Checks whether an MCP server actually answers for a stock client. Verdicts: usable, needs_credential, charged, unreachable, local_only, or not_listed, each with a one-line fix. Input: an MCP server URL. Use it before adding a server to a client.
mcp-liveness tools (5)
Read from the live server on Oct 30, 2026. These are the tools your AI assistant can call once connected.
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 eith
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 refer
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 se
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 is
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
How to connect mcp-liveness to Claude, Cursor or VS Code
mcp-liveness runs as a hosted remote MCP server at https://agentwares-mcp-liveness.vercel.app/mcp. Add that URL to your MCP client's config (Claude Code, Cursor, Windsurf or VS Code) and the tools appear immediately, no install required.
{
"mcpServers": {
"mcp-liveness": {
"url": "https://agentwares-mcp-liveness.vercel.app/mcp"
}
}
}Claude Code: claude mcp add --transport http mcp-liveness https://agentwares-mcp-liveness.vercel.app/mcp. Servers that require OAuth or an API key will prompt on first use.
mcp-liveness FAQ
What is mcp-liveness?
mcp-liveness is a Model Context Protocol (MCP) server in the Developer Tools category. Checks whether an MCP server actually answers for a stock client, with a verdict and a one-line fix. MCP servers expose tools that AI assistants like Claude can call during a conversation.
How do I use mcp-liveness with Claude or Cursor?
mcp-liveness runs as a hosted remote MCP server at https://agentwares-mcp-liveness.vercel.app/mcp. Add that URL to your MCP client's config (Claude Code, Cursor, Windsurf or VS Code) and the tools appear immediately, no install required.
Is mcp-liveness free to use?
mcp-liveness is listed as Proprietary software. Check the project homepage for pricing and terms.
What tools does mcp-liveness provide?
mcp-liveness exposes 5 MCP tools: mcp_liveness_check, mcp_liveness_explain_outcomes, mcp_liveness_drift, mcp_liveness_check_auth, mcp_liveness_check_apps. This list is read from the live server (last verified Oct 30, 2026).
Is the mcp-liveness MCP server online?
Yes. MCP Collection checks the endpoint every day; it last answered on Oct 30, 2026.