grokzilla.shop / mcp

Remote MCP server

Pay-per-call tools over x402 (USDC on Base, eip155:8453). Discovery tools list_skills and get_skill are free. This server does not pay and does not hold a wallet key.

Streamable HTTP URL: https://grokzilla.shop/mcp

Responses are JSON. There is no SSE stream and no session. GET /mcp returns 405. Paid calls do not use an HTTP 402; the challenge is inside the tool result.

Live payTo in this process: 0xc22f9CAEBAc37fE72D5142f35f21f6696Ea9Ef69. Asset: USDC 0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913.

Add it to an MCP client

Use the Streamable HTTP URL. A typical client entry:

{
  "mcpServers": {
    "grokzilla-micro-pay": {
      "url": "https://grokzilla.shop/mcp"
    }
  }
}

After initialize, send the notification notifications/initialized (the server answers HTTP 202), then tools/list.

Clients without x402

initialize and tools/list succeed. A paid tools/call returns isError: true and a PaymentRequired object in structuredContent (x402 version 2, scheme exact, USDC on Base). The skill handler does not run. Stop. The server will not pay on your behalf.

Clients that pay with x402

Python x402.mcp and TypeScript @x402/mcp read that challenge, sign an exact USDC payment on Base, and retry tools/call with _meta["x402/payment"]. The server verifies and settles through its facilitator, runs the same handler as the HTTP route, and returns _meta["x402/payment-response"].

The HTTP x-master-token bypass does not apply here.

curl

curl -sS https://grokzilla.shop/mcp \
  -H 'Content-Type: application/json' \
  -H 'Accept: application/json, text/event-stream' \
  -d '{"jsonrpc":"2.0","id":1,"method":"initialize","params":{"protocolVersion":"2025-06-18","capabilities":{},"clientInfo":{"name":"curl","version":"0.0.1"}}}'
curl -sS https://grokzilla.shop/mcp \
  -H 'Content-Type: application/json' \
  -H 'Accept: application/json, text/event-stream' \
  -d '{"jsonrpc":"2.0","id":2,"method":"tools/list"}'

Paid tools (19)

One tool per public catalog skill. The price column is the catalog price. The MCP challenge amount matches the HTTP 402 for that skill. Token counts from token_count are approximate.

MCP toolpriceHTTP
ai_detector $0.01 POST /api/skills/ai-detector
json_flatten $0.006 POST /api/skills/json-flatten
json_sort $0.003 POST /api/skills/json-sort
text_diff $0.006 POST /api/skills/text-diff
html_clean $0.008 POST /api/skills/html-clean
json_schema_validate $0.006 POST /api/skills/json-schema-validate
keyword_extract $0.008 POST /api/skills/keyword-extract
token_count $0.004 POST /api/skills/token-count
sha256 $0.003 POST /api/skills/sha256
uuid_mint $0.003 POST /api/skills/uuid-mint
slugify $0.003 POST /api/skills/slugify
pii_redact $0.003 POST /api/skills/pii-redact
csv_normalize $0.003 POST /api/skills/csv-normalize
base64 $0.003 POST /api/skills/base64
epoch_convert $0.003 POST /api/skills/epoch-convert
url_to_markdown $0.003 POST /api/skills/url-to-markdown
token_risk $0.005 POST /api/skills/token-risk
json_repair $0.0041 POST /api/skills/json-repair
cron_next $0.0031 POST /api/skills/cron-next

Also