Check x402 Payment Readiness

io.github.kingsleyzissougdiv0.1.2Updated Oct 6, 2026

Call before paying an x402 resource. Returns PAY/BLOCKED. Does not move funds.

VerifiedStreamable HTTPWeb executableFinanceBusiness & Commerce

Overview

AI-generated overview

Lets an assistant check whether an x402 payment resource is ready to pay, returning PAY or BLOCKED without moving funds.

What it does
This remote MCP server exposes a readiness check for x402 payment resources. According to its description, it is meant to be called before paying an x402 resource and returns either PAY or BLOCKED. It does not move funds itself, so it acts as a pre-payment gate rather than a payment executor.
When to use it
Use it when an assistant or agent workflow is about to pay an x402 resource and you want a pre-flight check before committing funds. It is a narrow, single-purpose gate, so it is only worth adding if your workflow already deals with x402 payments.
Requirements
A remote streamable HTTP endpoint at the provider's host; no packages, environment variables, headers, or authentication are declared. Network access to that endpoint is required.
Before you install
The server reports a readiness verdict but does not move funds, so any actual payment still happens elsewhere and should be handled with its own safeguards. No credentials or secrets are declared, but the endpoint is third-party and the check may reveal which x402 resource you intend to pay.

Installation

In SourceWeft

  1. Open Check x402 Payment Readiness 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.

Other MCP clients

Add this to your client's mcpServers config.

{
  "mcpServers": {
    "check-x402-payment-readiness": {
      "type": "http",
      "url": "https://forage.inflbs.xyz/mcp"
    }
  }
}

Tools

0
Tool metadata has not been indexed yet.

Version history

1
  1. v0.1.2LatestOct 6, 2026