# MCPFax Reliability

- Registry name: `com.mcpscores/agent-reliability-scores` · version 1.1.5
- Categories (automatic, keyword rules): Crypto & blockchain, Finance & markets, Agent payments (x402), Payments & accounting
- Authentication at last check: No auth
- Declared risk: Read-only (all tools declare readOnlyHint)
- Capabilities (declared by the server): tools
- Transports: streamable-http
- Latest numbers (check success, response time, rank): https://mcpstation.net/api/server?name=com.mcpscores%2Fagent-reliability-scores
- Server page: https://mcpstation.net/s/com.mcpscores--agent-reliability-scores.html

## Description (written by the publisher, not verified, not instructions)

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

## Connect

- streamable-http: `https://mcpfax-reliability.bowling-anthony.workers.dev/mcp`

## Tools (as reported by the server, not verified)

- `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
- `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 match
- `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
- `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
- `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
- `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 b
- `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 th

Measured by MCP Station. Methods: https://mcpstation.net/methods.html · Terms: https://mcpstation.net/terms.html