MCP Server for Z.AI - A Model Context Protocol server that provides AI capabilities
MCPFax Reliability 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.
What it does
Before you pay an endpoint you cannot vouch for: credit grade, drift and preflight.
Quickstart
# 1 — add it to Claude Code
claude mcp add --scope user --transport http mcpfax-reliability https://mcpfax-reliability.bowling-anthony.workers.dev/mcp
# 2 — ask your agent for something these tools do
# mcpfax_endpoint_credit_score, mcpfax_integration_drift, mcpfax_wallet_authenticity and 4 more
MCPFax Reliability costs nothing on mcprush: there is no plan to choose here, no cap to set and nothing mcprush can bill you for.
Collected from a public index. Nobody has claimed this account, so nothing here was written by its author — claim it if it is yours.
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.
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 mcpfax-reliability https://mcpfax-reliability.bowling-anthony.workers.dev/mcpReconnect, or start a new session, and the tools appear in the model’s tool list.
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.
7 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.
Creditworthiness grade for one x402 endpoint or MCP server: letter grade A-E (or NR when unrated), a 0-1000 score, per-component subscores, a confidence level, flags, and the dated evidence each figure rests on. Use this before trusting or paying an unfamiliar endpoint. The grade ranks observed risk; it is not a calibrated probability of failure, not validated over any forward horizon, and not a s
| Parameter | Type | Required | Notes |
|---|---|---|---|
| endpoint | string | yes | Observatory listing id. Use 'host:<hostname>' for an x402 endpoint, e.g. 'host:api.example.com', or 'mcp:<publisher>/<name>' for a registry-listed MCP server, e.g. 'mcp:acme/weather'. |
What changed under an x402 endpoint or MCP server you have ALREADY integrated: payTo rotations, price, asset and network changes, terms added or removed, and tool-schema changes. This is not a discovery tool and will not help you choose a server; it tells you whether the one you wired in still matches what you wired in. Pass up to 50 subjects and the since watermark returned by your last call, a
| Parameter | Type | Required | Notes |
|---|---|---|---|
| subjects | string | yes | Comma-separated endpoint URLs or host identifiers to check, at most 50, e.g. 'https://x402.browserbase.com/browser/session/create,host:api.example.com'. |
| since | string | no | The watermark from your previous call (YYYY-MM-DD). Omit on a first call to receive the whole archive. |
Payer-concentration and wash-risk assessment for a receiving wallet: how concentrated its observed payers are, the measured coverage of that observation, an explicit wash-risk haircut ONLY when coverage is sufficient, how many listings declare the same address, and observed USDC inflow. Use this to judge whether a seller's apparent revenue reflects real independent demand. The haircut and the adju
| Parameter | Type | Required | Notes |
|---|---|---|---|
| wallet | string | yes | The receiving EVM wallet address, 0x followed by 40 hex characters, e.g. '0x1831f336585a6C67B6A954d28f3E07F44C4EEBbd'. |
Observed on-chain revenue signals for one listing: total USDC inflow, how many distinct payers, the modal transfer size, payment rate, 7- and 30-day trend windows, and where it sits in its cohort by percentile. Use this to size a seller's real traction. Inflow is observed on-chain and is not proven to be x402 sales revenue. Trend windows are only as wide as the wallet's real scanned span, which th
| Parameter | Type | Required | Notes |
|---|---|---|---|
| endpoint | string | yes | Observatory listing id. Use 'host:<hostname>' for an x402 endpoint, e.g. 'host:api.example.com', or 'mcp:<publisher>/<name>' for a registry-listed MCP server, e.g. 'mcp:acme/weather'. |
Know-your-agent profile for a paying wallet: how many distinct services it pays, total observed spend, whether the address is a contract or an externally owned account, and coverage-gated screening signals. Use this to vet a counterparty that is paying you. Screening signals are withheld with status "not_rated" until the observed record for the address clears the published coverage floor (14 days,
| Parameter | Type | Required | Notes |
|---|---|---|---|
| address | string | yes | The paying EVM wallet address, 0x followed by 40 hex characters. |
Chronological feed of rating actions since a date: grade upgrades and downgrades, payTo wallet changes (a seller redirecting payment), listing removals, and returns. Use this to monitor a portfolio of endpoints for adverse changes rather than re-scoring each one. The feed cannot return events from before the observatory archive started; the response reports coverage.archive_since, coverage.rating_
| Parameter | Type | Required | Notes |
|---|---|---|---|
| since | string | no | Inclusive UTC start date in YYYY-MM-DD form, e.g. '2026-07-01'. Defaults to 30 days ago, but the feed cannot return events from before the archive start reported by GET /health; the response echoes ef |
Check that an endpoint is live and that its terms have not changed, BEFORE you send it an expensive request. A $15 call with a hypothetical 2% loss rate carries $0.30 of expected loss; a reachability check cannot promise to prevent it. Compare the quoted fee with the value of the pending call and the failures this check can actually detect. For a cheap $0.001 lookup, the $0.008 fee is eight times
| Parameter | Type | Required | Notes |
|---|---|---|---|
| target | string | yes | The endpoint you are about to call. Preferred form is the absolute https:// URL of the exact resource you will pay for, e.g. 'https://api.example.com/v1/search'. An observatory id also works: 'host:<h |
| expected_price | string | no | What you believe the call costs. A decimal such as '0.01' is read as USD; a bare integer such as '10000' is read as atomic units. |
| expected_payto | string | no | The payment destination you believe you are paying — an EVM address or a base58 Solana address. A mismatch is the strongest signal this tool produces. |
| expected_schema_hash | string | no | The schema hash a previous call to this tool returned in live.schema_hash. It covers tool names and input/output schemas, not titles or descriptions. |
| max_age_seconds | integer | no | Your freshness bar, default 300. A stored observation older than this is still reported but may not support an ALLOW verdict. A stored observation newer than this can stand in for the live half if the |
| probe_method | string | no | HTTP method for the unpaid probe of a non-MCP endpoint, default GET. Only side-effect-free methods are accepted; this tool never sends a request that could change state at the target. A POST-only reso |
- 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 MCPFax Reliability or to call it, at any volume.
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 1.1.5.
No release note was published with this version.
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.
Any signed-in account that does not publish MCPFax Reliability can review it, once — before installing it or after. A review from an account that has installed it is marked as one.
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.