Sekisho MCP runs on your own machine — the client starts it, so there is no endpoint to ping. Last commit 6 Nov 2026.
Lets any MCP client pay x402 tools in USDC on Avalanche, with per-call and 24 h caps.
What the code does
We read the source, 21 h ago · rules 995398eba69f
What this server is able to do. For an MCP server this is often the job itself — a terminal server runs commands because that is what it is for. Listed so you know what you are plugging in, not as an accusation.
"bytecode": "0x60c060405234801561000f575f5ffd5b50604051611a15380380611a1583398101604081905261002e916101a6565b836001600160a01b03811661005c57604051631e4fbdf760e01b81525f600482015260240160405180910390fd5b6100658161012f565b506001600160a01b038316158061008357506001600160a01b038116155…
const API = "https://api.telegram.org";
Is this your server and something here is wrong? Tell us — corrections are free and do not require a plan.
This code can reach further than it looks
We found places where it runs commands, builds paths or queries from values it is given. None of that is a flaw by itself — it becomes one when the code changes, and code changes quietly between releases. We re-read it on every one.
Connect this server
This server runs on your own machine — install it with the package manager and the client starts it for you. Package name taken from the official registry entry.
claude mcp add sekisho-mcp -e 'SEKISHO_MCP_URL=<SEKISHO_MCP_URL>' -- npx -y @zero-two-labs/sekisho-mcp{
"mcpServers": {
"sekisho-mcp": {
"command": "npx",
"args": [
"-y",
"@zero-two-labs/sekisho-mcp"
],
"env": {
"SEKISHO_MCP_URL": "<SEKISHO_MCP_URL>"
}
}
}
}[mcp_servers.sekisho-mcp]
command = "npx"
args = ["-y", "@zero-two-labs/sekisho-mcp"]
env = { SEKISHO_MCP_URL = "<SEKISHO_MCP_URL>" }{
"mcpServers": {
"sekisho-mcp": {
"command": "npx",
"args": [
"-y",
"@zero-two-labs/sekisho-mcp"
],
"env": {
"SEKISHO_MCP_URL": "<SEKISHO_MCP_URL>"
}
}
}
}{
"servers": {
"sekisho-mcp": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"@zero-two-labs/sekisho-mcp"
],
"env": {
"SEKISHO_MCP_URL": "<SEKISHO_MCP_URL>"
}
}
}
}Put your own value in place of
<SEKISHO_MCP_URL> (Remote paid MCP server (Streamable HTTP), e.g. https://sekisho-api.zerotwolabs.xyz/mcp).
The author’s registry entry marks it as required.
Optional settings from the registry entry, left out of the block above:
SEKISHO_NETWORK (avalancheFuji (testnet) or avalanche (mainnet, real USDC)), SEKISHO_MAX_PER_CALL (Max USDC per tool call), SEKISHO_MAX_PER_DAY (Max USDC in any 24 h window), SEKISHO_PAYER_KEY_FILE (Path to the payer private key file (mode 600). Never put the key itself in config).
Alternatives to Sekisho MCP
same job, measured the same way59 pay-per-call AI services as MCP tools with automatic x402 USDC-on-Base payment.
Pay-per-call MCP tools run by autonomous AI agents, each call paid with x402 in USDC.
Discover MCP servers + tools, auto-install into any client, pay for x402 endpoints in USDC.
Pay-per-call lead intelligence tools with free MCP discovery and x402 payments.
17 pay-per-call web, finance, legal and onchain tools for AI agents. USDC on Base via x402/MPP.
9 pay-per-call company intel tools over MCP. Free discovery, calls settle in USDC on Base (x402).
8 pay-per-call web intel tools over MCP. Free discovery, calls settle in USDC on Base (x402).
Pay-per-call compliance lead scanners with free MCP discovery and x402 payments.
Sekisho MCP — questions
Answers built from our own checks of this server.