Neura Market Logo

x402 MCP Starter

Validate x402 USDC payment configurations for a read-only MCP product on Cloudflare Workers before adding paid tools or deploying.

門屋　哲朗

@kadopi

Install

$ openclaw skills install @kadopi/x402-mcp-starter

x402 MCP Starter

Use this skill when an MCP product needs a small, x402-aware USDC payment path for a read-only result. Start before deployment, when the operator needs to check the network, USDC asset, price, recipient, and facilitator configuration.

Do not use it to custody wallets, move funds for another party, implement a subscription system, or turn an unvalidated product into a paid service.

Connect

  • MCP endpoint: https://x402-mcp-starter.kadopi.workers.dev/mcp
  • MCP Service Card: https://x402-mcp-starter.kadopi.workers.dev/.well-known/agent-card.json
  • Product page: https://aegis-sales-bot.kadopi.workers.dev/products/x402-mcp-starter
  • Source: https://github.com/kadopi/x402-mcp-starter
  • MCP Registry search: https://registry.modelcontextprotocol.io/?q=io.github.kadopi%2Fx402-mcp-starter

Free configuration check

Call validate_x402_config before deployment with:

  • network: eip155:84532 for Base Sepolia test USDC, or eip155:8453 for Base Mainnet real USDC;
  • asset, amount, and priceUsd: the intended canonical USDC asset and matching atomic-unit price;
  • payTo: the controlled recipient EVM address;
  • facilitatorUrl: the HTTPS facilitator endpoint.

If ready is false, correct only the returned configuration errors. Do not deploy or attempt payment until it is true.

Paid sample boundary

get_paid_sample is a fixed-price reference path, not product revenue. A call that may trigger payment requires the business principal's explicit approval immediately beforehand. Keep buyer keys in the payment client; never provide a private key or payment signature in a prompt, source file, log, or support message.

For a real customer product, replace the sample handler with one defined read-only result and state the price, delivery, retry, and failure behavior before release.

Limits

The public endpoint uses Base Sepolia and test USDC by default. The buyer's private key stays in the payment client. Production Mainnet operation requires the operator's own configuration, deployment approval, and a separately authorized payment decision.

Top skills in this category

API Gateway

@byungkyu

Call third-party APIs through the Maton gateway, which injects the credential for an app the user has already connected. Use this skill when the user names a connected app and a concrete action in it - read a mailbox, query a CRM, file an issue, update a spreadsheet, etc.

39488k

HubSpot

@hith3sh

HubSpot CRM API integration with managed OAuth. Manage contacts, companies, deals, pipelines, tickets, products, line items, marketing emails, and workflows....

327.2k

Master Marketing

@tevfikgulep

All-in-one marketing engine combining growth strategy, content remixing, and trend monitoring. Drive growth with data-driven strategies, repurposed content across all platforms, and real-time trend analysis.

148.1k

Feishu Bridge

@alexanys

Connect a Feishu (Lark) bot to Clawdbot via WebSocket long-connection. No public server, domain, or ngrok required. Use when setting up Feishu/Lark as a messaging channel, troubleshooting the Feishu bridge, or managing the bridge service (start/stop/logs). Covers bot creation on Feishu Open Platform, credential setup, bridge startup, macOS launchd auto-restart, and group chat behavior tuning.

812k

Zoho CRM

@byungkyu

Zoho CRM API integration with managed OAuth. Manage leads, contacts, accounts, deals, and other CRM records. Use this skill when users want to read, create, update, or delete CRM records, search contacts, manage sales pipelines, access organization settings, manage users, or retrieve module metadata in Zoho CRM. For other third party apps, use the api-gateway skill (https://clawhub.ai/byungkyu/api-gateway). Requires network access and valid Maton API key. Calls run through the `maton` CLI with OAuth login, or over raw HTTP with a Maton API key where the CLI cannot be installed. Every call is authenticated as the user's connection and reaches only what that connection's authorization allows, which the provider enforces on every request; the endpoints documented here are the ones this skill uses, and any other endpoint of this app needs the user to ask for it by name. Default to read and list calls, and confirm every write or new connection with the user. This file also documents the three constructs that turn a Zoho CRM connection into automation, in the order they are used: the connection (the first step), a hosted function that runs a Zoho CRM action through the Maton SDK, and a trigger that calls that function on a schedule or on an event. Those sections are the platform's own reference text, shared with the api-gateway skill, with Zoho CRM examples; they add no Zoho CRM capability - Zoho CRM is not an event source, a trigger cannot read Zoho CRM data, and the files under `references/<source>/triggers.md` are the platform's event catalogues for the sources Maton offers (time, Calendly, GitHub, Gmail, HubSpot, Linear, Notion, Slack, Stripe).

615k