Agenticpay runs on your own machine — the client starts it, so there is no endpoint to ping. 242 installs a week from npm. Last commit 24 Sep 2026.
x402 USDC paywall bridge for MCP — pay per tool call on Solana.
Every tool that appeared, vanished or quietly changed what it asks for. Recorded since 18 August 2026. No other catalogue keeps this.
We read the source, 6 d ago · rules 995398eba69f
What this server is able to do. For an MCP server this is often the job itself — a terminal server runs commands because that is what it is for. Listed so you know what you are plugging in, not as an accusation.
пакет @agenticpay/mcp-bridge ссылается на krystiangw/agenticpay
Is this your server and something here is wrong? Tell us — corrections are free and do not require a plan.
We found places where it runs commands, builds paths or queries from values it is given. None of that is a flaw by itself — it becomes one when the code changes, and code changes quietly between releases. We re-read it on every one.
This server runs on your own machine — install it with the package manager and the client starts it for you. Package name taken from the official registry entry.
claude mcp add agenticpay -e 'AGENTICPAY_BRIDGE_KEYPAIR=<AGENTICPAY_BRIDGE_KEYPAIR>' -e 'AGENTICPAY_BRIDGE_TOOLS=<AGENTICPAY_BRIDGE_TOOLS>' -- npx -y @agenticpay/mcp-bridge
{
"mcpServers": {
"agenticpay": {
"command": "npx",
"args": [
"-y",
"@agenticpay/mcp-bridge"
],
"env": {
"AGENTICPAY_BRIDGE_KEYPAIR": "<AGENTICPAY_BRIDGE_KEYPAIR>",
"AGENTICPAY_BRIDGE_TOOLS": "<AGENTICPAY_BRIDGE_TOOLS>"
}
}
}
}
[mcp_servers.agenticpay]
command = "npx"
args = ["-y", "@agenticpay/mcp-bridge"]
env = { AGENTICPAY_BRIDGE_KEYPAIR = "<AGENTICPAY_BRIDGE_KEYPAIR>", AGENTICPAY_BRIDGE_TOOLS = "<AGENTICPAY_BRIDGE_TOOLS>" }
{
"mcpServers": {
"agenticpay": {
"command": "npx",
"args": [
"-y",
"@agenticpay/mcp-bridge"
],
"env": {
"AGENTICPAY_BRIDGE_KEYPAIR": "<AGENTICPAY_BRIDGE_KEYPAIR>",
"AGENTICPAY_BRIDGE_TOOLS": "<AGENTICPAY_BRIDGE_TOOLS>"
}
}
}
}
{
"servers": {
"agenticpay": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"@agenticpay/mcp-bridge"
],
"env": {
"AGENTICPAY_BRIDGE_KEYPAIR": "<AGENTICPAY_BRIDGE_KEYPAIR>",
"AGENTICPAY_BRIDGE_TOOLS": "<AGENTICPAY_BRIDGE_TOOLS>"
}
}
}
}
Put your own values in place of
<AGENTICPAY_BRIDGE_KEYPAIR> (Solana keypair as 64-byte JSON array (the format `solana-keygen new` writes). The bridge signs each x402 payment with this keypair), <AGENTICPAY_BRIDGE_TOOLS> (JSON array of paid tool definitions. Each entry: { name, description, url, inputSchema, headers? }).
The author’s registry entry marks them as required.
Optional settings from the registry entry, left out of the block above:
AGENTICPAY_BRIDGE_NETWORK (CAIP-2 network identifier. Devnet: solana:EtWTRABZaYq6iMfeYKouRu166VU2xqa1), AGENTICPAY_BRIDGE_RPC (Solana JSON-RPC URL).
Pay-per-call intel bridge for AI agents — 18 tools; tolled lanes $0.02 USDC via x402
MCP server for Token Verdict — pay-per-call token risk verdicts over x402 ($0.02 USDC on Base)
Solana agent tools, x402 USDC pay-per-call (Cloudflare host).
Pay-per-call research tools for AI agents, paid via x402 USDC. Remote MCP, one free tool.
Multi-chain wallet MCP. 18 tools: balance, swap, bridge, stake, claim. Pay-per-call USDC (x402 v2).
5 pay-per-call SEO tools over MCP. Free discovery, tool calls settle in USDC on Base via x402.
MCP server for the @agentutility agentops cluster — pay-per-call x402 tools, no API keys, USDC on…
MCP bridge for autonomous x402 payments in HPP USDC.e — discover and pay for services per call.
Answers built from our own checks of this server.