SCRIPTMASTERLABS — x402 Gateway

What SCRIPTMASTERLABS — x402 Gateway MCP server does

SCRIPTMASTERLABS — x402 Gateway MCP server gives MCP clients a remote interface for inspecting the payment infrastructure used by SCRIPTMASTERLABS x402-paid tools. The supplied endpoint is https://mcp-x402.onrender.com/mcp. Its documented capabilities focus on discovery and status rather than general-purpose business operations.

The gateway is intended for agents that need to understand how a paid request is routed and settled. It identifies the relevant x402 gateway contract, shows the canonical payment rail, and exposes details needed to interpret payment requirements. The listed discovery and inspection operations are free to use.

How it works

An MCP client connects to the remote endpoint and invokes one of the available sml_ tools. sml_discover helps locate the x402 Gateway contract and indicates where current payment requirements should be inspected. sml_status returns the gateway’s public identity and canonical payment rail. x402_contract provides contract-level details, including the network, USDC asset, payTo address, relevant headers, and the rule for resolving fresh target requirements.

The tools are useful as a preflight step: an agent can first identify the payment contract and current requirement source, then use that information when working with an x402-paid capability. The supplied material does not describe the execution interface for paid tools themselves, so this listing should not be treated as a catalog of every operation available through the broader gateway.

Tools and capabilities

• sml_discover: Finds the x402 Gateway contract and the location for checking fresh payment requirements. The operation is free.
• sml_status: Reports the gateway’s public identity and canonical payment rail. The operation is free.
• x402_contract: Inspects the canonical x402 payment contract and returns network, USDC asset, payTo, headers, and the target-requirement resolution rule. The operation is free.

SCRIPTMASTERLABS — x402 Gateway is therefore most relevant to payment-aware agent workflows that need contract and rail metadata before attempting a paid request. It does not, based on the supplied tool list, provide a database, code repository, browser, or general financial-account interface.

Setup and configuration

Connect an MCP-compatible client to the remote URL https://mcp-x402.onrender.com/mcp. No environment variables, API keys, authentication method, client-specific installation steps, or local server command are provided in the available material. The endpoint and tool names are the only documented connection details here.

Limitations and notes

The README is unavailable, so client compatibility, transport specifics beyond the remote MCP endpoint, response schemas, uptime, rate limits, and licensing are not documented. The listing confirms free discovery and inspection tools, but it does not specify the cost, authentication, or invocation procedure for any x402-paid tools that may be accessed through the gateway. Verify those details from the gateway’s current payment requirements before building an automated payment flow.

SCRIPTMASTERLABS — x402 Gateway should be selected for x402 contract and payment-rail discovery, not assumed to be a complete payment execution SDK.