mcpbeat Sign in

MCPFax Reliability MCP Server

answering

MCPFax Reliability is answering right now. Last checked moments ago. It exposes 7 tools.

Before you pay an endpoint you cannot vouch for: credit grade, drift and preflight.

Uptime history 64 days of history · worst day 93%
64 days agonow
100.0%
Uptime 24h
92 of 92 checks
7
Tools
read from the server
80 ms
Response time
average over 24h
open, no key
Access
streamable-http

What changed 18

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

5 Sep 6 tool descriptions were rewritten8 times that day mcpfax_endpoint_credit_score, mcpfax_endpoint_revenue_estimate, mcpfax_integration_drift and 3 more
4 Sep 7 tools changed the parameters they ask for mcpfax_endpoint_credit_score, mcpfax_endpoint_revenue_estimate, mcpfax_integration_drift and 4 more
4 Sep a tool changed version
16 Aug a tool changed version
15 Aug a tool changed version
and 2 more, back to 15 August 2026

Nothing serious here today

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

Three servers free · no card

Connect this server

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

run in your terminal
claude mcp add agent-reliability-scores --transport http https://mcpfax-reliability.bowling-anthony.workers.dev/mcp
~/Library/Application Support/Claude/claude_desktop_config.json
{
  "mcpServers": {
    "agent-reliability-scores": {
      "url": "https://mcpfax-reliability.bowling-anthony.workers.dev/mcp"
    }
  }
}
~/.codex/config.toml
[mcp_servers.agent-reliability-scores]
url = "https://mcpfax-reliability.bowling-anthony.workers.dev/mcp"
.cursor/mcp.json
{
  "mcpServers": {
    "agent-reliability-scores": {
      "url": "https://mcpfax-reliability.bowling-anthony.workers.dev/mcp"
    }
  }
}
.vscode/mcp.json
{
  "mcpServers": {
    "agent-reliability-scores": {
      "url": "https://mcpfax-reliability.bowling-anthony.workers.dev/mcp"
    }
  }
}

Available tools 7

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

mcpfax
mcpfax_endpoint_credit_score
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 security audit. Coverage is young: the response carries archive_coverage (measured archive span), most listings grade NR, and payer-concentration risk is reported as "not rated" until a listing's own payment record clears the published coverage floor. Costs $0.008 USDC per call via x402 on Base.
mcpfax_endpoint_revenue_estimate
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 the response reports as trends.scanned_days with per-window backed-by-scan flags; a 30-day window is not yet backed by 30 days of scanning. Costs $0.005 USDC per call via x402 on Base.
mcpfax_integration_drift
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, and you receive only what changed after it plus a fresh watermark, so repeat checks stay cheap. A subject with no changes is reported as observed-unchanged with the date that is true as of — that is a real answer and is billed. A subject MCPFax has never observed is named in `not_observed` and given NO verdict, because reporting "no changes" about something we never watched is indistinguishable from a genuine all-clear. The watermark is the last date MCPFax actually observed, never the current clock, so no window is skipped between sweeps. Coverage is young and every response carries its archive span. Costs $0.008 USDC per call via x402 on Base.
mcpfax_payer_wallet_profile
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, 20 payments); the measured graph facts are always returned and carry no inference about intent. Costs $0.008 USDC per call via x402 on Base.
mcpfax_payto_change_feed
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_actions_recorded, and whether the requested window predates the archive. Costs $0.005 USDC per call via x402 on Base.
mcpfax_preflight_check
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 the call price. Returns two halves. LIVE: one unpaid bounded probe (~2.2s cap) giving reachability, HTTP status, latency, whether an MCP server still answers initialize, and the price and payTo it is serving right now. HISTORICAL: reliability over our OBSERVED window (stated in days, never implied), payTo changes, price changes, tool-schema changes, first-seen date, and credit grade or an honest not-rated. Supply expected_price, expected_payto or expected_schema_hash and each is compared with old to new and the date we first observed the change. The verdict is ALLOW, WARN or UNKNOWN and is ADVISORY: it reports evidence, it is not a warranty, an audit, or a promise your call will succeed. UNKNOWN is a real answer and is returned whenever the evidence does not support the other two. If we have never observed the target AND cannot reach it, you get UNKNOWN and are charged nothing. Otherwise $0.008 USDC per call via x402 on Base.
mcpfax_wallet_authenticity
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 adjusted-inflow figure are withheld as null with status "not_rated" until the wallet's own record covers at least 14 days and 20 payments, because below that a thin payer count is a property of our observation window, not of the wallet. Concentration is not proof of common control. Costs $0.01 USDC per call via x402 on Base.

Endpoints

URLTransportStateLatencyChecked
https://mcpfax-reliability.bowling-anthony.workers.dev/mcp streamable-http answering 76 ms 0 min ago

Alternatives to MCPFax Reliability

same job, measured the same way
Execute cyber-breach-liability-mcp
by evozim

Premium agentic endpoint for cyber-breach-liability-mcp.

1 tools answering
Hagglyai
by hagglyai

Compare paid agent endpoints (x402 + MCP) on price, uptime and real usage before you pay.

5 tools answering
PREFLIGHT — URL Routing for AI Agents
by gsterlingpress

Choose HTTP, browser, machine endpoint, or avoid before an agent visits an unfamiliar URL.

2 tools answering
Execute credit-risk-mcp
by evozim

Premium agentic endpoint for credit-risk-mcp.

1 tools answering
A
Agent Utility MCP
by insivotron

Stop your agent before it runs rm -rf /etc or emails your .env. Deterministic preflight checks.

4 tools answering
Lumière PayCheck
by book0feli

Check any x402 endpoint before your AI agent pays it: trust grade, verdict, and hijack checks.

6 tools answering
Endpoint Diligence
by x402supply

Live x402 endpoint trust/diligence check before you pay it. $0.02/call via x402.

3 tools answering
Attest
by attestagents

Scan agent payment endpoints (x402, AP2, L402, MPP, 402) for a trust grade A-F before paying.

28 installs/wk 2 tools answering

MCPFax Reliability — questions

Answers built from our own checks of this server.

What can MCPFax Reliability do?
It exposes 7 tools, read directly from the server on our last check. Among them: mcpfax_endpoint_credit_score, mcpfax_endpoint_revenue_estimate, mcpfax_integration_drift, mcpfax_payer_wallet_profile, mcpfax_payto_change_feed, mcpfax_preflight_check and 1 more. 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 MCPFax Reliability 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 80 ms. The bar chart above shows every period we have measured.
How do I connect MCPFax Reliability?
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 MCPFax Reliability need an API key?
No. MCPFax Reliability completed a full MCP handshake with us as an anonymous client and listed its tools without asking for anything. All 7 of them are readable on this page. This is what we observed, not what the docs claim.
How fast is MCPFax Reliability?
It answers our handshake in 80 ms on average, which is faster than 89% of all working MCP servers we measure. That puts it in the quick quarter of the ecosystem. The comparison comes from our own checks across the whole registry, every 15 minutes.