About Sekisho MCP
Sekisho MCP is a local server for OpenCode, Claude Code, Codex, and other MCP clients to use paid x402 tools from remote MCP servers on Avalanche. It presents tool prices and enforces per-call and rolling 24-hour USDC limits before signing payments.
Key features
- 01Pays x402 tool calls in USDC
- 02Per-call and 24-hour spending caps
- 03Displays prices in tool descriptions
- 04Keeps payer key in a private file
- 05Reports wallet, network, caps, and recent spend
Use cases
- 01Let an agent call paid Avalanche MCP tools
- 02Limit spending on each tool call
- 03Review wallet and recent payment totals
MCP support
Runs locally as an MCP server, connects to a remote paid MCP server over Streamable HTTP, and makes its tools available to MCP clients. It pays supported x402 calls subject to configured caps.
Configuration
Local server config is the same for every client. Copy it into your client’s MCP config file.
npx -y @zero-two-labs/sekisho-mcpSEKISHO_MCP_URLRemote paid MCP server (Streamable HTTP), e.g. https://sekisho-api.zerotwolabs.xyz/mcpSEKISHO_NETWORKavalancheFuji (testnet) or avalanche (mainnet, real USDC)SEKISHO_MAX_PER_CALLMax USDC per tool callSEKISHO_MAX_PER_DAYMax USDC in any 24 h windowSEKISHO_PAYER_KEY_FILESecretPath to the payer private key file (mode 600). Never put the key itself in config.Local servers need a runtime on your machine (e.g. Node.js 18+). Config file locations differ by client; see your client’s docs.
Tools
Local servers expose tools only once running on your machine, and the maintainer has not provided a tool list.
Details
From the project README@zero-two-labs/sekisho-mcp
A local MCP server that lets OpenCode, Claude Code, Codex or any MCP client use paid MCP tools. It connects to a remote MCP server that charges per call with x402 (USDC on Avalanche), shows its tools to your agent, and pays the paid ones from your wallet, never above your caps.
- Per-call cap (
SEKISHO_MAX_PER_CALL, default 0.01 USDC): a tool that costs more is refused, nothing is signed. - 24-hour cap (
SEKISHO_MAX_PER_DAY, default 0.10 USDC): kept in a file on disk, so it holds across restarts and sessions. - The key never goes in your editor config. It is read from a private file (
chmod 600); the proxy refuses a file other users can read. - Prices in tool descriptions. After the first call the agent sees what each tool costs (and whether it is above your cap), so it can decide before paying again.
- Extra free tool
sekisho_wallet: payer address, network, caps and what was spent in the last 24 h.
Works with any x402 exact MCP server on Avalanche, not only Sekisho sellers. Paid services you can use with it are listed at sekisho.zerotwolabs.xyz/services. Listed in the MCP Registry as io.github.usainbluntmx/sekisho-mcp.
1. The payer key
Use a wallet only for this, with a small amount of USDC. It does not need AVAX: the seller pays the gas.
mkdir -p ~/.config/sekisho && chmod 700 ~/.config/sekisho
read -s KEY && printf '%s\n' "$KEY" > ~/.config/sekisho/payer.key && chmod 600 ~/.config/sekisho/payer.key && unset KEY
2. OpenCode
In opencode.json (project root) or ~/.config/opencode/opencode.json (global), per the OpenCode MCP docs:
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"sekisho": {
"type": "local",
"command": ["npx", "-y", "@zero-two-labs/sekisho-mcp"],
"enabled": true,
"environment": {
"SEKISHO_MCP_URL": "https://sekisho-api.zerotwolabs.xyz/mcp",
"SEKISHO_NETWORK": "avalanche",
"SEKISHO_MAX_PER_CALL": "0.01",
"SEKISHO_MAX_PER_DAY": "0.50"
},
"timeout": 60000
}
}
}
Other clients: register a local (stdio) MCP server that runs npx -y @zero-two-labs/sekisho-mcp with the same environment variables.
Configuration
| Variable | Default | Meaning |
|---|---|---|
SEKISHO_MCP_URL | (required) | Remote paid MCP server (Streamable HTTP). https, or http on localhost only |
SEKISHO_NETWORK | avalancheFuji | avalancheFuji (testnet) or avalanche (mainnet, real USDC) |
SEKISHO_MAX_PER_CALL | 0.01 | Max USDC per tool call |
SEKISHO_MAX_PER_DAY | 0.10 | Max USDC in any 24 h window |
SEKISHO_PAYER_KEY_FILE | ~/.config/sekisho/payer.key | Private key file (0x + 64 hex, mode 600) |
SEKISHO_LEDGER_FILE | ~/.config/sekisho/spend.json | Spend log used for the 24 h cap |
Agents call paid tools on their own initiative, not only when you ask: keep the caps low. A signed payment counts toward the cap even if the server then fails to settle it. Logs go to stderr; stdout is the MCP protocol.
MIT · Sekisho by Zero Two Labs
Comments
New to MCP?
From what the protocol is to installing your first server, these answers cover most first questions.
An open protocol that defines how AI applications connect to external tools and data in a uniform way. Clients talk to the model; MCP servers provide tools, resources and prompt templates. They exchange standard messages, so one server can be reused by many clients.