MCP Tools DirectoryAbout this integration
USDC payments for AI agents on Base — direct, tabs, x402 paywalls, discovery
- Transport
- stdio
- Authentication
- unknown
- Initial setup
- credentials
- Runtime
- unattended
- Evidence
- documented
- Version
- 0.2.8
- Package
- @pay-skill/mcp
- Last compatibility test
- Not independently tested
Connect your agent
@pay-skill/mcpPublisher README and executable manifest were reviewed from pinned captures. This integration can move funds, create payment commitments, and store signing material in an OS credential store. The package, contracts, wallet flows, and API were not executed or independently security-audited.
Capabilities: USDC payments and x402 requests, Metered payment tabs, Wallet funding and withdrawal links, Paid service discovery and payment webhooks
Connected profiles
Additional details
io.github.pay-skill/pay-mcp
Source ↗ · Checked 2026-09-170.2.8
Source ↗ · Checked 2026-09-17CC0-1.0; package licenses are separate
Source ↗ · Checked 2026-09-17npm
Source ↗ · Checked 2026-09-17@pay-skill/mcp
Source ↗ · Checked 2026-09-190.2.8
Source ↗ · Checked 2026-09-19On first run the server documents automatic wallet generation and OS-keychain storage; subsequent runs load that wallet automatically. PAY_NETWORK selects Base mainnet by default or Base Sepolia testnet.
Source ↗ · Checked 2026-09-19Authentication uses a wallet private key loaded from the OS keychain, an encrypted keystore, a raw hex override, or an automatically generated keypair. This signing-key mechanism does not fit the native API-key, OAuth, or client-credentials taxonomy, so auth remains unknown and setup is classified as credentials.
Source ↗ · Checked 2026-09-19Configure an MCP client to run npx with -y and @pay-skill/mcp over stdio; optional PAYSKILL_SIGNER_KEY and PAY_NETWORK variables alter key resolution and network selection.
Source ↗ · Checked 2026-09-19Publisher documentation reviewed; package and integration endpoint not executed or independently security-audited.
Source ↗ · Checked 2026-09-19