MCP Liveness MCP Server

by agentwares Your server? Claim it

answering

MCP Liveness is answering right now. Last checked 4 min ago. It exposes 3 tools. Last commit 14 Sep 2026.

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

Uptime history 7 days of history

7 days agonow

100.0%

Uptime 24h

92 of 92 checks

Tools

read from the server

245 ms

Response time

average over 24h

Stars

last commit 14 Sep 2026

What changed 2

Every tool that appeared, vanished or quietly changed what it asks for. Recorded since 13 September 2026. No other catalogue keeps this.

13 Sep a tool appeared mcp_liveness_drift

13 Sep a tool changed version

Nothing serious here today

Today is the operative word: we check MCP Liveness every 15 minutes and re-read its code on every release. Watch it and you find out the day that stops being true.

Connect this server

Endpoint below is the one we actually reach during checks — not the one copied from a README. Last verified 4 min ago.

Claude Code Claude Desktop Codex Cursor VS Code

run in your terminal

claude mcp add mcp-liveness --transport http https://agentwares-mcp-liveness.vercel.app/mcp

~/Library/Application Support/Claude/claude_desktop_config.json

{
  "mcpServers": {
    "mcp-liveness": {
      "url": "https://agentwares-mcp-liveness.vercel.app/mcp"
    }
  }
}

~/.codex/config.toml

[mcp_servers.mcp-liveness]
url = "https://agentwares-mcp-liveness.vercel.app/mcp"

.cursor/mcp.json

{
  "mcpServers": {
    "mcp-liveness": {
      "url": "https://agentwares-mcp-liveness.vercel.app/mcp"
    }
  }
}

.vscode/mcp.json

{
  "mcpServers": {
    "mcp-liveness": {
      "url": "https://agentwares-mcp-liveness.vercel.app/mcp"
    }
  }
}

Available tools 3

Read directly from the server with tools/list, grouped by what they act on. If a tool disappears, we record the date.

mcp

mcp_liveness_check

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_drift

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_outcomes

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.

Endpoints

URL	Transport	State	Latency	Checked
https://agentwares-mcp-liveness.vercel.app/mcp	streamable-http	answering	256 ms	4 min ago

Alternatives to MCP Liveness

same job, measured the same way

AkTools MCP Server

by aahl

MCP Server for stock and crypto

301 installs/wk local only

Jobber MCP Server

by friendlygeorge

MCP server for Jobber (home services SaaS) — exposes tools for clients, jobs, invoices, and quote...

33 installs/wk local only

Stripe

by stripe

MCP server integrating with Stripe - tools for customers, products, payments, and more.

answering

NordicMCP — Stripe

by nordicmcp

Hosted Stripe MCP server: 18 tools for payments, subscriptions, invoicing, customers, and reporting.

answering

mcp-cbr-rates

by atomno-mcp

CBR exchange rates and key rates for Russia. MCP tools for finance agents.

531 installs/wk local only

Openfinance Br MCP

by brunovicco

Secure Open Finance Brasil MCP server with typed tools and a credential-free mock mode

69 installs/wk local only

jPOS MCP Server

by mohisyed

MCP server for jPOS and ISO 8583. Deterministic payment protocol tools for AI agents.

74 installs/wk local only

ToolRank

by brandonclark1996-design

Rank MCP servers/APIs for a job. Lexical ranking, 36 curated tools, no Stripe.

3 tools answering

MCP Liveness — questions

Answers built from our own checks of this server.

What can MCP Liveness do?

It exposes 3 tools, read directly from the server on our last check. Among them: mcp_liveness_check, mcp_liveness_drift, mcp_liveness_explain_outcomes. The full list with descriptions is on this page — we take it from the server itself via tools/list, not from a README. How MCP servers expose tools in the first place →

Is MCP Liveness working right now?

We send a real MCP handshake every 15 minutes. Over the last 24 hours 92 of 92 checks got a reply (100.0%), average response time 245 ms. The bar chart above shows every period we have measured.

How do I connect MCP Liveness?

Copy the ready config from this page — we generate it for Claude Code, Claude Desktop, Codex, Cursor and VS Code, each with the file path that client actually reads. It is a remote server, so there is nothing to install — the client connects to the address.

Does MCP Liveness need an API key?

No. MCP Liveness completed a full MCP handshake with us as an anonymous client and listed its tools without asking for anything. All 3 of them are readable on this page. This is what we observed, not what the docs claim.

How fast is MCP Liveness?

It answers our handshake in 245 ms on average, which is faster than 58% of all working MCP servers we measure. The comparison comes from our own checks across the whole registry, every 15 minutes.

Is MCP Liveness open source?

Yes — it is published under the MIT licence and 0 stars on GitHub. The source link is on this page, so you can read exactly what it does with your data before you connect it.