Open-source B2B and marketplace ecommerce; new stores include an MCP server for AI agents.
Agentpay
Overview
Description from the maker (original English)
AI Agent payment protocol on CKB Fiber Network. Zero-gas micropayments with Hold Invoice escrow.
PopNx MCP’s three pillars
These three are never merged into one score: opinions, measurements and popularity are different things.
- User voiceiNo reviews yetReviews open together with accounts in a later step
- Our basic checksi1 of 1 passedChecked from public information; code not scanned yet
- UsageiNot measured yet★ –
What you can do with it
We have not written a plain-language summary for this one yet. Below are the facts we read from the registry.
- Connection: Runs on your computer
- Transport: stdio
- Category: Online shops & payments
- You need to fill in: FIBER_RPC_URL
Install
Pick the AI app you use, then copy the settings.
Before you install
- Basic checks: 1 of 1 passed
- Runs on your computer with your user’s permissions (files, network, apps).
- You fill in yourself:
FIBER_RPC_URL
You need
- npmNode.js installed (for the npx command)
Which app do you use?
Pick your app above. We remember it, so next time the button says “Install in …”.
Open Claude Desktop → Settings → Developer → Edit Config, and paste this into claude_desktop_config.json
{
"mcpServers": {
"agentpay": {
"command": "npx",
"args": [
"-y",
"@agentpay-dev/mcp-server"
],
"env": {
"FIBER_RPC_URL": "your-value"
}
}
}
}Run this in your terminal
claude mcp add agentpay --env FIBER_RPC_URL=your-value -- npx -y @agentpay-dev/mcp-serverFill in the empty values before running it.
Or copy the settings yourself
Paste into .cursor/mcp.json in your project, or ~/.cursor/mcp.json
{
"mcpServers": {
"agentpay": {
"command": "npx",
"args": [
"-y",
"@agentpay-dev/mcp-server"
],
"env": {
"FIBER_RPC_URL": "your-value"
}
}
}
}Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.
Or copy the settings yourself
Paste into .vscode/mcp.json in your project
{
"servers": {
"agentpay": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"@agentpay-dev/mcp-server"
],
"env": {
"FIBER_RPC_URL": "your-value"
}
}
}
}Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.
This one runs on your computer, and ChatGPT can only connect to servers on the internet. Pick another app.
Your choice stays on this device in a cookie; no account needed.
Values you fill in
- Fiber Network RPC URL
These settings are generated from the maker’s registry entry. If the README says otherwise, follow the README.
What it can do
Runs on your computer; the tool list appears in your AI app after you install it.
Basic checksi
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 8, 2026
- ✓ Pass
Maker matches the repo
The registry name was verified with the GitHub account alefnt, which owns the repo
- … Not checked yet
Still maintained
We have not read this repo from GitHub yet
- … Not checked yet
Has a licence
We have not read this repo from GitHub yet
- – Not applicable
Endpoint responds
This one runs on your computer; there is no internet endpoint
- – Not applicable
Sign-in with OAuth
Runs on your computer and uses local settings instead
- … Not checked yet
No hidden instructions in tool descriptions
Runs on your computer; we can only read tool lists from internet endpoints
Compared with others in Online shops & paymentsi
- More stars than 0% of the other 2546 servers in this category
- Published to the registry more recently than 3% of the other 2546 servers in this category
- Basic checks equal to or better than 100% of the other 2546 servers in this category
Compared with every active server in this category in the registry. Stars count only when the publisher owns the repo.
Common questions
Is Agentpay safe?
It passed 1 of 1 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.
What keys or codes does it need?
You need to fill in: FIBER_RPC_URL
Does it run on my computer or in the cloud?
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).
Is it still maintained?
The GitHub repo last changed –, and the latest version (0.1.1) reached the registry 8 months ago.
Which apps can use it?
Apps that support MCP, such as Claude Desktop, Claude Code, Cursor and VS Code. You also need Node.js on your computer.
What can I use instead?
In the same category: Spree Commerce: open-source B2B and marketplace ecommerce, Stripe MCP, MCP Cn Commerce
Alternatives
Servers in the same category from other makers, sorted by stars.
Reading a card:★ GitHub starsiThree pillars: reviews · checks · usageiUpdated = latest version published to the registryi
Stripe MCP
Stripe’s official server lets AI view and manage customers, products, payments and invoices. Connect to Stripe’s cloud and sign in with OAuth.
MCP Cn Commerce
8 read-only MCP platform entries; support is operation-specific; merchant live acceptance pending
README from the maker
Open the README
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.
AgentPay - BTC-Native AI Agent Payment Protocol
Give every AI Agent a wallet. Let Agents pay each other - instantly, with zero fees.
AgentPay is a BTC-native payment protocol designed for AI Agent economies. Built on CKB Fiber Network (Lightning-compatible L2), it enables:
- Zero-gas micropayments - Pay per API call, no minimum amount
- Hold Invoice escrow - Lock funds until service delivery is confirmed
- BTC interoperability - Cross-chain payments via Lightning Network
- MCP integration - Let Claude/GPT agents make payments natively
Quick Start
Install
npm install @agentpay-dev/sdk @agentpay-dev/core
Create a Payment Agent
import { AgentWallet } from '@agentpay-dev/sdk';
const wallet = new AgentWallet({ fiberRpcUrl: process.env.FIBER_RPC_URL });
// Pay another agent for a service const result = await wallet.payAndCall( 'https://translator-agent.example.com', 'translate', { text: 'Hello World', target: 'zh' } );
Scaffold a New Project
npx create-agentpay my-agent
cd my-agent && npm install
Architecture
+-----------------------------------------------------+
| Applications | | AI Agents | DePIN Devices | API Marketplaces | +-----------------------------------------------------+ | AgentPay SDK | | AgentWallet | ServiceProvider | HubClient | +-----------------------------------------------------+ | AgentPay Core | | Settlement | Metering | DID | Assets | +-----------------------------------------------------+ | CKB Fiber Network (L2) | | Payment Channels | Hold Invoice | HTLC Routing | +-----------------------------------------------------+ | CKB L1 + BTC Lightning Network | | xUDT Assets | RGB++ | Cross-chain (Cch) | +-----------------------------------------------------+
Packages
| Package | npm | Description |
|---|---|---|
@agentpay-dev/core | Protocol core: Fiber RPC, settlement, assets, DePIN metering | |
@agentpay-dev/sdk | Developer SDK: AgentWallet, ServiceProvider, HubClient | |
@agentpay-dev/mcp-server | MCP Server: 8 payment tools for Claude/GPT | |
@agentpay-dev/x402-facilitator | HTTP 402 payment middleware with Fiber settlement | |
@agentpay-dev/ap2 | Google AP2 protocol bridge to Fiber | |
create-agentpay | CLI scaffolding tool |
Key Features
Hold Invoice - Trustless Escrow
The killer feature. Agent A locks payment, Agent B delivers, funds release only on confirmation:
import { ServiceProvider } from '@agentpay-dev/sdk';
const provider = new ServiceProvider({ fiberRpcUrl: process.env.FIBER_RPC_URL, services: { translate: { price: 100_000_000n, // 1 CKB per request handler: async (params) => { const result = await doTranslation(params.text, params.target); return { translation: result }; } } } });
// Hold flow: Lock -> Deliver -> Release (atomic) // If service fails, funds auto-refund via HTLC timeout
MCP Server - AI-Native Payments
Registered on the official MCP Registry as io.github.alefnt/agentpay.
Add to Claude Desktop config:
{
"mcpServers": { "agentpay": { "command": "npx", "args": ["@agentpay-dev/mcp-server"], "env": { "FIBER_RPC_URL": "http://localhost:8227" } } } }
8 MCP Tools:
| Tool | Description |
|---|---|
get_balance | Check wallet balance (CKB + xUDT) |
send_payment | Send a payment via Fiber invoice |
create_invoice | Generate a Fiber invoice to receive payment |
pay_for_service | Pay-and-call another agent's API |
create_hold_invoice | Create escrow payment (lock funds) |
settle_hold | Release held funds after service delivery |
cancel_hold | Cancel and refund held payment |
list_channels | View active payment channels |
x402 HTTP Compatibility
Any HTTP API becomes a paid API with one middleware:
import { createX402Middleware } from '@agentpay-dev/x402-facilitator';
const paywall = createX402Middleware({ price: '100000000' });
http.createServer((req, res) => { paywall(req, res, () => { res.end(JSON.stringify({ data: 'premium content' })); }); }); // Client: HTTP 402 -> pay Fiber invoice -> retry -> get content
BTC Cross-Chain
Pay with BTC, settle on CKB via Lightning-Fiber bridge:
import { CchClient } from '@agentpay-dev/core';
const cch = new CchClient({ cchRpcUrl: process.env.CCH_RPC_URL });
await cch.sendBtcToCkb({ btcPayReq: 'lnbc100n1p...', fiberChannelId: '0x...', });
Ecosystem Integration
AgentPay enhances existing payment solutions:
| Platform | How AgentPay Helps |
|---|---|
| x402 (Coinbase) | Zero-gas Fiber settlement backend for HTTP 402 protocol |
| AP2 (Google) | Settlement layer for agent authorization framework |
| Stripe | Complements with agent-to-agent micropayments (sub-cent) |
| Lightning Network | Cross-chain via Cch bridge, expanding BTC payment reach |
Project Structure
AgentPay/
packages/ core/ # Protocol core (Fiber RPC, settlement, DePIN) sdk/ # Developer SDK (Wallet, Provider, Hub) mcp-server/ # MCP Server for AI agents x402-facilitator/ # HTTP 402 middleware ap2/ # Google AP2 bridge create-agentpay/ # CLI scaffolding services/ hub/ # Hosted wallet service registry/ # Agent discovery service examples/ translate-agent/ # Translation service example code-review-agent/ # Code review agent example btc-to-ckb/ # Cross-chain payment example docs/ product.md # Product overview architecture.md # Technical architecture
Documentation
- Product Overview - What AgentPay solves and how
- Architecture - Technical design and protocol layers
- Competitive Analysis - Comparison with x402, AP2, Stripe
Tech Stack
- Runtime: Node.js 20+ / TypeScript 5.5+
- L2 Network: CKB Fiber Network (Lightning-compatible)
- L1 Blockchain: Nervos CKB
- Asset Standard: xUDT (extensible User Defined Token)
- Identity: .bit decentralized identity
- Cross-chain: Cch (CKB - BTC Lightning bridge)
- AI Integration: Model Context Protocol (MCP)
- Build: pnpm workspace monorepo
Development
git clone https://github.com/alefnt/AgentPay.git
cd AgentPay pnpm install pnpm build pnpm test
Roadmap
- Core protocol (Fiber RPC, settlement, assets)
- SDK (AgentWallet, ServiceProvider, HubClient)
- MCP Server with 8 payment tools
- x402 HTTP 402 facilitator
- AP2 protocol bridge
- DePIN metering module
- BTC cross-chain (Cch + LND)
- RGB++ bridge integration
- npm packages published
- MCP Registry registration
- Fiber mainnet deployment
- Stablecoin (RUSD) support on CKB
- Public demo site
- Production Hub service
License
MIT - see LICENSE for details.
Built for the Agent Economy - where AI agents autonomously discover, negotiate, and pay for services.