原型 · 预览版:收录官方注册中心里的全部服务器,每 30 分钟同步一次。使用 Google 登录即可撰写评价。原型 · 每 30 分钟更新
PopNx MCP为使用 AI 的人准备的 MCP 服务器 · 用大白话讲清楚

x402 Ethereum RPC

注册名称io.github.ffboers/x402-rpc-gateway

安装方法

What it does

Ethereum mainnet JSON-RPC paid per call in USDC on Base. No account, no API key: the wallet pays.

  • Connects –
  • Account or key No key needed
  • Category 加密货币与区块链

为什么排在这里

列表按使用分(满分 100)排序,由以下部分组成

热度4/80GitHub 星标或每周下载量:较大的计 60,较小的计 20
新鲜度7/1230 天内有发布或代码更新得满分
仍在响应0/8上次检查时云端端点有响应
使用分11/100

质量: 基础检查通过 3/3 项(仅展示,不用于排序) · 上升势头: 暂无数据 (只用于“上升中”标签)

安装

选择你使用的 AI 应用,然后复制设置。

通过 3/3 项检查 · 在你的电脑上运行

第一步:你用哪个 AI?

选择你用的应用,步骤会显示在下方。

Claude 暂时无法连接 x402 Ethereum RPC

开发者尚未在 MCP 注册表中填写安装方式

ChatGPT 暂时无法连接 x402 Ethereum RPC

开发者尚未在 MCP 注册表中填写安装方式

你可以改用这些方式

B · 加密货币与区块链 类中能连接 ChatGPT 的其他服务器

从同类中使用较多的里挑选,仅限用地址即可连接、无需密钥的

Claude Code 暂时无法连接 x402 Ethereum RPC

开发者尚未在 MCP 注册表中填写安装方式

Cursor 暂时无法连接 x402 Ethereum RPC

开发者尚未在 MCP 注册表中填写安装方式

VS Code 暂时无法连接 x402 Ethereum RPC

开发者尚未在 MCP 注册表中填写安装方式

其他支持 MCP 的应用(如 Windsurf、Zed、Gemini CLI)添加方式各不相同,请在应用列表中查看

查看所有支持 MCP 的应用 →

JSON 设置在下方“开发者专用”中

卡住了?问问正在用 x402 Ethereum RPC 的人💬 讨论 →

一览

每周下载量i
不在 npm/PyPI 上
连接方式
–
最新版本i
1.0.0
发布到注册中心i
2026年8月29日
代码最后更新i
2026年8月29日
作者
ffboers
注册状态
活跃

它能做什么

它在你的电脑上运行;安装后,工具列表会显示在你的 AI 应用中。

基础检查i

我们检查的是任何人都能看到的信息;我们没有阅读代码。不适用的检查项不计入总数。 · 检查于 2026年11月19日

  • ✓ 通过

    作者与仓库一致

    注册名称已通过 GitHub 账户 ffboers 验证,该账户拥有此仓库

  • ✓ 通过

    仍在维护

    代码最后更新于3个月前

  • ✓ 通过

    有许可证

    使用 MIT

  • – 不适用

    端点有响应

    它在你的电脑上运行,没有互联网端点

  • – 不适用

    使用 OAuth 登录

    在你的电脑上运行,改用本地设置

  • … 尚未检查

    工具描述中没有隐藏指令

    它在你的电脑上运行;我们只能读取互联网端点的工具列表

我们检查什么 → · JSON

作者:申请重新检查或报告信息错误
给作者:在 README 中加徽章

如果你是作者,可把这段代码贴到 README。徽章会链接回本页。

