原型 · 预览版:收录官方注册中心里的全部服务器,每 30 分钟同步一次。评价和账户功能将在后续阶段推出。
PopNx MCP为使用 AI 的人准备的 MCP 服务器 · 用大白话讲清楚

Interline

作者:Choppaaahh版本 0.1.3i★ –i在你的电脑上运行
注册名称io.github.Choppaaahh/interline

安装

概览

作者提供的说明(英文原文)

Neutral, non-custodial MCP payment router: discover rails, then pay across them.

PopNx MCP 的三大支柱

这三项永远不会合并成一个分数:意见、测量和人气是不同的东西。

它能帮你做什么

我们还没有为它写通俗的介绍。下面是我们从注册中心读取到的事实。

  • 连接方式: 在你的电脑上运行
  • 传输方式: stdio
  • 分类: 网店与支付
  • 你需要填写:APV0_BUYER_PRIVATE_KEY

安装

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

安装之前

  • 基础检查:1 项中通过 1 项
  • 在你的电脑上运行,拥有你的用户账户的权限(文件、网络、应用)。
  • 需要你自己填写: APV0_BUYER_PRIVATE_KEY, APV0_NETWORK

标为机密的值是你账户的钥匙。千万不要分享给别人,也不要粘贴到聊天里。

你需要

  • PyPI已安装 Python 的 uv(用于 uvx 命令)

你用的是哪个应用?

在上方选择你的应用。我们会记住它,下次按钮会显示“安装到 …”。

打开 Claude Desktop → Settings → Developer → Edit Config,把下面的内容粘贴到 claude_desktop_config.json

{
  "mcpServers": {
    "interline": {
      "command": "uvx",
      "args": [
        "interline"
      ],
      "env": {
        "APV0_BUYER_PRIVATE_KEY": "your-value",
        "APV0_NETWORK": "your-value"
      }
    }
  }
}

在终端中运行这条命令

claude mcp add interline --env APV0_BUYER_PRIVATE_KEY=your-value --env APV0_NETWORK=your-value -- uvx interline

运行前请先填写空着的值。

在 Cursor 中打开

或者自己复制设置

粘贴到项目中的 .cursor/mcp.json,或 ~/.cursor/mcp.json

{
  "mcpServers": {
    "interline": {
      "command": "uvx",
      "args": [
        "interline"
      ],
      "env": {
        "APV0_BUYER_PRIVATE_KEY": "your-value",
        "APV0_NETWORK": "your-value"
      }
    }
  }
}

浏览器会先询问是否打开应用,然后应用会显示设置并请你确认。密钥的值会留空,由你自己填写。

在 VS Code 中打开

或者自己复制设置

粘贴到项目中的 .vscode/mcp.json

{
  "servers": {
    "interline": {
      "type": "stdio",
      "command": "uvx",
      "args": [
        "interline"
      ],
      "env": {
        "APV0_BUYER_PRIVATE_KEY": "your-value",
        "APV0_NETWORK": "your-value"
      }
    }
  }
}

浏览器会先询问是否打开应用,然后应用会显示设置并请你确认。密钥的值会留空,由你自己填写。

这个服务器在你的电脑上运行,而 ChatGPT 只能连接互联网上的服务器。请选择其他应用。

你的选择通过 Cookie 保存在这台设备上,无需账户。

需要你填写的值

  • APV0_BUYER_PRIVATE_KEY 机密 env
    Your own wallet private key (0x...). Stays in your env; the server never holds funds. Required only for pay_for_resource, not for discovery.
  • APV0_NETWORK env
    base-sepolia (testnet) or base (mainnet). Default base-sepolia.

这些设置是根据作者在注册中心的条目生成的。如果 README 的写法不同,请以 README 为准。

它能做什么

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

基础检查i

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

  • ✓ 通过

    作者与仓库一致

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

  • … 尚未检查

    仍在维护

    我们还没有从 GitHub 读取这个仓库

  • … 尚未检查

    有许可证

    我们还没有从 GitHub 读取这个仓库

  • – 不适用

    端点有响应

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

  • – 不适用

    使用 OAuth 登录

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

  • … 尚未检查

    工具描述中没有隐藏指令

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

与“网店与支付”中的其他服务器比较i

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

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

常见问题

Interline 安全吗?

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

它需要哪些密钥或代码?

你需要填写:APV0_BUYER_PRIVATE_KEY

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

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

它还在维护吗?

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

哪些应用可以使用它?

支持 MCP 的应用,例如 Claude Desktop、Claude Code、Cursor 和 VS Code。你的电脑上还需要有 Python (uv)。

有什么可以替代它?

同一分类中有:Spree Commerce: open-source B2B and marketplace ecommerce, Stripe MCP, MCP Cn Commerce

替代选择

同一分类中其他作者的服务器,按星标数排序。

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

Stripe MCP

作者:stripe

MCP server integrating with Stripe - tools for customers, products, payments, and more.

在云端运行★ 2,043MIT12个月前更新
安装

MCP Cn Commerce

作者:TonyWang-hub

8 read-only MCP platform entries; support is operation-specific; merchant live acceptance pending

在你的电脑上运行★ 96MIT27天前更新
安装

作者的 README

打开 README

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

Interline — agent-to-agent payment router

Archived (2026-10-10). Interline is no longer maintained. The code stays here for reference; nothing is being developed, and the testnet demos are not monitored.

