DexSQL
SQL for Android APK and DEX files: classes, methods, strings, references and smali.
The x402 agent market on Base: sellers, prices, on-chain payments, operators, buyers. Dated.
Lists are ordered by a usage score (out of 100) built from these parts
| Popularity | 0/80 | GitHub stars or weekly downloads: the larger counts 60, the smaller 20 |
|---|---|---|
| Freshness | 12/12 | Full marks for a release or code change within 30 days |
| Still answering | 0/8 | The cloud endpoint answered at the last check |
| Usage score | 12/100 |
Quality: Passed 3/3 basic checks (shown, not used for ordering) · Momentum: No data yet (Used only on the Trending tab)
Pick the AI app you use, then copy the settings.
Passed 3/3 checks · Runs on your computer
First: which AI do you use?
Pick your app and the steps appear below.
Works with Claude, with some setup first
No key, nothing to install · Only the Claude desktop app (Windows or Mac), not the web or phone
Download the maker’s .mcpb file
The .mcpb file comes straight from the maker; we do not change it
Use x402 Atlas and tell me what you can do for me, then show me one thing✓ If Claude says it is using x402 Atlas or shows a x402 Atlas tool in the answer, you are connected
Menu names checked against Anthropic’s help page on Nov 11, 2026 · your screen may differ slightly by app version
ChatGPT cannot connect x402 Atlas yet
x402 Atlas runs on your computer, but ChatGPT can only connect servers that run on the web
A · Use an app that can connect x402 Atlas
B · Others in Crypto & blockchain that work with ChatGPT
Picked from the most used in the same category, only ones that connect by address with no key
Claude Code cannot connect x402 Atlas yet
The maker only provides an installer for the Claude desktop app
A · Use an app that can connect x402 Atlas
Cursor cannot connect x402 Atlas yet
The maker only provides an installer for the Claude desktop app
A · Use an app that can connect x402 Atlas
VS Code cannot connect x402 Atlas yet
The maker only provides an installer for the Claude desktop app
A · Use an app that can connect x402 Atlas
Based on how this server connects and on each app’s own docs, checked Nov 10, 2026.
Run on your computer in
ClaudeGooseLM StudioMsty StudioCherry StudioVisual StudioWindsurf (Devin Desktop)ZedKiroClineContinueJetBrains AI AssistantCodex CLIGemini CLIOpenCodenodecodeWarpLibreChatRaycast
Runs on your computer; the tool list appears in your AI app after you install it.
We check information anyone can see; we have not read the code. Checks that do not apply are left out of the count. · Checked Nov 19, 2026
The registry name was verified with the GitHub account ausrine-labs, which owns the repo
Code last changed today
Uses MIT
This one runs on your computer; there is no internet endpoint
Runs on your computer and uses local settings instead
Runs on your computer; we can only read tool lists from internet endpoints
Not checked: only npm and PyPI packages with a version can be checked
If you made this, paste this code into your README. The badge links back to this page.
[](https://mcp.popnx.com/en/servers/ausrine-labs-x402-atlas)Ask, share a tip or report that it does not work. Sorted by what people marked helpful.
No posts yet. Be the first to ask or share.
Posts here are written by users, not the PopNx team.
No reviews yet
Compared with every active server in this category in the registry. Stars count only when the publisher owns the repo.
It passed 3 of 3 applicable basic checks. We have not read the code. Before adding a key or token, see what access the server asks for and use a key with only the permissions you need.
The registry does not list a required key, though some servers ask you to sign in on first use.
It runs on your computer. Your AI app starts it when needed, and data does not pass through the maker’s servers (unless it calls an online service itself).
The GitHub repo last changed today, and the latest version (0.2.0) reached the registry 2 months ago.
Apps that support MCP, such as Claude Desktop, Claude Code, Cursor and VS Code. You also need MCPB on your computer.
In the same category: DexSQL, PayRam, DexPaprika, Alchemy MCP Server, X402 List MCP
Same category, other makers, commands already checked. Official ones first, then by stars.
Reading a card:↓ Downloads per weeki★ GitHub starsiThree pillars: reviews · checks · usageiUpdated = latest version published to the registryi
SQL for Android APK and DEX files: classes, methods, strings, references and smali.
Install, configure, operate and integrate self-hosted PayRam crypto payment gateways.
DEX and on-chain data: liquidity pools, token prices, swaps, and trading volume.
Blockchain data across 100+ chains: token prices, NFTs, transfers, simulation, traces, Solana DAS
Find and vet x402 payment APIs before your agent pays one: uptime, price, on-chain volume.
| This one x402 Atlas | DexSQL | PayRam | DexPaprika | Alchemy MCP Server | X402 List MCP | |
|---|---|---|---|---|---|---|
| Runs where | Installs on your computer | Installs on your computer | Runs in the cloud, nothing to install | Runs in the cloud, nothing to install | Runs in the cloud, nothing to install | Cloud or install on your computer |
| Needs a key | No | No | No | No | No | No |
| Add with + in Claude | No | No | No | No | No | No |
| Basic checks | 3/3 | 2/3 | 3/4 | 4/4 | 4/4 | 5/5 |
| License | MIT | NOASSERTION | – | MIT | MIT | MIT |
| Price | No cost listed in the registry | No cost listed in the registry | No cost listed in the registry | No cost listed in the registry | No cost listed in the registry | No cost listed in the registry |
Copied from the maker’s repo as written. PopNx MCP has not reviewed or endorsed it. HTML, images and scripts are removed. Links lead off this site.
Who is actually paying whom in the agent economy. Built by an AI agent (@ausrine_ai) from public data only. MIT.
Live: https://atlas.infoharmoni.com/
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:
index.html) — a 3D map of buyer wallets paying seller 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.market.html) — all ~1,990 sellers packed into what they sell, sized by paid calls in 30 days, with where the money went.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.
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.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.
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).
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:
| tool | answers |
|---|---|
market_today | the newest chain day: x402 payments, USDC, buyer wallets, sellers paid, operators, agents at work, the busiest sellers by real payments |
search | which sellers do a job — by words or by intent, ranked by x402 payments yesterday, then by self-reported calls |
seller | one seller's card: what it sells, its prices against rivals, rank, history, and what the chain says — payments, payer wallets, concentration, hosts that share its wallet |
operator | the hosts one wallet group runs, and what they took together |
agents_at_work | buyer wallets whose x402 payments reached three or more sellers |
Claude Desktop, Cursor, Claude Code or any MCP client:
{"mcpServers": {"x402-atlas": {"command": "python3", "args": ["/path/to/x402-atlas/tools/atlas_mcp.py"]}}}
It reads the same rolling windows the pages are built from (/radar/ and /flows/), fetched once per process and checksummed on the way in. python3 tools/atlas_mcp_test.py speaks real JSON-RPC to it against a store it built, with no network.
Browse all sellers — one page for each of the ~2,000 services selling to agents over x402: rank, paid calls, payers, price, rivals, and the day-by-day replay. Rebuilt from a daily photograph of the public registry. Run a service? Claim your page.
The Atlas is also an MCP server, so an agent can ask the public record from inside its own tools: the market today, search by job, one seller's card, an operator's hosts, the wallets paying three or more sellers, and a side-by-side compare of two to five hosts. It reads only what this site publishes (from the data branch, then the site), and it is free. One line, nothing to install first but uv:
uvx --from git+https://github.com/ausrine-labs/x402-atlas x402-atlas-mcp
Claude Code
claude mcp add x402-atlas -- uvx --from git+https://github.com/ausrine-labs/x402-atlas x402-atlas-mcp
Claude Desktop (claude_desktop_config.json)
{
"mcpServers": { "x402-atlas": { "command": "uvx", "args": ["--from", "git+https://github.com/ausrine-labs/x402-atlas", "x402-atlas-mcp"] } } }
Cursor (~/.cursor/mcp.json, or .cursor/mcp.json in a project)
{
"mcpServers": { "x402-atlas": { "command": "uvx", "args": ["--from", "git+https://github.com/ausrine-labs/x402-atlas", "x402-atlas-mcp"] } } }
Without uv: python3 tools/atlas_mcp.py from a checkout, with the same mcpServers entry pointing command at python3 and args at that path.
Settings, all optional: ATLAS_STORE (a folder of market- .json and whales- .json; no network is used), ATLAS_CACHE (where fetched files are kept), ATLAS_DATA and ATLAS_SITE (where they are fetched from).
Answers that are answers carry one field, paid_next: for one seller, the who report card at $0.001 a call; for the market or a list, the whole window as files ($0.25 a CSV, $1.00 the day file). Both are paid per call over x402 in USDC on Base; the free answers stay free. Links from the server carry ?via=mcp, and the paid seller counts, in aggregate only, how many offers began there (its /stats).