Prototype · Preview: every server in the official registry, synced every 30 minutes. Reviews and accounts come in a later step.
PopNx MCPMCP servers for people who use AI · explained in plain words

Sekisho MCP

by usainbluntmxversion 0.1.1i★ –iRuns on your computer
Registry nameio.github.usainbluntmx/sekisho-mcp

Install

Overview

Description from the maker (original English)

Lets any MCP client pay x402 tools in USDC on Avalanche, with per-call and 24 h caps.

PopNx MCP’s three pillars

These three are never merged into one score: opinions, measurements and popularity are different things.

What you can do with it

We have not written a plain-language summary for this one yet. Below are the facts we read from the registry.

  • Connection: Runs on your computer
  • Transport: stdio
  • Category: Other
  • You need to fill in: SEKISHO_MCP_URL

Install

Pick the AI app you use, then copy the settings.

Before you install

  • Basic checks: 1 of 1 passed
  • Runs on your computer with your user’s permissions (files, network, apps).
  • You fill in yourself: SEKISHO_MCP_URL, SEKISHO_NETWORK, SEKISHO_MAX_PER_CALL, SEKISHO_MAX_PER_DAY, SEKISHO_PAYER_KEY_FILE

You need

  • npmNode.js installed (for the npx command)

Which app do you use?

Pick your app above. We remember it, so next time the button says “Install in …”.

Open Claude Desktop → Settings → Developer → Edit Config, and paste this into claude_desktop_config.json

{
  "mcpServers": {
    "sekisho": {
      "command": "npx",
      "args": [
        "-y",
        "@zero-two-labs/sekisho-mcp"
      ],
      "env": {
        "SEKISHO_MCP_URL": "your-value",
        "SEKISHO_NETWORK": "your-value",
        "SEKISHO_MAX_PER_CALL": "your-value",
        "SEKISHO_MAX_PER_DAY": "your-value",
        "SEKISHO_PAYER_KEY_FILE": "your-value"
      }
    }
  }
}

Run this in your terminal

claude mcp add sekisho --env SEKISHO_MCP_URL=your-value --env SEKISHO_NETWORK=your-value --env SEKISHO_MAX_PER_CALL=your-value --env SEKISHO_MAX_PER_DAY=your-value --env SEKISHO_PAYER_KEY_FILE=your-value -- npx -y @zero-two-labs/sekisho-mcp

Fill in the empty values before running it.

Open in Cursor

Or copy the settings yourself

Paste into .cursor/mcp.json in your project, or ~/.cursor/mcp.json

{
  "mcpServers": {
    "sekisho": {
      "command": "npx",
      "args": [
        "-y",
        "@zero-two-labs/sekisho-mcp"
      ],
      "env": {
        "SEKISHO_MCP_URL": "your-value",
        "SEKISHO_NETWORK": "your-value",
        "SEKISHO_MAX_PER_CALL": "your-value",
        "SEKISHO_MAX_PER_DAY": "your-value",
        "SEKISHO_PAYER_KEY_FILE": "your-value"
      }
    }
  }
}

Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.

Open in VS Code

Or copy the settings yourself

Paste into .vscode/mcp.json in your project

{
  "servers": {
    "sekisho": {
      "type": "stdio",
      "command": "npx",
      "args": [
        "-y",
        "@zero-two-labs/sekisho-mcp"
      ],
      "env": {
        "SEKISHO_MCP_URL": "your-value",
        "SEKISHO_NETWORK": "your-value",
        "SEKISHO_MAX_PER_CALL": "your-value",
        "SEKISHO_MAX_PER_DAY": "your-value",
        "SEKISHO_PAYER_KEY_FILE": "your-value"
      }
    }
  }
}

Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.

This one runs on your computer, and ChatGPT can only connect to servers on the internet. Pick another app.

Your choice stays on this device in a cookie; no account needed.

