Finance · Remote MCP server
x402 Pay - USDC API Payment Helper
Pay for APIs with USDC. Read-only x402 payment discovery, verification, evidence, and status.
What the MCP Registry states
The entry as published to the official MCP Registry (read 2026-10-04), latest version.
- Registry name
com.scriptmasterlabs/x402-pay- Version
- 1.0.0
- Status
- Active
- Category
- finance
- Transport
- Streamable HTTP
- Published
- 2026-09-05
- Updated
- 2026-09-05
- Publisher
- com.scriptmasterlabs · 5 servers with pages here
- Namespace
- Namespace verified by the MCP Registry via the domain scriptmasterlabs.com · how
- Website
- www.scriptmasterlabs.com/stack.html
- Repository
- gitlab.com/timothy.walton45/sml-portfolio
- Source
- Registry API entry
Remote endpoints
| Transport | URL | Headers declared |
|---|---|---|
| Streamable HTTP | https://squeezeos-api.onrender.com/mcp/x402-pay | None |
Live check
This directory connected to each remote endpoint and asked for its list of tools. The check connects and lists tools only; it doesn't run tools, sign in or test security.
- Reachable
- Yes (HTTP 200)
- Handshake
- x402-pay 1.0.1 · protocol 2025-06-18
- Tools discovered
- 4:
payment_info,list_paid_apis,check_payment,check_status - Checked on
- 2026-10-05
How to connect x402 Pay - USDC API Payment Helper
x402 Pay - USDC API Payment Helper is a remote MCP server: there is nothing to install. Its endpoint is https://squeezeos-api.onrender.com/mcp/x402-pay, served over Streamable HTTP. In an assistant that accepts remote MCP servers (often under a setting named connectors, integrations or tools), add a new server and give it this URL; in a client configured by file, add it as a remote (HTTP) server with the same URL.
No headers are declared in the registry entry. If the server needs you to sign in, a client that supports MCP authorization opens the service's own sign-in page when it first connects.
Derived from the registry entry; the live check above only shows whether the endpoint answered. What the server does, and on what terms, is set by its publisher; check its repository or website before giving it access to your accounts or files. How to add an MCP server to an assistant · Before you connect
More from com.scriptmasterlabs
| Server | Runs |
|---|---|
| GhostKey - Route Paid APIs with x402Find paid APIs, check access policy and price, and route x402 requests. No autonomous spending. | Remote · HTTPLive check: ✓ handshake |
| Provider Trust - Verify a Source or ProviderVerify a source or provider before an AI agent trusts it. Evidence only; unknown stays unknown. | Remote · HTTPLive check: ✓ handshake |
| SCRIPTMASTERLABS - SqueezeOS MCPSqueezeOS MCP for live machine discovery and x402-paid USDC APIs on Base. | Remote · HTTPLive check: ✓ handshake |
| x402 Gateway - Inspect Paid API TermsDiscover x402 paid APIs and inspect fresh payment requirements before authorizing spend. | Remote · HTTPLive check: ✗ no handshake |
More finance servers
| Server | Runs |
|---|---|
| x402 MCP StarterFree self-hosted x402 USDC billing for Cloudflare MCP servers, with a Base Sepolia test endpoint. | Remote · HTTPLive check: ✓ handshake |
| x402 Merchant CheckPre-payment merchant trust checks for x402 agents on Base and Solana. | Remote · HTTPLive check: ✓ handshake |
| X402 MiddlewareOne-line x402 + Stripe payment middleware for MCP servers. The Stripe for the agent economy. | Local · stdio |
| x402 Notary MCPCryptographic receipts for AI outputs on Base or Solana via x402. | Local · stdio |
| X402 Payagent MCPPay x402 APIs in USDC on Base, Solana, and BNB Chain with spend mandates, receipts, idempotency. | Local · stdio |
| x402 SellerPay-per-call MCP tools (crypto/DeFi data, web reading, AI tasks) in USDC over x402 on Base. | Local · stdio |
| X402 ServicesThe only x402 MCP server for Robinhood Chain (chainId 4663) - 147 onchain, trading & AI tools. | Remote · HTTPLive check: ✓ handshake |
| X402 SolanaX402 paid API tools for AI agents on Solana: crypto safety, market data, KYB/AML verification. | Remote · HTTPLive check: ✓ handshake |