Base USDC Payment Verifier (x402)

com.onrender.x402-usdc-verifyPublished by x402-usdc-verify.onrender.comOfficial publisherv1.2.0Updated Oct 29, 2026

Verify a Base tx is a confirmed native-USDC transfer to a recipient. Paid via x402, 0.01 USDC/call.

VerifiedStreamable HTTPWeb executableFinanceBusiness & Commerce

Overview

AI-generated overview

Remote MCP endpoint that checks whether a Base transaction is a confirmed native-USDC transfer to a given recipient, charged per call via x402.

What you can do
  • Verify a Base transaction: confirm that a given transaction hash is a confirmed native-USDC transfer to a specified recipient address.
  • Return a verification result the assistant can use to decide whether a payment actually settled.
  • No individual tools are listed in the manifest, so the exact tool names and parameters are not documented here.
When to use it
Useful when an assistant needs to confirm that a USDC payment on Base actually landed before treating an order, invoice or access request as paid, for example in agent-to-agent or x402 payment flows.
Requirements
A remote streamable HTTP endpoint; no local package or runtime is needed. No authentication, environment variables or headers are declared. Calls are paid through x402 at 0.01 USDC per call, so a wallet able to make x402 payments on Base is needed.
Before you install
Each call costs 0.01 USDC, so repeated verification spends real funds. Payment is handled through x402, which means the client must sign or authorize payments with a wallet. The service is a third-party endpoint, so transaction hashes and recipient addresses you submit are sent to it. Verification only covers native USDC transfers on Base.

Installation

In SourceWeft

  1. Open Base USDC Payment Verifier (x402) in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. 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/com.onrender.x402-usdc-verify%2Fbase-usdc-verifier/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.

{
  "mcpServers": {
    "base-usdc-payment-verifier-x402": {
      "type": "http",
      "url": "https://x402-usdc-verify.onrender.com/mcp"
    }
  }
}

Tools

0
SourceWeft has not read this server's tools yet.

Version history

1
  1. v1.2.0LatestOct 29, 2026

Score

56% 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 listedRequired15 pts

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

  • DescriptionRequired15 pts
  • Logo10 pts

    Publish an icon in the registry entry.

  • Documentation15 pts

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

  • LicenseNot applicable

    A hosted service is used under its provider's terms, so no license is expected here. This check is left out of the percentage.