# Where to Find MCP Servers That Accept USDC Payments: The Complete 2025 Guide

> Discover MCP servers accepting USDC payments with the punkpeye/awesome-mcp-servers guide. Find and connect to your next gaming server today.

- Repository: [Frank Fiegel/awesome-mcp-servers](https://github.com/punkpeye/awesome-mcp-servers)
- Tags: getting-started
- Published: 2026-09-02

---

**Find MCP servers that accept USDC payments in the punkpeye/awesome-mcp-servers repository, which maintains a searchable directory at glama.ai/mcp/servers and annotates each entry with payment method details including "USDC on Base" for x402-compatible implementations.**

The **punkpeye/awesome-mcp-servers** repository serves as the definitive community-curated registry for Model Context Protocol (MCP) implementations. As the ecosystem evolves toward decentralized, metered billing, dozens of servers now accept **USDC payments** via the x402 micropayment protocol on Base L2, eliminating the need for traditional API keys while enabling per-call billing.

## Locating USDC-Accepting MCP Servers in the Registry

You can identify MCP servers that accept USDC payments through two primary discovery mechanisms documented in the repository's [`README.md`](https://github.com/punkpeye/awesome-mcp-servers/blob/main/README.md).

### Using the Glama Web Directory

The repository maintains a live, auto-generated web directory at **[glama.ai/mcp/servers](https://glama.ai/mcp/servers)** that indexes all listed implementations. This searchable interface flags USDC-enabled servers with specific payment annotations, allowing you to filter for cryptocurrency-payable endpoints without manually scanning the raw markdown source.

### Searching the README.md Source

For developers auditing the registry locally, the root [`README.md`](https://github.com/punkpeye/awesome-mcp-servers/blob/main/README.md) file contains explicit payment metadata for each entry. Search for the string "USDC" to surface all servers implementing the x402 standard. Each entry follows a consistent annotation format indicating "USDC on Base" or "pay-per-call x402 USDC" alongside the server description.

## Categories of MCP Servers Supporting USDC Payments

The repository organizes USDC-payable servers into functional categories, making it easy to locate specific capabilities that align with your agent's requirements.

### Aggregators and Multi-Provider Gateways

These servers aggregate multiple AI providers or data sources behind a single MCP endpoint, charging per-call fees in USDC:

- **Correctover/mcp-server** – Provides BYOK (Bring Your Own Key) direct connections to 9 providers with USDC settlement on Base
- **daedalusdevelopmentgroup/ddg-agent-payable-services** – Operates a pay-per-call x402 gateway routing to multiple backends via USDC on Base  
- **forgemeshlabs/coinopai-mcp** – Delivers x402-powered crypto intelligence with USDC micropayments on Base

### Cloud Platforms and Infrastructure

Infrastructure-as-a-service implementations that charge based on resource consumption:

- **blockrunai/blockrun-mcp** – Offers pay-per-use cloud compute via x402 micropayments with USDC on Base, eliminating monthly subscription requirements

### Finance and Fintech Services

Specialized financial data and trading tools leveraging USDC for high-frequency, low-cost settlement:

- **Gliana-Labs/gliana-mcp** – Implements pay-per-call access with HTTP 402 settlement in USDC across Base, Solana, BNB Chain, and Algorand networks
- **thebrierfox/the-stall** – Provides 209 pay-per-call AI capabilities with USDC payments on Base mainnet
- **whiteknightonhorse/APIbase** – Enables pay-per-call API access via x402 micropayments denominated in USDC

### Payment Infrastructure and Discovery

Core infrastructure servers that facilitate the x402 payment ecosystem itself:

- **x402-index/x402search-mcp** – Charges agents $0.01 USDC per search via x402 micropayments on Base mainnet
- **rplryan/x402-discovery-mcp** – Provides runtime discovery for x402-payable APIs with USDC-per-query billing
- **sF1nX/x402station-mcp** – Offers preflight validation services for USDC on Base transactions

## How the x402 USDC Payment Architecture Works

According to the repository documentation and source implementations, the x402 payment flow follows a standardized cryptographic handshake validated on the Base L2 chain.

When an MCP server marks a tool as **pay-per-call**, it implements the **x402 protocol**, expecting client requests to include a signed payment payload. This payload authorizes the transfer of a specified USDC amount from the caller's wallet to the server's on-chain address. The server validates this payment signature against Base mainnet before executing the requested operation, creating a trustless, metered billing system without API key management overhead.

This architecture enables **per-call microtransactions** as small as fractions of a cent, settled instantly via USDC stablecoin transfers, removing traditional subscription barriers while preventing abuse through cryptographic payment verification.

## Implementing Client-Side USDC Payments

To invoke USDC-payable MCP tools, clients must construct HTTP 402 Payment Required payloads containing signed transaction data. Below are implementation patterns extracted from the repository's example integrations.

### Python Client Implementation

```python
import requests
import json

# Build the tool call payload with x402 payment envelope

payload = {
    "tool": "price_usd",
    "args": {"symbol": "BTC"},
    "payable": {
        "currency": "USDC",
        "amount": "0.001",          # 0.1 cents per call

        "chain": "base",
        "paymentSignature": "0x…"   # Signed by caller's wallet

    }
}

# POST to MCP endpoint with payment verification

resp = requests.post(
    "https://gliana-mcp.gliana.ai/mcp",
    json=payload,
    headers={"Content-Type": "application/json"}
)

print(json.dumps(resp.json(), indent=2))

```

### CLI Wrapper Usage

```bash

# Using npm-based CLI wrapper for Gliana MCP servers

npx -y @gliana-ai/mcp price_usd --symbol BTC --pay USDC=0.001

```

Both approaches attach the required payment payload that servers validate on-chain prior to response generation. The `paymentSignature` field must contain a valid EIP-712 signature authorizing the USDC transfer on Base.

## Contributing New USDC-Supported Servers

To add a new MCP server accepting USDC payments to the registry, follow the contribution guidelines in [`CONTRIBUTING.md`](https://github.com/punkpeye/awesome-mcp-servers/blob/main/CONTRIBUTING.md). When submitting entries via pull request, include explicit payment metadata in the server description, such as "USDC on Base" or "x402 micropayments," to ensure proper indexing by the Glama directory crawler and search functionality.

## Summary

- The **punkpeye/awesome-mcp-servers** repository maintains the canonical list of USDC-accepting MCP implementations at glama.ai/mcp/servers
- **x402 protocol** enables USDC micropayments on Base L2, replacing API keys with cryptographic payment verification
- Servers are categorized into Aggregators, Cloud Platforms, Finance/Fintech, and Payment Infrastructure segments
- Client implementations must attach signed payment payloads specifying currency (USDC), amount, chain (Base), and payment signature
- Repository files [`README.md`](https://github.com/punkpeye/awesome-mcp-servers/blob/main/README.md) and [`CONTRIBUTING.md`](https://github.com/punkpeye/awesome-mcp-servers/blob/main/CONTRIBUTING.md) provide the complete annotation schema for payment metadata

## Frequently Asked Questions

### How do I know if an MCP server requires USDC payment versus free usage?

Inspect the server entry in the [`README.md`](https://github.com/punkpeye/awesome-mcp-servers/blob/main/README.md) file or the Glama directory listing. USDC-payable servers display specific icons and text annotations like "USDC on Base," "pay-per-call x402," or "HTTP 402." Free servers typically lack payment annotations or display "free tier" indicators.

### What wallet infrastructure do I need to pay for MCP calls with USDC?

You need an Ethereum-compatible wallet funded with USDC on the Base L2 network. The client library must support EIP-712 typed data signing to generate the `paymentSignature` required by x402-compliant servers. Popular options include MetaMask, Coinbase Wallet, or programmatic MPC wallets that can authorize micro-transactions automatically.

### Are USDC payments on MCP servers limited to the Base blockchain?

While the majority of indexed servers operate on Base for cost efficiency, some implementations like **Gliana-Labs/gliana-mcp** support multi-chain USDC settlement across Base, Solana, BNB Chain, and Algorand. Always verify the `"chain"` parameter in the server's documentation before initiating payment.

### What happens if my USDC payment transaction fails during an MCP call?

If the payment signature is invalid, expired, or the wallet lacks sufficient USDC balance, the server returns an HTTP 402 Payment Required status without executing the tool. The response body typically includes the required payment amount and valid blockchain addresses, allowing your client to retry with a valid payment payload.