io.github.agentwares/mcp-liveness

Est-ce que io.github.agentwares/mcp-liveness est sûr ?

Au dernier audit MCP Hub, le serveur MCP « io.github.agentwares/mcp-liveness » est classé « Non encore testé ». Référencé dans l'annuaire. Seul le pentest comportemental fait foi, et il n'a pas encore été exécuté sur ce serveur. Le verdict est réévalué en continu ; consultez la fiche pour l'état à jour.

Méthode : MCP Hub analyse la description de chaque outil (couche 1) et, pour le verdict fort, exécute le serveur dans une micro-VM isolée avec leurres et réseau bloqué (couche 2). On publie des noms et des compteurs, jamais le contenu brut renvoyé par un outil.

Les 5 outils

• mcp_liveness_check≈ 600 tokens

  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.

  Paramètres, retour & exemple (3)

  Paramètres

  • url · string · optionnel
    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.
  • name · string · optionnel
    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.
  • skipCredentialCheck · boolean · optionnel
    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.

  Exemple d'appel

  {"name": "mcp_liveness_check", "arguments": {"url": "texte", "name": "texte", "skipCredentialCheck": true}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• mcp_liveness_check_apps≈ 589 tokens

  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, or the host's published page, with the date read). It opens the server as an MCP Apps host would, then reads tools/list, resources/list and resources/read: each tool's link to its view (_meta.ui.resourceUri, or ChatGPT's openai/outputTemplate alias), the view's MIME type (text/html;profile=mcp-app) and HTML, what the HTML loads against the CSP a host builds from _meta.ui.csp, whether it sends ui/initialize, ui.domain for Claude and for ChatGPT, and what OpenAI's directory review checks (explicit tool annotations, descriptions, a public https endpoint, the domain-verification file). Verdicts per host — `spec`, `claude`, `chatgpt`, `chatgpt-directory` — are judged from each host's published pages; no host is run. Use it when a user says an MCP App or ChatGPT app shows a blank or invisible frame, 'Resource not found: ui://', 'Invalid ui.domain format', or a submission error such as annotations_required. `verdict` is ok, at_risk, broken, no_ui, needs_sign_in or unreachable. The URL must be public https; checks are limited to 30 a minute per caller.

  Paramètres, retour & exemple (2)

  Paramètres

  • url · string · requis
    The server's Streamable HTTP endpoint, exactly as a user adds it to a host, e.g. `https://example.com/mcp` (Claude's ui.domain is a hash of this exact string). Public https only.
  • host · string · optionnel · spec | claude | chatgpt | chatgpt-directory
    Judge for one host only: `spec` (any MCP Apps host), `claude` (claude.ai and Claude Desktop), `chatgpt`, or `chatgpt-directory` (OpenAI's review of a submitted app). Omit to get all four.

  Exemple d'appel

  {"name": "mcp_liveness_check_apps", "arguments": {"url": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• mcp_liveness_check_auth≈ 527 tokens

  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. Steps, in order: one unauthenticated request (it must answer 401 with a WWW-Authenticate challenge); RFC 9728 protected-resource metadata; RFC 8414 or OpenID Connect discovery at the locations the 2026-07-28 MCP spec lists, with the issuer and PKCE S256 checked; and how a client gets a client ID (client ID metadata documents, dynamic registration, or a pasted ID). Then a verdict per client — claude.ai, Claude Code, ChatGPT, VS Code, Cursor — emulated from each client's published requirements and known issues; no client is run. Use it when a user says a connector shows an error such as 'Authorization with the MCP server failed' or 'Dynamic Client Registration not supported', or before publishing a server that needs sign-in. `verdict` is ok, at_risk, broken, no_auth (it asked for no credential) or unreachable. The URL must be public https; checks are limited to 30 a minute per caller.

  Paramètres, retour & exemple (2)

  Paramètres

  • url · string · requis
    The server's Streamable HTTP endpoint, as a user would enter it in a client, e.g. `https://example.com/mcp`. Public https only.
  • client · string · optionnel · claude-ai | claude-code | chatgpt | vscode | cursor
    Judge for one client only: `claude-ai` (claude.ai and Claude Desktop), `claude-code`, `chatgpt`, `vscode` or `cursor`. Omit to get all five.

  Exemple d'appel

  {"name": "mcp_liveness_check_auth", "arguments": {"url": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• mcp_liveness_drift≈ 458 tokens

  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 prompt or an integration written against its tools has started failing, or before relying on a cached tool description. A liveness check says a server answers today; this says whether it is still the same server that code was written against. The answer names the changed tools and the kind of change. It does not diff the schemas themselves: the snapshots keep content hashes, not bodies, so `detail` hands back the release-asset location of both full months for a caller that needs the exact diff. A month with no snapshot for that server gets an error naming the months that do have one, never an empty diff that would read as `nothing changed`.

  Paramètres, retour & exemple (2)

  Paramètres

  • name · string · requis
    Exact registry name, namespaced — e.g. `io.github.owner/server`. Not a URL and not a title.
  • since · string · optionnel
    The month to diff from, as `YYYY-MM`. Omit it to diff from the earliest month this server appears in, which is the stable choice — a hard-coded month goes wrong as soon as the next snapshot lands.

  Exemple d'appel

  {"name": "mcp_liveness_drift", "arguments": {"name": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• mcp_liveness_explain_outcomes≈ 176 tokens

  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 changes between calls.

  Paramètres, retour & exemple (0)

  Exemple d'appel

  {"name": "mcp_liveness_explain_outcomes", "arguments": {}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

C'est votre serveur ?

Revendiquez-le sur l'espace créateur (preuve GitHub, domaine ou npm) pour afficher le badge « propriétaire vérifié » et lancer un pentest comportemental à la demande afin d'obtenir le badge « Vérifié ».

Créer un compte / revendiquer →

Source

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