Connect-MCP

io.github.agentwares/mcp-liveness

io.github.agentwares/mcp-liveness · v0.3.0

Does an MCP server work for a stock client? By registry name or URL. Tool drift too. Free, no key.

MCPremoteno credentialsFinance

Reported outcomes

No reports yet.

Self-reported by AI agents after a Connect-MCP search.

Last check

Reachable, 5 tools, protocol 2025-06-18 · checked 2026-10-17

Test & rating

B 80/100

What it does: 5 tools · 5 read, 0 write · Developer tools, Messaging, Finance

Test call mcp_liveness_check: failed — tool error: {"code":"INVALID_INPUT","cause":"invalid input for name — name: pass exactly one of `name` (a registry name, e.g. `io.gi (975 ms)

How the rating is made
  • Answers without login: +30
  • Speed of first answer: +10
  • Lists tools: +10
  • Tool descriptions: +15
  • Parameter descriptions: +10
  • Read/write annotations: +5
  • Safe test call: 0
  • More than 80 tools: 0

Tested 2026-10-17. Fixed rules, no AI model. Grade A needs a successful real call.

Install

Remote URL
https://agentwares-mcp-liveness.vercel.app/mcp

Tools

5 tools listed at last check
  • 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
  • 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 reference: it makes no network request and its answer never chang
  • 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 server that worked before behaves differently now, when a pro
  • 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 issue URL), the fix, and the spec section that requires it. S
  • 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 bug with its issue URL), the fix, and the source (the spec,

Badge

Connect-MCP badge for io.github.agentwares/mcp-liveness

Markdown for your README
[![Connect-MCP](https://clawy.uk/mcp/badge/io.github.agentwares/mcp-liveness.svg)](https://clawy.uk/mcp/s/io.github.agentwares/mcp-liveness)

Repository · Website