Values you fill in

  • SEKISHO_MCP_URL required env
    Remote paid MCP server (Streamable HTTP), e.g. https://sekisho-api.zerotwolabs.xyz/mcp
  • SEKISHO_NETWORK env
    avalancheFuji (testnet) or avalanche (mainnet, real USDC)
  • SEKISHO_MAX_PER_CALL env
    Max USDC per tool call
  • SEKISHO_MAX_PER_DAY env
    Max USDC in any 24 h window
  • SEKISHO_PAYER_KEY_FILE env
    Path to the payer private key file (mode 600). Never put the key itself in config.

These settings are generated from the maker’s registry entry. If the README says otherwise, follow the README.

What it can do

Runs on your computer; the tool list appears in your AI app after you install it.

Basic checksi

We check information anyone can see; we have not read the code. Checks that do not apply are left out of the count. · Checked Nov 9, 2026

  • ✓ Pass

    Maker matches the repo

    The registry name was verified with the GitHub account usainbluntmx, which owns the repo

  • … Not checked yet

    Still maintained

    We have not read this repo from GitHub yet

  • … Not checked yet

    Has a licence

    We have not read this repo from GitHub yet

  • – Not applicable

    Endpoint responds

    This one runs on your computer; there is no internet endpoint

  • – Not applicable

    Sign-in with OAuth

    Runs on your computer and uses local settings instead

  • … Not checked yet

    No hidden instructions in tool descriptions

    Runs on your computer; we can only read tool lists from internet endpoints

Compared with others in Otheri

  • More stars than 0% of the other 18654 servers in this category
  • Published to the registry more recently than 92% of the other 18654 servers in this category
  • Basic checks equal to or better than 100% of the other 18654 servers in this category

Compared with every active server in this category in the registry. Stars count only when the publisher owns the repo.

Common questions

Is Sekisho MCP safe?

It passed 1 of 1 applicable basic checks. We have not read the code. Before adding a key or token, see what access the server asks for and use a key with only the permissions you need.

What keys or codes does it need?

You need to fill in: SEKISHO_MCP_URL

Does it run on my computer or in the cloud?

It runs on your computer. Your AI app starts it when needed, and data does not pass through the maker’s servers (unless it calls an online service itself).

Is it still maintained?

The GitHub repo last changed –, and the latest version (0.1.1) reached the registry 4 days ago.

Which apps can use it?

Apps that support MCP, such as Claude Desktop, Claude Code, Cursor and VS Code. You also need Node.js on your computer.

What can I use instead?

In the same category: Spec Driven Development, Remote Desktop Commander, Show HN Launches — buy per-query in-session (showhnwatch)

Alternatives

Servers in the same category from other makers, sorted by stars.

Reading a card:↓ Downloads per weeki★ GitHub starsiThree pillars: reviews · checks · usageiUpdated = latest version published to the registryi

Spec Driven Development

MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.

by formulahendryEarly↓ 66/wk★ 440Updated 14 months ago

Runs on your computer

Remote Desktop Commander

Remote Desktop Commander: use files, terminal and processes on your own computers from any AI app.

by desktop-commanderGrowing★ 211Updated 3 days ago

Runs in the cloud✓ desktopcommander.app

README from the maker

Open the README

Copied from the maker’s repo as written. PopNx MCP has not reviewed or endorsed it. HTML, images and scripts are removed. Links lead off this site.

@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

VariableDefaultMeaning
SEKISHO_MCP_URL(required)Remote paid MCP server (Streamable HTTP). https, or http on localhost only
SEKISHO_NETWORKavalancheFujiavalancheFuji (testnet) or avalanche (mainnet, real USDC)
SEKISHO_MAX_PER_CALL0.01Max USDC per tool call
SEKISHO_MAX_PER_DAY0.10Max USDC in any 24 h window
SEKISHO_PAYER_KEY_FILE~/.config/sekisho/payer.keyPrivate key file (0x + 64 hex, mode 600)
SEKISHO_LEDGER_FILE~/.config/sekisho/spend.jsonSpend 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

Ask PopNx