An agent-to-agent payment router: one agent does work, another agent pays for it, no human keys a card. Interline is a neutral, non-custodial router over the fragmented agent-payment-rail stack — *"OpenRouter for agent payments."* Built on x402 (HTTP-402 micropayments, USDC), aggregator-shaped so adding a rail is one adapter, not a rewrite.

Today it routes payments across three live rails — x402 USDC on EVM (Base Sepolia) and on Solana (devnet), plus MPP on Tempo (Moderato testnet) — all behind one Paywall.gate() call. Real on-chain agent-to-agent settles are confirmed on all three. It ships an MCP router so agents can discover + pay endpoints, and includes a Google-AP2 inbound adapter — a signed AP2 mandate (verified, constraint-checked + freshness-gated) settles non-custodially on the rails.

Run the demo (no wallet, no faucet, no risk)

python3 -m venv .venv && source .venv/bin/activate

pip install -r requirements.txt python3 run_demo.py

Expected: DEMO PASS — agent paid agent, settlement receipt issued.

What just happened (the x402 "exact-evm" loop):

buyer GET /work

-> seller 402 + PaymentRequirements {amount, asset=USDC, payTo, network} -> buyer signs an EIP-3009 transferWithAuthorization (gasless USDC auth) -> buyer retries with X-PAYMENT header (base64 signed payload) -> facilitator VERIFIES the signature (real signer-recovery) + checks policy -> facilitator SETTLES (mock: fake tx hash; live: on-chain USDC transfer) -> seller 200 + work product + X-PAYMENT-RESPONSE receipt (tx hash)

The facilitator's verify step is real cryptography even in mock mode — it recovers the EIP-712 signer and matches it to the authorization. Only the on-chain broadcast is mocked. So a passing demo proves the buyer's signing is protocol-correct against real USDC.

Files

filerole
router/paywall.pythe reusable Paywall primitive — gate any endpoint behind x402 in one .gate() call
router/ledger.pysettlement receipt-ledger → logs/agent_payment_settlements.jsonl (audit trail)
router/seller.pyFastAPI agent that sells work — defines the requirements + work, wires one Paywall.gate()
router/buyer.pyagent that auto-pays 402s (pay_and_get) with a client-side spend limit
router/eip3009.pythe one crypto-subtle file: EIP-3009 typed-data, shared by buyer+facilitator so they can't drift
router/facilitator_mock.pyin-process verify+settle (real sig check, mock chain) — the dry-run rail
router/facilitator_real.pylive x402 facilitator over HTTP via the x402 SDK's own client; get_facilitator() picks mock↔real by config
router/config.pynetwork/asset facts + .env loader; mock↔testnet↔mainnet is a one-line env change
run_demo.pyend-to-end smoke (ephemeral keys, mock facilitator)
run_live.pylive runner — settles a real x402 payment on Base Sepolia

Go live (Base Sepolia testnet)

  1. Two testnet wallets (buyer signs, seller receives):
   python3 -c "from eth_account import Account; a=Account.create(); print('addr', a.address); print('key', a.key.hex())"

Do this twice. Keep the keys out of git (use .env).

  1. Fund the buyer with Base Sepolia testnet USDC (Circle faucet) + a little testnet ETH for any gas the facilitator relays.
  2. `.env` (copy .env.example → .env, it's gitignored + auto-loaded):
   APV0_NETWORK=base-sepolia

APV0_BUYER_PRIVATE_KEY=0x... # buyer testnet key (signs) APV0_SELLER_ADDRESS=0x... # seller address (receives) APV0_FACILITATOR_URL=https://x402.org/facilitator

4. **Run it live:**
   python3 run_live.py

The seller now uses RealFacilitator (the x402 SDK's own facilitator client), the buyer auto-pays the 402, and x402.org broadcasts the EIP-3009 USDC transfer on-chain. You get a real tx hash → https://sepolia.basescan.org/tx/ .

Gasless: with EIP-3009 the facilitator relays gas, so the buyer only needs

testnet USDC, not ETH.

Gate your own endpoint (the product primitive)

from router.paywall import Paywall

from router.facilitator_real import get_facilitator

paywall = Paywall(get_facilitator(), my_requirements_fn) # mock ↔ real by env

@app.get("/my-endpoint") def my_endpoint(request: Request): return paywall.gate(request, lambda: do_expensive_work())

That one .gate() call handles the whole x402 V2 dance — 402 challenge → verify → settle → record receipt → deliver — and appends every settlement to the receipt-ledger. The deployer never touches the protocol or holds a key.

v1 dogfood — pay an agent, get REAL work back

v0 proved the *payment*. v1 proves the *loop*: a buyer agent pays → a seller agent does real inference → returns the result + a settlement receipt. The seller's _do_the_work(task) is the product's integration point (plug in your own model/compute/service).

APV0_OPENROUTER_KEY=sk-or-... python3 run_v1_dogfood.py "your task here"

→ V1 DOGFOOD PASS — agent paid agent for real work ✅ (mock payment + real model call by default; set APV0_NETWORK=base-sepolia for a real on-chain settle under the same loop). Without a key it returns a stub so the product still runs.

This is the authentic loop: an agent doing real work, metered + paid-for over x402 — the same primitive whether the work is a model call, a compute job, or any other billable agent task.

问 PopNx