AgnicPay MCP
- agnicpay-prog/agnicpay-mcp
AgnicPay is a MCP server that auto-pays 300+ APIs for AI agents using USDC on Base and Solana through an X402 payment remote.
About
AgnicPay is an MCP server that lets developers attach autonomous checkout to hundreds of paid APIs without hand-rolling payment handlers for every provider. You connect via the hosted SSE endpoint with an AgnicPay API token, and your agent can satisfy X402-style payment requirements using USDC on Base or Solana while continuing its task. That matters when you are prototyping agents that call search, data, or generation APIs that bill per request—one integration layer instead of a patchwork of Stripe links and manual top-ups. Placement is Build integrations because you register the remote MCP alongside other tool servers before Ship hardening. Complexity is intermediate: you need stable wallet funding and to understand which chain each endpoint expects. It is a payment rail MCP, not a skill for pricing strategy or subscription UX design.
- X402 payment MCP for AI agents with USDC on Base and Solana
- Auto-pay access across 300+ APIs from one MCP remote
- Hosted SSE remote at https://mcp.agnic.ai/sse with API token auth
- Registry version 1.0.3; no local stdio package required for remote use
AgnicPay MCP by the numbers
- Data as of Aug 10, 2026 (Skillselion catalog sync)
claude mcp add --transport sse agnicpay https://mcp.agnic.ai/sseAdd your badge
Show developers this MCP server is listed on Skillselion. Paste this into your README.
| Transport | SSE |
|---|---|
| Auth | None |
| Repository | agnicpay-prog/agnicpay-mcp ↗ |
What it does
Auto-pay metered third-party APIs from your agent using USDC on Base and Solana via the X402 payment flow.
Who is it for?
Best when you're shipping agents that must call many metered APIs and want one USDC payment layer on Base or Solana.
Skip if: Products that only need human checkout, single-vendor Stripe, or chains AgnicPay does not support.
What you get
After you add the SSE remote with your API token, your agent can clear X402 payments and keep calling supported APIs without custom payment code per service.
- Single MCP remote for agent-triggered API payments
- Coverage narrative for 300+ auto-payable APIs via X402
- Multi-chain USDC settlement on Base and Solana
By the numbers
- Markets auto-pay for 300+ APIs (per publisher description)
- Server version 1.0.3 with one SSE remote endpoint
Recommended MCP Servers
$THREE Token MCPPrice, hold, and burn $THREE on Solana — the first MCP server whose actions burn a token.91
402 MCPAI agents discover, pay for, and consume any Lightning-gated API autonomously
9192 Public Compute MCPRemote MCP for 9192 discovery, pricebook, payment rails, GET_PULSE quotes, and receipt checks.
Aarna MCPAarna - 34 tools for swap quotes, liquidity pools, and trading dataAave MCPAave - 6 tools for lending rates, supply, and borrow data
AbraFlexi MCPMCP server for AbraFlexi ERP — invoices, contacts, products, bank transactions.1How it compares
Hosted X402 payment MCP for API spend, not an open-source Solana ZK pool tool or a documentation skill.
FAQ
Who is AgnicPay MCP for?
Developers and small teams running coding agents that need to pay for third-party APIs automatically with USDC.
When should I use AgnicPay MCP?
Use it in Build when you connect agents to paid endpoints and want X402 settlement on Base or Solana instead of manual billing per API.
How do I add AgnicPay MCP to my agent?
Register the remote MCP SSE URL https://mcp.agnic.ai/sse in your client and supply your AgnicPay MCP API token as the documented apiKey variable.