NR Not rated

Public evidence report · x402 endpoint host

anchor-x402 — 18 x402 pay-per-call services for AI agents

host:api.anchor-x402.com · https://api.anchor-x402.com

Numeric scorewithheld
Confidencelow
Archive coverage2 day(s)
Successful observations2
Tools discovered
Observations as of Method MCP Authority 1.0 Meaning Not enough observation history for a published grade

Why there is no number here.

Below the publication floor, MCP Scores publishes no grade and no numeric score. NR is not a favorable or adverse finding.

  • archive coverage is 2 day(s); 7 are required
  • successful observations are 2; 3 are required
Publication floor progress Archive coverage 2 of 7 required days. Successful observations 2 of 3 required. ARCHIVE DAYS 2 / 7 OBSERVATIONS 2 / 3

Earliest eligible publication date: 2026-08-17, if observation continues without interruption.

NR is not a favorable or adverse finding. The measured components below are model inputs, published as diagnostics with their own stated denominators — they are not a rating.

Decomposition

Five components. No hidden blend.

Component values run 0–100 and are measured, not modelled. The weight shown is that component's share of the 0–1000 composite for this listing type. The composite they feed is withheld until the publication floor is met.

R Reliability 100 30% weight
T Tenure 13 20% weight
F Financial evidence 51 20% weight
S Stability 85 15% weight
I Identity 60 15% weight

Evidence ledger

What was actually observed.

Every line separates a measured statement from its source table, its coverage confidence, and its observation date. No line infers motive or intent.

Measured statementSourceConfidenceObserved as of
First observed 2026-08-11; last observed 2026-08-12; 2 archive day(s); 2 successful observation(s). D1 resource_history + probes limited coverage
Served a qualifying HTTP response on 1/1 probes; returned any HTTP response on 1/1; valid payment challenge observed on 1/1. D1 probes limited coverage
Seller-owned domain registration date observed as 2026-05-09. R2 RDAP enrichment RDAP supplied
Payment terms were parseable; declared payee wallet 0x127462e296fAc1A7F5cF33bA57bB2f0FFf5cD0B6. R2 enrichment record listing declared
Observed on-chain USDC inflow: 0.01 across 10 inbound transfer(s) from 7 distinct payer(s); top payer share 30%. D1 wallet_flow, Base USDC transfer logs measured within scanned block range
1 distinct archive day(s) contain listing metadata changes. D1 resource_history archive history
The host published llms.txt when checked. R2 enrichment record single latest record

Material observations and score constraints

Financial-evidence credit is concentration-adjusted: 7 observed distinct payer(s); top payer share 30%; the declared payee also appears on 2 listings.

D1 wallet_flow + enrichment · measured within scanned block range · Aug 11, 2026, 04:33 PM UTC

Base USDC observation

Inflow, diversity, concentration.

Inbound USDC transfers observed inside a disclosed Base block range. MCP Scores never labels a balance or an observed inflow as operator revenue, and a wallet declaration does not establish legal ownership.

Observed inflow
0.01 USDC
Inbound transfers
10
Distinct payers
7
Top payer share
30%

Declared payee: 0x127462e296fAc1A7F5cF33bA57bB2f0FFf5cD0B6 · declared on 2 listing(s)

Wallet balance snapshot: 7.656 USDC as of Aug 11, 2026 UTC

Share of observed inbound transfers Top payer 3 of 10; All other payers 7 of 10Top payer: 3 (30.0%)All other payers: 7 (70.0%)
Top payerOther payers
Observed daily USDC inflow 1 observation day(s) from 2026-08-11 to 2026-08-11. Minimum 0.01, maximum 0.01. 2026-08-11: 0.01SINGLE ARCHIVE DAY — NO TREND EXISTS YET 2026-08-11 2026-08-11

Coverage. Base blocks 49,812,323–49,838,323, updated Aug 11, 2026, 04:33 PM UTC. Transfers outside that range are not included. “Top payer share” is a share of observed inbound transfer count and says nothing about payer identity or intent.

Longitudinal record

History, with the missing history visible.

Stored engine rating records are archive material only; the current rating above is the single authoritative figure and is recomputed read-only. 1 stored record(s) that never carried a published grade are withheld from this series, because replaying their numbers would publish the figure the NR rule withholds.

Stored engine score records

Internal Model 1.0 sweep records held in D1. These are engine diagnostics; the public figure is always the live recomputation shown above.

No engine rating record has been stored for this listing yet. The archive has to run a rating sweep before a history exists.

Stored score records for this listing.

Live badge

Carry the record with the listing.

The image is generated from this scorecard at request time and the link returns readers to this evidence ledger. It currently renders NR, because that is the honest state.

MCP Scores live rating for host:api.anchor-x402.com

Served live from mcpscores.com, cached five minutes. Badge rules and gallery →

HTML embed
<a href="https://mcpscores.com/score/host%3Aapi.anchor-x402.com" rel="noopener"><img src="https://mcpscores.com/badge/host%3Aapi.anchor-x402.com.svg" alt="MCP Scores live rating for host:api.anchor-x402.com" width="280" height="42"></a>
Markdown embed
[![MCP Scores live rating for host:api.anchor-x402.com](https://mcpscores.com/badge/host%3Aapi.anchor-x402.com.svg)](https://mcpscores.com/score/host%3Aapi.anchor-x402.com)

Coverage & limitations

What this report can — and cannot — support.

This report describes observed data at stated times. It does not allege intent or misconduct and is not an endorsement, guarantee, security audit, or transaction recommendation.

Included now

  • Rotating HTTP probes and latest endpoint enrichment
  • Archive tenure and listing-change days
  • Declared payment terms and available Base USDC observations

Limitations

  • The score is an ordinal Model 1.0 output, not a calibrated probability of failure.
  • Unpaid checks measure reachability and protocol responses; they do not prove paid delivery.
  • A score is not an endorsement, security audit, guarantee, or transaction recommendation.
  • The observation archive spans 2 calendar day(s) (2026-08-11 through 2026-08-12), with observations recorded on 2 day(s). No 30-day or 90-day trend, survival estimate, or forward horizon can be supported by an archive of that length.
  • The payee wallet is declared by listing metadata; the observation does not establish legal ownership.
  • Observed on-chain inflow covers Base blocks 49812323–49838323; transfers outside that scanned range are not included.

Pending model inputs

  • Cross-wallet funding-source analysis
  • Cohort survival percentile after sufficient archive age
  • Wallet-funded delivery verification
  • 90-day probability calibration and quarterly backtest

Corrections and appeals

Include the listing ID, the specific measured statement at issue, supporting evidence, and a reply address.

An accepted correction is recorded in the observatory action log and rendered on this scorecard, in this JSON payload, and in the MCP tool response, dated and attributed to MCP Authority.

corrections@mcpscores.com · Appeals process

GET https://mcpscores.com/api/score?id=host%3Aapi.anchor-x402.comOpen the factual JSON →