Connect Quartermaster

One MCP endpoint, all tools, per-call USDC pricing. Free tools work for everyone; paid tools return payment instructions unless the client carries an x402 wallet.

Claude Code (CLI)

claude mcp add --transport http quartermaster https://quartermaster.surewhynot.app/mcp

Claude.ai / Claude Desktop

Settings → Connectors → Add custom connector → paste https://quartermaster.surewhynot.app/mcp

Cursor / Windsurf / any MCP-client config

{
  "mcpServers": {
    "quartermaster": { "url": "https://quartermaster.surewhynot.app/mcp" }
  }
}

Test drive (free, no wallet)

After adding the server, paste these into Claude. They use free tools and work immediately, no wallet or payment:

List Quartermaster's tools.
Use Quartermaster to generate 3 UUIDs.
Use Quartermaster to give me the current time in Tokyo.
Use Quartermaster to SHA-256 hash the word "hello".
Show me Quartermaster's x402 test vector.

Paid tools (web extraction, DNS, transaction status, AI, and more) will report that they need payment in a standard Claude client. That is expected, not a failure - see below to enable paying.

Which tools work without a wallet? The free ones — current_time, generate_uuid, hash_string, http_errors_list, x402_test_vector, quartermaster_info — work in Claude, Cursor, or any MCP client right now, no setup. The paid tools need a crypto wallet, and here is the honest part: Claude Desktop and Claude.ai have no built-in wallet, so calling a paid tool there returns a "payment required" result rather than paying. That is expected — it is a limit of the client, not this server.

How to actually pay for the paid tools

Two real paths today, both requiring a funded USDC wallet on Base (a dollar covers hundreds of calls):

From code — an agent or script using the @x402/mcp or @x402/fetch client pays automatically (see the snippets below). This is how autonomous agents — the real paying customers — consume the API.
Inside Claude Desktop — run a small local "paying bridge": an MCP server on your machine that holds your wallet, that Claude connects to, and that forwards calls to Quartermaster while signing the payments. Claude never sees the key; the bridge pays. Ask if you want this — it is the way a human uses the paid tools through a chat client while the ecosystem's native wallet support is still early.

Agents that pay automatically (x402)

import { createx402MCPClient } from "@x402/mcp";
import { ExactEvmScheme } from "@x402/evm/exact/client";
import { StreamableHTTPClientTransport } from "@modelcontextprotocol/sdk/client/streamableHttp.js";
import { privateKeyToAccount } from "viem/accounts";

const client = createx402MCPClient({
  name: "my-agent", version: "1.0.0", autoPayment: true,
  schemes: [{ network: "eip155:*", client: new ExactEvmScheme(privateKeyToAccount(KEY)) }],
});
await client.connect(new StreamableHTTPClientTransport(new URL("https://quartermaster.surewhynot.app/mcp")));
const result = await client.callTool("web_extract", { url: "https://example.com" });

Plain HTTP (no MCP)

import { wrapFetchWithPaymentFromConfig } from "@x402/fetch";
// ...same wallet setup...
const payFetch = wrapFetchWithPaymentFromConfig(fetch, { schemes });
const res = await payFetch("https://quartermaster.surewhynot.app/v1/extract?url=https://example.com");

Full endpoint list and prices: all tools · OpenAPI spec · llms.txt

Where else Quartermaster is listed

Coinbase x402 Bazaar (search "Quartermaster"), x402scan, and 402index (domain-verified). Uptime: public status page — self-tested daily with a real settled payment.