DexSQL
SQL for Android APK and DEX files: classes, methods, strings, references and smali.
Ethereum mainnet JSON-RPC paid per call in USDC on Base. No account, no API key: the wallet pays.
Lists are ordered by a usage score (out of 100) built from these parts
| Popularity | 4/80 | GitHub stars or weekly downloads: the larger counts 60, the smaller 20 |
|---|---|---|
| Freshness | 7/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 | 11/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.
Claude cannot connect x402 Ethereum RPC yet
The maker has not listed install details in the MCP Registry yet
ChatGPT cannot connect x402 Ethereum RPC yet
The maker has not listed install details in the MCP Registry yet
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 Ethereum RPC yet
The maker has not listed install details in the MCP Registry yet
Cursor cannot connect x402 Ethereum RPC yet
The maker has not listed install details in the MCP Registry yet
VS Code cannot connect x402 Ethereum RPC yet
The maker has not listed install details in the MCP Registry yet
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 ffboers, which owns the repo
Code last changed 3 months ago
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
If you made this, paste this code into your README. The badge links back to this page.
[](https://mcp.popnx.com/en/servers/ffboers-x402-rpc-gateway)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 3 months ago, and the latest version (1.0.0) reached the registry 3 months ago.
Apps that support MCP, such as Claude Desktop, Claude Code, Cursor and VS Code.
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 Ethereum RPC | 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.
A Cloudflare Worker that sells JSON-RPC access to your own Ethereum node, one request at a time, over x402. No accounts, no API keys, no invoices: a caller signs a USDC authorization on Base and gets the answer in the same exchange.
Running in production at 402rpc.com.
Selling RPC access normally means building signup, billing, key rotation and rate plans before you serve a single request. x402 removes all of it — but a naive gateway that simply charges per call creates two new problems, and this template solves both.
Callers must never pay for an answer you cannot give. Every request is checked *before* the paywall. A blocked namespace, a block below your history floor, a log range that is too wide — all return HTTP 400, and x402 does not settle on a response of 400 or higher. Node failures return 502 for the same reason.
Flat pricing loses money. eth_getLogs across ten thousand blocks costs your node hundreds of times more than eth_blockNumber. Prices here scale with the work a method actually costs.
Your node's own refusals arrive as HTTP 200. A node that says "no state available at that block" or "too many logs in one response" returns a JSON-RPC error with a 200 status — and x402 settles on a 200. Left alone, your customers pay for answers you could not give. This template translates that class of error into a 4xx so nothing settles. Errors that are a real answer, execution reverted for instance, stay chargeable.
Accept headernpm install
cp wrangler.jsonc.example wrangler.jsonc # edit the vars npx wrangler deploy
At minimum, set PAY_TO_ADDRESS, ORIGIN_URL and PUBLIC_URL. Everything else has a working default.
For a mainnet network you need Coinbase CDP credentials — the public x402.org facilitator serves testnets only:
npx wrangler secret put CDP_API_KEY_ID
npx wrangler secret put CDP_API_KEY_SECRET
Without them the Worker deliberately answers 503 rather than issuing payment challenges it cannot settle.
The facilitator has an undocumented floor. Amounts around $0.0002 are rejected with amount_too_low; $0.001 goes through. Price differentiation therefore only works upward from roughly a tenth of a cent.
The Bazaar only indexes x402 version 2. Every one of the twenty resources I checked runs v2; none run v1. If you build on the v1 packages (x402-hono, x402-fetch — last published April 2026) your service works but is invisible to the discovery layer agents actually query. This template uses v2 throughout.
Pin `resource` to your public URL. Left to derive it from the request, the middleware puts your Worker's internal hostname — which contains your Cloudflare account name — into every payment challenge, right next to your receiving address.
Everything this template puts in your payment terms and landing page is a promise to a paying stranger. Test them against what your node actually does, not against what you believe it does. Three that bit us:
nodeRefusal in policy.ts.Ranking in the Bazaar is driven by measured usage — l30DaysTotalCalls and l30DaysUniquePayers — not by how well you write your description. Worth knowing before you spend an afternoon on copy.
Worth knowing too: as of August 2026 the entire visible Bazaar handled roughly 1,200 paid calls in thirty days across eighty services. The busiest Ethereum RPC among them served fourteen. Build for the market this becomes, not the one it is.
What this template does for you anyway: a bazaar discovery extension so you are indexed at all, an iconUrl, and payment accepted on Base, Polygon and Arbitrum so more wallets can reach you. What it deliberately does not do is inflate your own call count — that buys a position in a list nobody reads yet, with your own money.
Set ORIGIN_TOKEN as a secret and have your origin require the matching X-Origin-Token header. Without it, anyone who learns your origin hostname uses your node for free and the paywall is decorative. A minimal reference proxy is in examples/origin-proxy.py.
The receiving address is necessarily public: it is in every payment challenge. Your node's IP is also public, because it takes part in the peer-to-peer network. The link between the two is what you protect.
Someone who submits a transaction through your gateway and watches which IP broadcasts it first learns where your service physically runs. Setting RELAY_URLS sends raw transactions out through public endpoints instead, and that trail disappears. Every other method only returns answers and reveals nothing.
Any x402 client pays and retries automatically:
import { wrapFetchWithPayment, x402Client } from "@x402/fetch";
import { ExactEvmScheme } from "@x402/evm";
const x402 = new x402Client().register("eip155:8453", new ExactEvmScheme(account)); const fetchWithPay = wrapFetchWithPayment(fetch, x402); await fetchWithPay("https://your-gateway/rpc", { method: "POST", body });
As a paid fallback behind your own node — see examples/fallback.mjs:
transport: fallback([
http(YOUR_OWN_RPC), http("https://your-gateway/rpc", { fetchFn: fetchWithPay }), ], { retryCount: 0 })
A standby you never use costs nothing. That is the property a subscription cannot offer, and it is the strongest reason to run one of these.
MIT.