What shipped

Eight stdio MCP packages on npm, one per live cluster, covering every endpoint already callable as HTTP at x402.agentutility.ai. Plus a catalog page at mcp.agentutility.ai.

| Package | Cluster | Tools | |---|---|---| | @agentutility/mcp-mediakit | PDF, image, audio, video, OCR | 50 | | @agentutility/mcp-wordmint | Text, language, classification | 44 | | @agentutility/mcp-web-probe | Scraping, search, archives, DNS, OSINT | 43 | | @agentutility/mcp-edge-market | Onchain risk, DEX depth, wallet PnL, gas, bridges | 37 | | @agentutility/mcp-locale | Geo, addresses, country / city data, timezones | 26 | | @agentutility/mcp-edge-finance | SEC filings, 13F deltas, BLS, prediction-markets | 21 | | @agentutility/mcp-synthforge | Image / video / music / voice generation | 14 | | @agentutility/mcp-prooflayer | Repo trust, deploy config, dependency risk | 13 |

248 tools across 8 clusters. Comppoint stays a spec cluster (eBay / PSA / Scryfall / TCGplayer all forbid commercial resale); card-resolve ships under Wordmint.

Why stdio, not a hosted remote MCP

Hosting a remote MCP server that holds customer USDC introduces real custody risk — hot wallet drain, ledger compromise, deploy-key theft. The market for "agents that can't custody but want our endpoints via MCP" is small today. Most agent traffic runs on local clients — Claude Desktop, Cursor, Cline, Claude Code, custom agents — where stdio works perfectly.

So v1 is stdio. Each package runs on the agent's machine. The agent's wallet stays on the agent's machine. We hold nothing.

A hosted remote MCP at mcp.agentutility.ai/mcp is reserved for v2. It comes back on the table when either (a) the MCP spec ships native x402 payment handoff, or (b) we choose to take on custody work properly. See /mcp/remote/.

How discovery works

MCP discoverability doesn't require a hosted remote server. The 8 stdio packages are indexed by:

  • npm registry — npm search @agentutility
  • Smithery, Glama, mcpservers.org, mcp.so
  • Anthropic's MCP directory + Cursor's MCP catalog
  • Coinbase's x402 directory
  • The new catalog page at mcp.agentutility.ai

Every stdio call also sets X-Agent-Channel: mcp-stdio-<cluster> and X-Agent-Id: 47167, so the dashboard now buckets MCP-driven traffic separately from direct HTTP. We can see exactly which clusters MCP is moving.

Install (Claude Desktop)

Edit ~/Library/Application Support/Claude/claude_desktop_config.json: 

{
  "mcpServers": {
    "agentutility-mediakit": {
      "command": "npx",
      "args": ["-y", "@agentutility/mcp-mediakit"],
      "env": { "X402_PRIVATE_KEY": "0xYOUR_KEY" }
    }
  }
}

Restart Claude Desktop. 50 PDF / image / video / audio tools appear. Fund the wallet address with USDC on Base. Call any tool.

Same shape for Cursor (.cursor/mcp.json), Cline, Claude Code, and any other MCP-aware agent.

What changed in the system

  • New: packages/mcp-<slug>/ × 8 — auto-generated from bankr.x402.json
  • New: scripts/generate-mcp-clusters.mjs — codegen + drift gate hooked into the existing sync-bankr-manifest test
  • New: mcp.agentutility.ai — Cloudflare Pages custom domain, 301 to agentutility.ai/mcp/
  • Extended: cdp-deploy/migrations/0002_agent_channel.sql + request-log.ts — X-Agent-Channel + X-Agent-Id header capture
  • Extended: cdp-deploy /api/channels — per-channel rollup over a configurable window
  • Unchanged: bankr.x402.json (cluster field was already there), docs/cluster-map.json, site/lib/clusters.ts

The unpublished mcp-server/ kitchen sink stays in the repo as a rollback reference. A follow-up PR deletes it after a week of green smoke.

Source