MCPFax Reliability
com.mcpscores/agent-reliability-scores · 1.1.5
Before you pay an endpoint you cannot vouch for: credit grade, drift and preflight.
Nobody here has read this server's code, because it publishes none. The description above is the maker's own, from the registry. A connection test shows whether it answers and what tools it says it has; it never calls a tool, so it cannot show what one does with your data.
Where it sits in the directory's order
What can be seen from outside, weighed as the directory publishes.
Observable signals: 45 of 100 points (at most 60 here)
| Input | Points | What was seen |
|---|---|---|
| Source published | held at 0 | No entry here publishes source: that is what puts it in this directory. |
| Licence stated | held at 0 | With no files, there is nothing for a licence to be stated in or held against. |
| Advisory state | held at 0 | Advisory databases index packages, and these entries publish none, so there is nothing to look up. |
| Auth declared | 0 of 15 | The registry entry declares no key. That is what it declares, not a finding that it has no protection. |
| Latest connection test reached it | 20 of 20 |
Where it answers
https://mcpfax-reliability.bowling-anthony.workers.dev/mcpstreamable-http
Connection test
The MCP handshake, then a request for the tool list, with no key and no data of yours. Run nightly, and by anyone, at most once every ten minutes per server.
It completed the handshake and listed 7 tools.
- Protocol
- 2025-06-18
- Calls itself
- com.mcpscores/agent-reliability-scores 1.1.5
- Handshake time
- 104 ms
- HTTP status
- 200
The tools it lists (7, as of 3 days ago)
The tool-description rules found nothing in these descriptions. They look for instructions aimed at a model and for hidden characters; they cannot see what a tool does when it runs.
mcpfax_endpoint_credit_scoreCreditworthiness 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 p
mcpfax_integration_driftWhat 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
mcpfax_wallet_authenticityPayer-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 observ
mcpfax_endpoint_revenue_estimateObserved 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.
How this entry becomes a listing
For the maker. The catalogue lists what it can read, and this server publishes nothing to read yet. There are two routes, and only the first is open today.
Publish the source Open today
- Put the server's source in a public repository on github.com, with a licence.
- Keep a server.json in that repository naming this server,
com.mcpscores/agent-reliability-scores, and declare the repository in it:"repository": { "url": "https://github.com/owner/repo", "source": "github" }, adding"subfolder"when the server lives in a folder. - Publish that version to the official MCP registry.
- The nightly registry sweep records the declaration. This page stays, dated, and says the source is declared but not yet read.
- The catalogue reads declared repositories at a pinned commit, in batches run by hand, and lists the servers that meet the batch's rules (among them a server.json at that commit naming the server, an https endpoint and a licence). When it lists this server, this page links to the listing. There is no schedule, so no date can be promised.
List it through the maker studio Not open yet
From the official MCP registry, last updated there 38 days ago. The registry entry · mcpscores.com