[![Featured on PopNx MCP](https://mcp.popnx.com/badge/ffboers-x402-rpc-gateway.svg)](https://mcp.popnx.com/en/servers/ffboers-x402-rpc-gateway)

讨论

提问、分享技巧或报告无法使用。按“有帮助”数量排序。

还没有帖子,欢迎第一个提问或分享。

此处内容由用户撰写,不代表 PopNx 团队。

登录后发帖

用户评价

还没有评价

登录后写评价

与“加密货币与区块链”中的其他服务器比较i

  • 星标数多于此分类中其他 1759 个服务器的 84%
  • 发布到注册中心的时间比此分类中其他 1759 个服务器的 36% 更新
  • 基础检查结果等于或优于此分类中其他 1759 个服务器的 99%

与注册中心里这个分类中所有活跃的服务器比较。只有当发布者拥有该仓库时,星标数才计入。

常见问题

x402 Ethereum RPC 安全吗?

它在 3 项适用的基础检查中通过了 3 项。我们没有阅读代码。在添加密钥或令牌之前,请先看看这个服务器要求哪些权限,并使用只具备所需权限的密钥。

它需要哪些密钥或代码?

注册中心没有列出必需的密钥,不过有些服务器会在首次使用时要求你登录。

它在我的电脑上运行还是在云端?

它在你的电脑上运行。你的 AI 应用会在需要时启动它,数据不会经过作者的服务器(除非它自己调用在线服务)。

它还在维护吗?

GitHub 仓库最后更新于3个月前,最新版本(1.0.0)于3个月前进入注册中心。

哪些应用可以使用它?

支持 MCP 的应用,例如 Claude Desktop、Claude Code、Cursor 和 VS Code。

有什么可以替代它?

同一分类中有:DexSQL, PayRam, DexPaprika, Alchemy MCP Server, X402 List MCP

功能相近的其他选择

同一分类、其他作者、命令已通过检查。官方的排在前面,再按星标排序。

如何看卡片:↓ 每周下载量i★ GitHub 星标i三大支柱:评价 · 检查 · 使用情况i更新 = 最新版本发布到注册中心的时间i

DexSQL

SQL for Android APK and DEX files: classes, methods, strings, references and smali.

作者:LSPosed正在增长★ 32032天前更新

在你的电脑上运行✓ lsposed.org

PayRam

Install, configure, operate and integrate self-hosted PayRam crypto payment gateways.

作者:PayRam正在增长★ 15843天前更新

在云端运行✓ 服务方 · payram.com

DexPaprika

DEX and on-chain data: liquidity pools, token prices, swaps, and trading volume.

作者:coinpaprika正在增长★ 1206天前更新

在云端运行✓ 服务方 · dexpaprika.com

X402 List MCP

Find and vet x402 payment APIs before your agent pays one: uptime, price, on-chain volume.

作者:mcccsm起步阶段↓ 80/周★ 1840天前更新

电脑或云端✓ 服务方 · x402-list.com
与相似项目对比
本项
x402 Ethereum RPC
DexSQLPayRamDexPaprikaAlchemy MCP ServerX402 List MCP
运行位置需要安装在电脑上需要安装在电脑上在云端运行,无需安装在云端运行,无需安装在云端运行,无需安装云端或安装在电脑上都可以
需要密钥否否否否否否
可在 Claude 中按 + 添加否否否否否否
基础检查3/32/33/44/44/45/5
许可证MITNOASSERTION–MITMITMIT
价格登记中未列出费用登记中未列出费用登记中未列出费用登记中未列出费用登记中未列出费用登记中未列出费用

作者的 README

打开 README

按原文从作者的仓库复制。PopNx MCP 没有审查或背书其内容。HTML、图片和脚本已被移除。链接会离开本站。

x402-rpc-gateway

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.

Why this exists

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.

What you get

  • Per-method pricing, configurable, with a ceiling so a batch never surprises anyone
  • A policy layer that refuses before charging, with reasons a caller can act on
  • Raw transactions relayed through public RPCs instead of your own node — see Privacy
  • Discovery metadata so agents can find and use the service without a human
  • A landing page for humans and JSON for machines, chosen by the Accept header
  • An MCP server, so any agent can use it as a tool
  • A fallback example: one line to add your gateway as a paid standby behind a primary

Setup

npm 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.

Three things the documentation will not tell you

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.

Verify your own claims

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:

  • "History from block N onward" — check block N and N-1.
  • "Historical state calls are refused, not charged" — a node's own refusal arrives as HTTP 200, so without translation it settles. See nodeRefusal in policy.ts.
  • "eth_getLogs up to N blocks" — your client has its own cap on logs per response (Nethermind defaults to 20,000), which bites long before your block limit does.

Getting found

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.

Protecting your origin

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.

Privacy

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.

Client usage

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.

Licence

MIT.