Enterprise DNA
M MCP Servers Developer low

fernsugi/x402-api-server

by Various

x402 protocol API server — pay-per-call DeFi data endpoints using USDC micropayments on Base

F

MCP

fernsugi/x402-api-server

Added 1 June 2026

#ai-agent #crypto #defi #elizaos-plugins #mcp #micropayments #usdc #x402

Overview

An API server implementing the x402 protocol for pay-per-call DeFi data endpoints. It enables USDC micropayments on the Base network for each API request. Built in JavaScript, it provides a server that handles payment verification and data delivery.

Best for

Best for
Developers building DeFi applications that need pay-per-call data access with USDC micropayments on Base

Use cases

  • Serve DeFi data endpoints with per-call USDC micropayments
  • Integrate pay-per-use data feeds into dApps on Base
  • Build a monetized API for blockchain data without subscriptions

Notes

An API server implementing the x402 protocol for pay-per-call DeFi data endpoints. It enables USDC micropayments on the Base network for each API request. Built in JavaScript, it provides a server that handles payment verification and data delivery.

2 stars on GitHub. Last updated 2026-03-25.

Use cases

  • Serve DeFi data endpoints with per-call USDC micropayments
  • Integrate pay-per-use data feeds into dApps on Base
  • Build a monetized API for blockchain data without subscriptions

Pros

  • Implements the x402 protocol for standardized pay-per-call payments
  • Uses USDC on Base for low-cost micropayments
  • Open source and customizable for specific data endpoints

Cons

  • Very early stage with only 2 GitHub stars and limited community
  • Currently only supports Base network for payments
  • Requires running and maintaining your own server instance

Indexed from awesome-mcp-servers-punkpeye and enriched against its public facts.

Pros

  • Implements the x402 protocol for standardized pay-per-call payments
  • Uses USDC on Base for low-cost micropayments
  • Open source and customizable for specific data endpoints

Cons

  • Very early stage with only 2 GitHub stars and limited community
  • Currently only supports Base network for payments
  • Requires running and maintaining your own server instance