Connect MCP Liveness and your agent gets 3 tools, among them mcp_liveness_check, mcp_liveness_drift, mcp_liveness_explain_outcomes. It answers at https://agentwares-mcp-liveness.vercel.app/mcp over streamable HTTP, and it listed its tools to an anonymous client, so no sign-in was needed for that. Our probes reached it 6 of 6 times since 12 September 2026; the last check, on 24 October 2026, succeeded.
Whether a registry MCP server works for a stock client, and what changed in its tools. Free, no key.
Description as the publisher wrote it.
| Tool | What it does |
|---|---|
mcp_liveness_check | Given a server's exact name in the official MCP registry, make one `initialize` call to the endpoint its listing names and report what a client with no credential gets. Outcomes: `usable` (it connected and negotiated a protocol version), `n Inputs: name, skipCredentialCheck |
mcp_liveness_drift | Given a server's exact name in the official MCP registry, report which of its tools were added, removed, or had their description, input schema or output schema change between the month you name and the latest monthly snapshot. Call this wh Inputs: name, since |
mcp_liveness_explain_outcomes | Return the six outcomes this server can report, what each means for an agent choosing a server from the registry, and what to do next for each. Makes no request and costs nothing; call it once to interpret mcp_liveness_check results. |
Every block below points at https://agentwares-mcp-liveness.vercel.app/mcp. Pick your client and copy.
claude mcp add --transport http mcp-liveness https://agentwares-mcp-liveness.vercel.app/mcp
{
"mcpServers": {
"mcp-liveness": {
"command": "npx",
"args": ["-y", "mcp-remote", "https://agentwares-mcp-liveness.vercel.app/mcp"]
}
}
}{
"mcpServers": {
"mcp-liveness": {
"url": "https://agentwares-mcp-liveness.vercel.app/mcp"
}
}
}{
"servers": {
"mcp-liveness": {
"type": "http",
"url": "https://agentwares-mcp-liveness.vercel.app/mcp"
}
}
}{
"context_servers": {
"mcp-liveness": {
"url": "https://agentwares-mcp-liveness.vercel.app/mcp"
}
}
}{
"mcpServers": {
"mcp-liveness": {
"serverUrl": "https://agentwares-mcp-liveness.vercel.app/mcp"
}
}
}{
"mcpServers": {
"mcp-liveness": {
"url": "https://agentwares-mcp-liveness.vercel.app/mcp"
}
}
}name: MCP Liveness
version: 0.0.1
schema: v1
mcpServers:
- name: MCP Liveness
type: streamable-http
url: https://agentwares-mcp-liveness.vercel.app/mcp{
"mcpServers": {
"mcp-liveness": {
"httpUrl": "https://agentwares-mcp-liveness.vercel.app/mcp"
}
}
}{
"mcpServers": {
"mcp-liveness": {
"type": "http",
"url": "https://agentwares-mcp-liveness.vercel.app/mcp"
}
}
}{
"mcpServers": {
"mcp-liveness": {
"url": "https://agentwares-mcp-liveness.vercel.app/mcp"
}
}
}goose://extension?url=https%3A%2F%2Fagentwares-mcp-liveness.vercel.app%2Fmcp&type=streamable_http&id=mcp-liveness&name=MCP%20Liveness
It answered our last check on 24 October 2026 in 176 ms. Over 6 checks since 12 September 2026 it answered 6. Status here comes from Neuronto's own probes, not from the publisher.
3, as returned by the server's own tools/list on 23 September 2026: mcp_liveness_check, mcp_liveness_drift, mcp_liveness_explain_outcomes.
It answered our last check on 24 October 2026 in 176 ms. Over 6 checks since 12 September 2026 it answered 6.
Put the server under mcpServers in ~/.cursor/mcp.json with the URL https://agentwares-mcp-liveness.vercel.app/mcp. The exact JSON is above, with the same setup for Claude Code, Claude Desktop, VS Code, Windsurf, Zed, Gemini CLI and the rest.
It listed its tools to an anonymous client, so reading the tool list needs no key. Individual tools can still ask for credentials in their own inputs.
Publisher: io.github.agentwares. Endpoint host: agentwares-mcp-liveness.vercel.app. ARD identifier: urn:air:io.github.agentwares:mcp:mcp-liveness.
First indexed 12 September 2026. The tools are exactly what the server returned; nothing on this page
is inferred from its name. Ranking in Neuronto search is never for sale.