well-012-x402-probe

dev.workers.mmelnyk2000.well-012-x402-probePublished by well-012-x402-probe.mmelnyk2000.workers.devOfficial publisherv1.0.0Updated Oct 27, 2026

Unpaid x402 probe: status, latency, payment terms. x402 $0.005 USDC, Base. As is, no warranty.

VerifiedStreamable HTTPWeb executableFinanceDeveloper Tools

Overview

AI-generated overview

A remote x402 probe server that reports status, latency and payment terms for an unpaid x402 endpoint priced at $0.005 USDC on Base.

What you can do
  • Probe an x402 endpoint for its current status and latency.
  • Read the advertised payment terms, including the $0.005 USDC price on Base.
  • No tool list is published, so the exact operations are not documented; the description only covers status, latency and payment terms.
When to use it
Useful when you want an assistant to check whether an x402-paywalled endpoint is reachable and responsive, and to see what it would cost to pay, before wiring it into a workflow.
Requirements
A remote streamable HTTP endpoint; no package, environment variables, headers or authentication are declared. Network access to the hosted worker endpoint is needed.
Before you install
The probe is described as unpaid, and the endpoint quotes a $0.005 USDC payment on Base, so any paid use involves spending crypto funds. The service is offered as is with no warranty, and no tool list or documentation is published, so behavior is unverified.

Installation

In SourceWeft

  1. Open well-012-x402-probe 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/dev.workers.mmelnyk2000.well-012-x402-probe%2Fx402-probe/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": {
    "well-012-x402-probe": {
      "type": "http",
      "url": "https://well-012-x402-probe.mmelnyk2000.workers.dev/mcp"
    }
  }
}

Tools

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

Version history

1
  1. v1.0.0LatestOct 16, 2026

Score

17% 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

    Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.

  • Auth declaredRequired10 pts

    Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.

  • Tools listed15 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.