Mcp
Call 2s.io pay-per-use tools from your agent with USDC settlement on Base or Solana via x402 instead of manual API billing setup.
Overview
io.github.2s-io/mcp is a Build-phase MCP server that invokes 2s.io pay-per-call tools with USDC settlement on Base or Solana via x402 using your EVM signing key.
What is this MCP server?
- npm @2sio/mcp v1.9.0 with npx runtime hint and stdio transport
- Pay-per-call tooling settled in USDC on Base or Solana using x402 payment authorizations
- Required EVM_PRIVATE_KEY env var signs EIP-3009 style payment flows for Base USDC
- Published from 2s-io/sdk monorepo packages/2s-mcp on GitHub
- Website 2s.io documents the broader pay-per-call tool network behind the MCP surface
- Registry version 1.9.0 for npm package @2sio/mcp with stdio transport
- EVM_PRIVATE_KEY documented as required for x402 EIP-3009 authorizations funding USDC on Base
What problem does it solve?
You want agents to use premium tools on demand but traditional API keys and prepaid credits do not match per-call USDC pricing on Base or Solana.
Who is it for?
Solo builders composing agent workflows who already fund USDC on Base and want metered third-party tools without custom payment middleware.
Skip if: Builders who require flat-rate SaaS billing, no private keys in dev environments, or tools outside the 2s.io x402 network.
What do I get? / Deliverables
Once stdio MCP and EVM_PRIVATE_KEY are configured, your agent can call 2s.io tools with automatic x402 USDC payment authorization per invocation.
- Agent-callable 2s.io tools with x402 USDC settlement
- Stdio MCP integration aligned with the 2s-io SDK monorepo release line
- Metered third-party capability without building a custom payment client first
Recommended MCP Servers
Journey fit
Metered external tools attach during Build when you integrate third-party capabilities into agents and backends. Integrations subphase reflects wallet-signed x402 payments and stdio MCP wiring to the 2s.io tool catalog.
How it compares
x402 USDC pay-per-call MCP gateway, not a local testing skill or static API key REST wrapper alone.
Common Questions / FAQ
Who is io.github.2s-io/mcp for?
It is for developers building MCP-driven agents that consume 2s.io’s priced tool catalog and settle calls in USDC on Base or Solana.
When should I use io.github.2s-io/mcp?
Use it during Build integrations when you are wiring pay-per-use external tools and want x402 payments handled by the official SDK rather than bespoke code.
How do I add io.github.2s-io/mcp to my agent?
Register stdio MCP with npx @2sio/mcp per npm hints, set EVM_PRIVATE_KEY to your 0x-prefixed hex key for Base USDC signing, and fund the wallet before calling paid tools.