MCP Server for Z.AI - A Model Context Protocol server that provides AI capabilities
Nothing to run from here
Liveness is installed from its publisher's own source and answers where it runs, so this marketplace is not in the path of a single call. There is no address here to send one to, and a panel that pretended otherwise would be showing you an answer we made up. Install it and call it from your own client — the Installation tab has the entry for each one.
5
tools declared
—
trust score
remote
at its publisher
—
calls last 7d
What it does
Does an MCP server work for a stock client? By registry name or URL. Tool drift too. Free, no key.
Quickstart
# 1 — add it to Claude Code
claude mcp add --scope user --transport http liveness-mcp https://agentwares-mcp-liveness.vercel.app/mcp
# 2 — ask your agent for something these tools do
# mcp_liveness_check, mcp_liveness_explain_outcomes, mcp_liveness_drift and 2 more
Liveness costs nothing on mcprush: there is no plan to choose here, no cap to set and nothing mcprush can bill you for.
Publishernot claimed
AGAll 9 servers
agentwares9 servers
5 categories
Collected from a public index. Nobody has claimed this account, so nothing here was written by its author — claim it if it is yours.
Installation
Where are you running it?
Every route below installs the same thing and ends at the same approval screen. Nothing here runs on your machine and nothing runs on ours: this server answers at its publisher’s own address, and what you install is the connection straight to it.
Claude Codedeclared by this listing
This is a public server: it answers at its publisher’s own address and this marketplace is not in the path. Claude Code registers it in one command; --scope user makes it available in every project. The transport below is http, as the publisher's own manifest declares it.
claude mcp add --scope user --transport http liveness-mcp https://agentwares-mcp-liveness.vercel.app/mcpReconnect, or start a new session, and the tools appear in the model’s tool list.
Free on mcprush, and it answers at its publisher’s own address: this marketplace is not in the path, so there is no key of ours to hold and no card to add.
What it writes
One config entry pointing straight at the publisher’s own address — this marketplace is not in the path, and nothing from this listing executes on your machine.
What you approve
5 tools, with what each one reads, writes and reaches shown before you agree — the same list on every route above. Read the tool surface.
Tool surface
What the model actually sees. Descriptions are diffed on every release — see version history.
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 acc
| Parameter | Type | Required | Notes |
|---|---|---|---|
| name | string | no | 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. |
| url | string | no | 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. |
| skipCredentialCheck | boolean | no | 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 cha |
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.
No parameter schema on file.
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 t
| Parameter | Type | Required | Notes |
|---|---|---|---|
| name | string | yes | Exact registry name, namespaced — e.g. io.github.owner/server. Not a URL and not a title. |
| since | string | no | 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. |
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);
| Parameter | Type | Required | Notes |
|---|---|---|---|
| url | string | yes | 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 | no | Judge for one client only: claude-ai (claude.ai and Claude Desktop), claude-code, chatgpt, vscode or cursor. Omit to get all five. |
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,
| Parameter | Type | Required | Notes |
|---|---|---|---|
| url | string | yes | 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 | no | 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. |
Free
$0 forever
- Every tool — any call limit is its publisher’s, not ours
- No card, and mcprush charges nothing for it
- Runs at its publisher’s own address — this marketplace is not in the path
- Nothing to cap, because mcprush bills nothing
What counts against your monthly calls
| Tool | Unit | Calls used | Out of the allowance |
|---|
Nothing here is billable: mcprush charges nothing to install Liveness or to call it, at any volume.
Call allowance · this installenforced at the gateway
Monthly allowance, in calls
—
—
Alert at 80% · then the tool returns a normal MCP error
Used this month: —
—Grade not published
No rule-by-rule report on file for this release
Two independent axes, because powerful and malicious are different questions. The grade is threat only. The capability level is blast radius, and it is never a penalty on the grade — it is priced as one subtract-only term in the score, where you can see it.
This listing is an address its publisher runs, and you connect to it directly — this marketplace is not in the path. The scanner reads packages and public source, and an address is neither. So there is no grade — not a withheld one, an unmeasured one.
Release history
This is an address its publisher runs: which release it serves is theirs to choose, so there is nothing here to pin. The history below is for reading; the current release on file is 0.3.0.
0.3.0
undated
latestNo release note was published with this version.
—
no reviews yet
Who can review
One review per account, from a signed-in account that does not publish this listing. Nothing else is asked — you can say what you think before you install it. Publishers can reply once per review, and a review can be edited or deleted by whoever wrote it.
Sign in to write one
Any signed-in account that does not publish Liveness can review it, once — before installing it or after. A review from an account that has installed it is marked as one.
No reviews yet
Nobody has reviewed this listing. The rating on the card is the mean of the reviews written here and nothing else, so there is no rating until somebody writes the first — which takes a signed-in account that does not publish it, and nothing else.