@scriptmasterlabs/mcp-x402
SCRIPTMASTERLABS x402 Gateway discovers x402 paid APIs and inspects fresh payment requirements before a caller decides whether to pay. It does not autonomously spend.
Current public package
Verified npm release: 2.1.10
Current GitLab source and the public package are intentionally narrow. The canonical public MCP role is discovery and payment-requirement inspection.
Exactly three public MCP tools
sml_status
x402_contract
Query the live MCP schema for runtime authority. Cached directory tool counts do not override the current live contract.
Canonical runtime
Source: https://gitlab.com/timothy.walton45/sml-portfolio/-/tree/main/mcp-x402
x402 directory: https://scriptmasterlabs.com/x402-usdc-api-directory
Payment truth
Current hosted SML payment authority is x402 v2 · Base mainnet (eip155:8453) · USDC. Resolve exact amount, asset, network, receiver and resource from the target endpoint's fresh PAYMENT-REQUIRED challenge immediately before spend.
A 402 challenge is not settlement. A signature is authorization, not settlement. Caller wallet policy remains outside this discovery package.
Older npm/search copy
Older crawls may still show 2.1.3-era autonomous USDC/RLUSD, 402Proof, Ghost Layer, GitHub, credit-score or broad-tool claims. Those are legacy cached package descriptions, not current SCRIPTMASTERLABS payment or source authority.
Use the narrowest product
Use Provider Trust to verify a provider before spend, Agent Web Access for one URL → Markdown job, and Web Research when source discovery is required. Use x402 Gateway when the job itself is finding or inspecting machine-payable services.