Micropay Test Suite

app.netlify.micropay-test-suitePublished by micropay-test-suite.netlify.appOfficial publisherv1.0.0Updated Oct 24, 2026

Verify your agent's x402 payment flow for free on Base Sepolia testnet before real money moves.

VerifiedStreamable HTTPWeb executableBusiness & Commerce

Overview

AI-generated overview

Lets an assistant verify an agent's x402 payment flow for free on the Base Sepolia testnet.

What you can do
Exposes one tool, check_payment_flow, that verifies an agent's x402 payment flow against a free Base Sepolia testnet endpoint. Call it with no arguments to receive the payment-required challenge (price, network, payTo), sign that challenge with an x402 client, then call again passing paymentSignature as the encoded PAYMENT-SIGNATURE header value.
When to use it
Use it while developing or debugging an x402 client, to confirm the challenge and signing flow works before real money is involved.
Requirements
Remote MCP endpoint over streamable HTTP; no local runtime or package needed. Requires network access to the endpoint and an x402 client able to sign the payment challenge. No authentication, environment variables or headers are declared.
Before you install
The tool handles payment signatures: the assistant processes and sends a PAYMENT-SIGNATURE value, so use testnet keys only and never sign with real funds or production assets. The service is third-party hosted, so signed data is sent to that endpoint.

Installation

In SourceWeft

  1. Open Micropay Test Suite 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/app.netlify.micropay-test-suite%2Fmicropay-test-suite/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": {
    "micropay-test-suite": {
      "type": "http",
      "url": "https://micropay-test-suite.netlify.app/api/mcp"
    }
  }
}

Tools

1

check_payment_flow

Check x402 payment flow

Verifies an agent's x402 payment flow against a free Base Sepolia testnet endpoint. Call with no arguments first to get back the payment-required challenge (price, network, payTo). Sign it with your x402 client, then call again passing paymentSignature as the encoded PAYMENT-SIGNATURE header value to get back a verified/failed receipt.

ParameterspaymentSignature

Version history

1
  1. v1.0.0LatestSep 16, 2026

Score

83% 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
  • DescriptionRequired15 pts
  • Logo10 pts
  • 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.