Spec Driven Development
MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.
Description from the maker (original English)
Lets any MCP client pay x402 tools in USDC on Avalanche, with per-call and 24 h caps.
These three are never merged into one score: opinions, measurements and popularity are different things.
We have not written a plain-language summary for this one yet. Below are the facts we read from the registry.
Pick the AI app you use, then copy the settings.
SEKISHO_MCP_URL, SEKISHO_NETWORK, SEKISHO_MAX_PER_CALL, SEKISHO_MAX_PER_DAY, SEKISHO_PAYER_KEY_FILEYou need
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-mcpFill in the empty values before running it.
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.
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.
SEKISHO_NETWORK envSEKISHO_MAX_PER_CALL envSEKISHO_MAX_PER_DAY envSEKISHO_PAYER_KEY_FILE envThese settings are generated from the maker’s registry entry. If the README says otherwise, follow the README.
Runs on your computer; the tool list appears in your AI app after you install it.
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
The registry name was verified with the GitHub account usainbluntmx, which owns the repo
We have not read this repo from GitHub yet
We have not read this repo from GitHub yet
This one runs on your computer; there is no internet endpoint
Runs on your computer and uses local settings instead
Runs on your computer; we can only read tool lists from internet endpoints
Compared with every active server in this category in the registry. Stars count only when the publisher owns the repo.
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.
You need to fill in: SEKISHO_MCP_URL
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).
The GitHub repo last changed –, and the latest version (0.1.1) reached the registry 4 days ago.
Apps that support MCP, such as Claude Desktop, Claude Code, Cursor and VS Code. You also need Node.js on your computer.
In the same category: Spec Driven Development, Remote Desktop Commander, Show HN Launches — buy per-query in-session (showhnwatch)
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
MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.
Remote Desktop Commander: use files, terminal and processes on your own computers from any AI app.
Show HN: indie launches & side projects. $0.01/query. Be born in one call — free testnet funds.
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.
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.
SEKISHO_MAX_PER_CALL, default 0.01 USDC): a tool that costs more is refused, nothing is signed.SEKISHO_MAX_PER_DAY, default 0.10 USDC): kept in a file on disk, so it holds across restarts and sessions.chmod 600); the proxy refuses a file other users can read.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.
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
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.
| 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