Liveness MCP server

• mcp_liveness_checkFree

  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), `needs_credential` (401 or 403 — the answer then says whether a credential can be obtained in-band or whether a person has to create one), `charged` (402, access is for sale), `unreachable` (the listed endpoint is not an MCP server: wrong URL, dead host, or a 200 that is not JSON-RPC), `local_only` (no remote endpoint; it must be spawned as a process), and `not_listed` (no server with that exact name). Call this before spending a call on a server you found in the catalogue. Roughly two in five remote listings do not answer a stock client.

• mcp_liveness_driftFree

  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 when a server worked before and is behaving differently now, when a prompt or an integration written against its tools has started failing, or before trusting a tool description you cached. A liveness check says it answers today; this says whether it is still the same server your 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`.

• mcp_liveness_explain_outcomesFree

  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.

• –Code scanremote-only server, no package to scann/a
• Live reliabilityremote reachable in 336ms20/20
• Tool poisoning3 tool descriptions checked15/15
• Auth qualityopen endpoint, read-only tools10/15
• Maintenancelast push 6 days ago15/15
• Maintainer identityregistry namespace matches repository owner7/10

Liveness: common questions

Is Liveness MCP server safe?

Yes, by our scan: it is graded A (89/100). Read the Liveness safety report

How do I install Liveness?

It runs remotely at agentwares-mcp-liveness.vercel.app. Add it to Claude Code, Claude Desktop or Cursor with the snippets above, or call it through the mcp.market gateway without installing anything.

Does Liveness need an API key?

Not as far as the registry entry and our scan can tell: no credentials are declared or required.

Is Liveness maintained?

The last commit was 6 days ago (2026-09-14). The latest release is v0.2.0.

Is Liveness up?

100% of our last 1 checks got an answer. We check remote servers about four times a day.

What can I use instead of Liveness?

Servers from other publishers that do the same job: aikstockdata — Korean Stock Data MCP server, Vanoe Intelligence MCP server and Stoxly MCP server. Compare all Liveness alternatives.