Skip to content
Agentmart
Submit a tool

MCP Liveness

Does an MCP server work for a stock client?

Connector by agentwares · GitHub account verified by the MCP Registry

IndexedLicense unknownRemote (HTTP)
Write a review

Install

Works with Claude Code, VS Code, Cursor, Windsurf. Read the repository before you give any tool access to your data.

npx agentmarket install connector/agentwares-mcp-liveness

Asks which of your tools to add it to (Claude Code, Codex, Cursor, VS Code, Windsurf, Gemini CLI, Claude Desktop) and shows the change first. See https://agentmart.dev/cli.

Remote endpoint

  • https://agentwares-mcp-liveness.vercel.app/mcp Remote (HTTP)

Get the weekly diff

The weekly diff: one email a week with new agent tools, notable updates and grade changes, plus security alerts for tools you follow. Double opt-in, one-click unsubscribe.

We use your email only for this newsletter. Privacy

About

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

Reviews

Write a review

No reviews yet. Installed it? Reviews come from verified installers only. How reviews work

Permissions

What this server can do and what it asks for, from its tool list and install config. Checked Oct 25, 2026.

Tools
5 read · 0 write · 0 deleteRead-only
Secrets
None asked for
Install scripts
Nothing to install (hosted)
Runs as
Hosted (remote endpoint)

Tools by what they do 5

From the running server's own tool list (tools/list) on Oct 25, 2026.

Read 5 · Look things up without changing anything.

  • mcp_liveness_check
  • mcp_liveness_check_apps
  • mcp_liveness_check_auth
  • mcp_liveness_drift
  • mcp_liveness_explain_outcomes

Network hosts it talks to 1

  • agentwares-mcp-liveness.vercel.app · found in remote endpoint, install command

Tools (5)

As the server listed them on Oct 25, 2026. Descriptions are the server’s own words; hidden characters are shown as [U+…].

  • mcp_liveness_checkCan a stock client use this MCP server?read-only

    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 pe…

  • mcp_liveness_check_appsWhy does this MCP App render blank?read-only

    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…

  • mcp_liveness_check_authWhere does this MCP server's sign-in break?read-only

    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 (cli…

  • mcp_liveness_driftWhat changed in this server's tools since a given monthread-only

    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. …

  • mcp_liveness_explain_outcomesWhat the outcomes meanread-only

    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.

Signals

Last release
Oct 6, 2026 (23 days ago)
Repository
Not found on GitHub (deleted or private)

Details

Registry name
io.github.agentwares/mcp-liveness
Version
0.3.0
Auth
Auth not stated
License
License unknown
Repository
github.com/agentwares/servers
Website
agentwares-mcp-liveness.vercel.app
First seen
Oct 24, 2026
Last checked
Oct 25, 2026
Source
Official MCP Registry

More from agentwares

Cite this page

MCP Liveness. Agent Mart. https://agentmart.dev/connectors/agentwares-mcp-liveness (last updated 2026-10-25)