Skip to main content

Slayer on the Marketplace

The Singularity MCP server exposes 35 tools that let any MCP-compatible AI client (Claude Desktop, Cursor, Windsurf, Claude Code, etc.) interact with the x402Studio marketplace. Browse listings, manage endpoints, process payments, and register agents — all through natural language.

Quick Setup

Add to ~/Library/Application Support/Claude/claude_desktop_config.json:

Authentication

Create PATs at Dashboard > Settings > PAT with granular scopes:
  • mcp:read — List inventory, fetch details and stats
  • mcp:endpoints:write — Update endpoints, manage webhooks
  • mcp:campaigns:write — Create and update fundraiser campaigns
  • mcp:products:write — Update product metadata and pricing
  • mcp:* — Full access

Discovery Tools

Browse and discover marketplace listings without any authentication.

Management Tools

Manage your x402Studio resources programmatically. Requires a PAT.

Payment Tools

Complete payment-backed operations through MCP. These tools handle the x402 challenge-response flow.

How Payment Flows Work

  1. Request — Call the request_* tool to get an x402 payment challenge
  2. Sign — The AI client’s wallet signs the USDC payment on-chain
  3. Complete — Call the corresponding completion tool with the X-Payment payload
  4. Done — The resource is created, topped up, or purchased

Agent Registry Tools

Wallet-session tools for ERC-8004 and Solana-8004 agent management.
MCP never holds wallet private keys. The wallet signs locally, and MCP exchanges the signature for a short-lived session token.

MCP Resources

Static resources available via the MCP resource protocol:

Security

  • Secrets never touch the AI model — PATs and API keys are passed per-request to the MCP server and never stored. They are used only for authentication and immediately discarded after the request completes.
  • No secret logging — Token values are never written to logs, analytics, or any persistent storage on the MCP server.
  • Prompt injection safe — Because secrets are handled at the transport layer (HTTP headers), they cannot be extracted through prompt injection attacks against the AI client.
  • Scoped access — Read-only PATs (mcp:read) cannot perform writes. Endpoint-write PATs cannot mutate products (and vice versa).
  • Instant revocation — Revoked or expired PATs are rejected immediately. Revoke from Dashboard > Settings > PAT at any time.
  • Owner isolation — All tool calls are scoped to the authenticated owner’s resources. You cannot access another user’s data.

Server Info

Full MCP Documentation

See the complete MCP server reference for advanced usage, direct API testing, and detailed parameter schemas.