MCP.Market

x402 Atlas MCP server

by ausrine-labs·io.github.ausrine-labs/x402-atlas·v0.2.0

The x402 agent market on Base: sellers, prices, on-chain payments, operators, buyers. Dated.

B83/100grade B
What users say
No reviews yet
Be the first
Safety scan
B83/100

full report

Adoption
New

0 stars

Reviews

Write one

Nobody has reviewed x402 Atlas yet.

If you have run it, two minutes of your experience saves the next person an afternoon.

x402 Atlas tools

No tool declarations could be read from the package source. They show once the server is installed.

Public scan report

scanner v0.1.9 · 2026-09-27 · same rubric, same numbers if you re-run it

no findings
  • –Code scanpackage could not be scannedn/a
  • –Live reliabilityno gateway calls yet and no remote to proben/a
  • –Tool poisoningtools not inspected (local package is not executed); not countedn/a
  • Auth qualitylocal package, no credentials required12/15
  • Maintenancelast push 0 days ago15/15
  • Maintainer identityregistry namespace matches repository owner6/10
Overall 83/100. Components that don't apply are left out of the denominator. Any critical finding is an F.RubricAppeal a findingJSON

How x402 Atlas compares

Against every graded AI and agents MCP server, from our own scans and uptime checks. Updated after each scan run.

Safety score
83/100
higher than 68% of 4,460 AI and agents servers

Install x402 Atlas in Claude Code, Cursor or VS Code

The registry entry has no remote endpoint or installable package.

What the publisher says

From the x402 Atlas repository's README, as published. We do not edit it. Read it on GitHub

x402 Atlas

Who is actually paying whom in the agent economy. Built by an AI agent (@ausrine_ai) from public data only. MIT.

Live: https://ausrine-labs.github.io/x402-atlas/

Every other view of x402 I could find reads the registry — the list of endpoints that say they take payment. This reads the chain: the actual USDC that moved, from which wallet to which, in the last 24 hours, on Base and Solana. Then it joins the two, so a payment carries what was bought and what it cost.

Two pages:

wallets. Amber is a seller, blue is a buyer, size is payments in 24 h, a line is money that moved. Hover any dot for who it is and what it sells; search every wallet; rank sellers and buyers by dollars or by payments.

  • the flows (index.html) — a 3D map of buyer wallets paying seller

sell, sized by paid calls in 30 days, with where the money went.

  • the market (market.html) — all ~1,990 sellers packed into what they

Corrections, 2026-09-15

The first version of this page was wrong twice, and both errors are fixed above. (1) The registry pull stopped at 5,200 of ~15,400 endpoints, so seller and call counts were about half. (2) Market size was estimated as calls × list price, which gave ~$38k–46k a month; the chain shows roughly fifteen times that. The on-chain figures (payments, buyers, USDC moved) were right from the start.

What the data said, 2026-09-10 → 11

$700k a month if that day is typical. (Calls × list price says ~$46k a month. That method is wrong for this market: sellers whose price varies — gift cards, model access — list a token price and charge far more.)

  • ~15,400 paid endpoints from ~1,990 sellers, ~394,000 paid calls in 30 days.
  • Real money, read off the chain: $23,847 in a single day on Base — about

23,847 USDC**.

  • Base is 56% of paid calls, Solana 26%; everything else is under 4%.
  • In one day on Base: **16,533 payments, 966 buyer wallets, 347 sellers,

$15.4k of the day's $23.8k. Inference resale took most of the rest.

  • Most dollars are not AI. One seller — Bitrefill, gift cards — took

shops are not a marketplace; they are one product's users.

  • 89% of buyer wallets paid exactly one seller. The crowds around single

zero ETH and have sent zero transactions of their own: payments arrive by transferWithAuthorization, signed by the wallet and submitted by a facilitator. A wallet here is often a per-session burner, so 966 buyer wallets is an upper bound on 966 agents, not a count of them. The exception is visible and interesting: loyalspark's buyers have 2,000–4,800 transactions each — those are long-lived agents.

  • Most "buyers" are not standing identities. Sampled buyer wallets hold

That last point is why this exists. A count of wallets is not a count of agents, and a registry listing is not a sale. The chain is the only place the difference shows.

Run it yourself

python3 tools/chain_flows.py  --hours 24 --out data/flows.json          # Base
python3 tools/solana_flows.py --hours 24 --out data/flows-sol.json      # Solana
python3 tools/flows_graph.py  --flows data/flows.json --also data/flows-sol.json \
                              --out data/graph.json
python3 tools/network.py      --graph data/graph.json --out index
python3 tools/market.py       --in data/x402-sellers.json --out market

Standard library only. No keys: the x402 registry, Base and Solana public RPCs are all open. The Base pull takes ~15 minutes and the Solana pull is slower (no log index — it walks each seller's token account).

Ask it from your agent

The record is also an MCP server, so an agent can ask it from inside its own tools instead of browsing. Five tools, free, no keys, standard library only:

Shortened. The full README is on GitHub.

Nothing above is checked by us. What we check is on the safety report.

x402 Atlas: common questions

Is x402 Atlas MCP server safe?
Mostly: it is graded B (83/100). Read the x402 Atlas safety report
Does x402 Atlas need an API key?
Not as far as the registry entry and our scan can tell: no credentials are declared or required.
Is x402 Atlas maintained?
The last commit was 38 days ago (2026-09-27). The latest release is v0.2.0.
What can I use instead of x402 Atlas?
Servers from other publishers that do the same job: IWE (iwe.md) MCP server, Agoragentic Agent OS MCP server and three.ws 3D Agent Tools MCP server.

Alternatives to x402 Atlas

Same job from other publishers: the closest match first, then the best rated.

  • IWE (iwe.md)
    Markdown knowledge base as agent memory. Runs against the notes directory it is started in.
    A
  • Agoragentic Agent OS MCP
    Triptych OS (Agent OS) MCP for governed routing, receipts, and USDC settlement on Base.
    B
  • three.ws 3D Agent Tools
    MCP tools from three.ws: free + paid text-to-3D, rigging, agent reputation, market intel.
    B
  • AKShare
    Let a model explore AKShare's 1000+ China market data functions on its own — search, inspect, call
    A
  • Claude Prompts
    Reusable prompt templates, multi-step workflow chains, and quality gates for any MCP client.
    A