Skip to content
Back to search
100
MCP live MCP 2026-07-28 streamable-http

io.github.agentwares/mcp-liveness

io.github.agentwares/mcp-liveness

Whether a registry MCP server works for a stock client, and what changed in its tools. Free, no key.

Watch this dependency Share evidence report
Uptime
100.0%
5 direct probes · 30d
Response
480ms
last probe
Tools
5
callable
Resources
0
readable
Prompts
0
available
Score: 100/100
Handshake verified by our own probe.
pass Answers the MCP handshake 50/50
The handshake and the list calls succeeded on the primary URL.
pass Lists tools, resources or prompts 30/30
5 tools, 0 resources, 0 prompts returned.
pass 3 or more catalogue items 10/10
5 items in total; 3 or more earns these points.
pass Describes itself 10/10
100 characters; more than 30 earns these points.

Tools · 5

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 sto…

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 …

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 l…

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 `cli…

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 …

How to use

Claude Desktop or claude.ai: add a custom connector (Customize → Connectors; on Team and Enterprise plans an owner adds it under Organization settings → Connectors) with this server URL: https://agentwares-mcp-liveness.vercel.app/mcp

Cursor or Cline: add to your MCP config:

{
  "mcpServers": {
    "io.github.agentwares/mcp-liveness": {
      "url": "https://agentwares-mcp-liveness.vercel.app/mcp",
      "transport": "streamable-http"
    }
  }
}