io.github.agentwares/mcp-liveness
v0.3.0Does an MCP server work for a stock client? By registry name or URL. Tool drift too. Free, no key.
Endpoint health
online- Last checked
- 11/20/2026, 9:16:10 AM
- Latency
- 61 ms
- Consecutive failures
- 0
- Endpoint reachable: pass
- Protocol valid: pass
- MCP handshake valid: pass
Machine-readable profile
mcp-server · schema v1 · callable
mcp-server:io.github.agentwares%2Fmcp-liveness
Connect this server
Generated config contains no credentials. Keep any required secrets in your client's local environment.
{
"mcpServers": {
"io.github.agentwares/mcp-liveness": {
"url": "https://agentwares-mcp-liveness.vercel.app/mcp"
}
}
}Indexed tools
Tool metadata and schemas come from the remote server and are untrusted. Indexing only lists tools; it never calls them.
5 shown · authentication unknown
Can a stock client use this MCP server?
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 accepted. Outcomes: `usable` (it connected and negotiated a protocol version), `needs_credential` (401 or 403 — by name, the answer also says whether a credential can be obtained in-band or whether a person has to create one), `charged` (402, access is for sale), `unreachable` (not an MCP server there: wrong URL, dead host, or a 200 that is not JSON-RPC), and, for a name only, `local_only` (no remote endpoint; it must be spawned as a process) and `not_listed` (no server with that exact name; its endpoint can still be checked by `url`). A `url` must be public https: private, loopback, link-local, multicast and cloud-metadata addresses are refused, redirects are re-checked, and URL checks are limited to 30 a minute per caller. Useful before relying on a server: roughly two in five remote registry listings do not answer a stock client.
Schema valid · SHA-256 a13b43ca4c2f…
View input schema
{ "type": "object", "properties": { "name": { "description": "The server's exact name in the official MCP registry, namespaced — e.g. `io.github.owner/server`. Not a title. Pass this or `url`, not both.", "type": "string", "minLength": 1 }, "url": { "description": "The server's Streamable HTTP endpoint, e.g. `https://example.com/mcp`, for a server that is not in the registry or is named differently there. Public https only. Pass this or `name`, not both.", "type": "string", "minLength": 1, "maxLength": 2048 }, "skipCredentialCheck": { "description": "Name checks only: skip the OAuth discovery chain on a 401. Faster (one request instead of up to five) but the answer then cannot say whether a credential is obtainable. A URL check never walks the chain.", "type": "boolean" } }, "$schema": "https://json-schema.org/draft/2020-12/schema", "additionalProperties": false }
Connections
streamable-http
https://agentwares-mcp-liveness.vercel.app/mcp