English Français العربية

Paid MCP Metering

Official registry Other

Metered MCP tools: free discovery over MCP; per-call execution settled in USDC via x402 v2.

Source code Website Documentation

Install

Add this to your client's MCP configuration (Claude Desktop: claude_desktop_config.json; Cursor: .cursor/mcp.json; VS Code and others use the same "mcpServers" shape).

Remote (streamable-http)
Claude Code 
claude mcp add --transport http paid-mcp-metering 'https://paid-mcp-metering-clsiojdd7-benlafreniere6-3913s-projects.vercel.app/mcp'
JSON configuration (Claude Desktop, Cursor, VS Code) 
{
    "mcpServers": {
        "paid-mcp-metering": {
            "type": "http",
            "url": "https://paid-mcp-metering-clsiojdd7-benlafreniere6-3913s-projects.vercel.app/mcp"
        }
    }
}

Documentation

From the project's README on GitHub, refreshed weekly. Links open on GitHub.

Contents
  1. paid-mcp-metering
  2. Live deployment
  3. Tools
  4. Rails
  5. Run
  6. Registry
  7. License

paid-mcp-metering

Metered MCP tools, priced per call.

Discovery is free: POST /mcp speaks JSON-RPC 2.0 per the Model Context Protocol (initialize, tools/list, ping). Execution is metered: POST /v1/t/{tool} sits behind an x402 v2 paywall. An unpaid request gets HTTP 402 with payment requirements; a paid request carries a PAYMENT-SIGNATURE header and settles USDC through the facilitator before the tool runs.

Live deployment

Base URL: https://paid-mcp-metering.vercel.app

  • GET /health — free, public
  • POST /mcp — free discovery
  • POST /v1/t/{tool} — metered; currently answers 503 settlement_not_configured because X402_PAY_TO is unset on the deployment (settlementConfigured:false in /health is the honest switch). No payment can be accepted until a receiving address is configured.

server.json declares this URL as the registry remote.

Tools

ToolPriceWhat it returns
web_search$0.001/callRanked live web results with source URLs
deep_research$0.01/callMulti-source research pass with a synthesized answer plus cited sources

Upstreams are Exa (primary) and Tavily (fallback). Every handler returns live upstream output or throws — there is no canned response.

Rails

x402 v2, USDC, EIP-155 network selected by X402_NETWORK (default Base Sepolia testnet, CAIP-2 eip155:84532). Facilitator defaults to https://x402.org/facilitator.

Env varPurpose
X402_PAY_TOReceiving address. Required for settlement; unset serves 402 requirements only
X402_NETWORKCAIP-2 network id (default eip155:84532)
X402_FACILITATOR_URLx402 facilitator endpoint
EXA_API_KEY / TAVILY_API_KEYSearch upstream credentials

Run

npm install
npm run build
npm start          # node dist/x402-server.js
npm test           # build + node --test dist/test-x402.js

Free discovery:

curl -s localhost:4021/mcp -H 'Content-Type: application/json' \
  -d '{"jsonrpc":"2.0","id":1,"method":"tools/list"}'

Paid execution:

curl -s localhost:4021/v1/t/web_search -H 'Content-Type: application/json' \
  -d '{"query":"x402 protocol","max_results":3}'
# -> 402 with payment requirements; pay via an x402 client and retry with PAYMENT-SIGNATURE

Registry

server.json targets the official MCP Registry as io.github.dev55acc-ai/paid-mcp-metering. Tagging v* runs .github/workflows/publish-mcp.yml: tests, build, npm publish (when NPM_TOKEN is set), then registry publish authenticated by GitHub OIDC — no stored registry credential.

License

MIT

Frequently asked questions

What is Paid MCP Metering?

Metered MCP tools: free discovery over MCP; per-call execution settled in USDC via x402 v2.

How do I install Paid MCP Metering?

It runs as a remote server. In Claude Code: claude mcp add --transport http paid-mcp-metering 'https://paid-mcp-metering-clsiojdd7-benlafreniere6-3913s-projects.vercel.app/mcp'. For other clients, paste the JSON configuration from this page into their MCP settings.

Does Paid MCP Metering need an API key?

Its registry entry lists no required key or secret. Some features may still need an account with the service it connects to.

Is Paid MCP Metering open source?

Yes. Its code is on GitHub under the MIT license.

Who maintains Paid MCP Metering?

It is published by dev55acc-ai. AI.tn lists it but does not maintain or endorse it.

From the official MCP Registry. Listing is not an endorsement: review a server's code and permissions before giving it access to your data.