
Sekisho MCP
io.github.usainbluntmxPublished by GitHub account usainbluntmxv0.1.1Updated Nov 5, 2026
Lets any MCP client pay x402 tools in USDC on Avalanche, with per-call and 24 h caps.
Overview
Local proxy MCP server that lets an assistant use paid x402 MCP tools, paying per call in USDC on Avalanche within per-call and daily caps.
- What you can do
- Connect to a remote x402-enabled MCP server and expose its tools to the assistant
- Pay for paid tool calls in USDC on Avalanche from a local payer wallet, refusing anything above the per-call cap
- Enforce a rolling 24-hour spending cap kept in a file on disk across restarts and sessions
- Show tool prices in tool descriptions after the first call so the assistant can judge cost before paying again
- Report payer address, network, caps and recent spend through a free wallet tool
- When to use it
- Use it when you want an assistant to call paid x402 MCP services on Avalanche and you need hard spending limits and a dedicated low-balance wallet rather than open-ended payments.
- Requirements
- Runs locally via npx from the npm package; needs Node.js. Requires SEKISHO_MCP_URL pointing at a remote Streamable HTTP MCP server, a payer private key file at SEKISHO_PAYER_KEY_FILE with mode 600, and USDC on Avalanche (testnet avalancheFuji or mainnet avalanche). Caps are set with SEKISHO_MAX_PER_CALL and SEKISHO_MAX_PER_DAY.
Installation
In SourceWeft
- Open Sekisho MCP in the dashboard and add it to a workspace.
- Enable the server for the chats that should use its tools.
Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.
Other MCP clients
Follow the launch instructions in the repository.
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.
2. OpenCode
In opencode.json (project root) or ~/.config/opencode/opencode.json (global), per the OpenCode MCP docs:
Other clients: register a local (stdio) MCP server that runs npx -y @zero-two-labs/sekisho-mcp with the same environment variables.
Configuration
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
Source: packages/sekisho-mcp/README.md at commit 1a3442a
Tools
0Version history
1- v0.1.1LatestNov 5, 2026
Score
50% of the applicable checks met
How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.
- Reached in the last 30 days25 pts
Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.
- Auth declared10 pts
Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.
- Tools listed15 pts
Answer tools/list without a credential, or ship a package that starts in a sandbox without one.
- DescriptionRequired15 pts
- Logo10 pts
- Documentation15 pts
- License10 pts