AgnicPay

io.github.agnicpay-progPublished by GitHub account agnicpay-progv1.0.3Updated Oct 27, 2026

X402 payment MCP for AI agents. Auto-pay 300+ APIs with USDC on Base and Solana.

VerifiedSSEWeb executableFinanceDeveloper Tools

Overview

AI-generated overview

Remote MCP endpoint that lets an AI agent make X402 payments in USDC on Base and Solana to auto-pay 300+ APIs.

What you can do
  • Pay for X402-enabled APIs on behalf of the agent using USDC on Base and Solana.
  • Access a catalog of 300+ APIs that can be paid automatically.
  • Handle payment authorization through OAuth sign-in to the hosted service.
  • No tool list is published, so the exact operations are not documented in the supplied material.
When to use it
Consider it when an agent needs to call paid, X402-metered APIs and you want the payment step handled automatically rather than manually topping up each service.
Requirements
A remote SSE endpoint at the provider's hosted address; no local package or runtime is needed. OAuth authentication is required, so an account with the provider is implied. No environment variables or headers are declared.
Before you install
It moves real money: payments are made in USDC on Base and Solana, so spending limits and wallet exposure should be reviewed before connecting. OAuth grants the server access to the agent's payment flow, and the tool list is not published, so what it can charge for cannot be verified from the listing.

Installation

In SourceWeft

  1. Open AgnicPay in the dashboard and add it to a workspace.
  2. Connect the required credentials. They are stored privately and never shown on public pages.
  3. Enable the server for the chats that should use its tools.

Web executable via SSE. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/io.github.agnicpay-prog%2Fagnicpay/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config. The client completes OAuth sign-in on first connect.

{
  "mcpServers": {
    "agnicpay": {
      "type": "sse",
      "url": "https://mcp.agnic.ai/sse"
    }
  }
}

README

This repository has no README.

Tools

0
This server asks you to sign in, so SourceWeft could not read its tools without an account and has not indexed them. What a connected account sees can depend on that account and its permissions.

Version history

1
  1. v1.0.3LatestSep 16, 2026

Score

60% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 daysRequired25 pts
  • Auth declaredRequired10 pts
  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts

    Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.

  • License10 pts

    Declare a license in the repository or the registry entry.