API Tools

code402.dev

Provides tools to list, retrieve, probe, and register services on the code402 payment gateway, which handles x402-compliant API monetization.

1 endpoint8 known toolsFirst detected August 21, 2026Last detected August 21, 2026

ENDPOINT 1

https://mcp.code402.dev/mcp

No auth detected

MCP server metadata

Name: code402-mcp-server
Version: 1.0.0

Capabilities

tools.listChanged

Known tools 8

code402_list_services

List services on the code402 gateway storefront (GET /v1/services): first-party APIs and third-party seller listings, each with method, URL, USDC price, and network.

Inferred read-only

code402_get_service

Fetch a single service from the code402 storefront by its serviceId (as returned by code402_list_services).

Inferred read-only

code402_probe_endpoint

Send an unpaid GET to any public https URL and report whether it answers with a valid x402 402 challenge, plus normalized terms { scheme, network, amount (USDC base units), price (dollars), payTo, asset }.

Potential side effects

code402_gateway_health

Check the code402 gateway's /healthz: returns { status, service, network } where network is the settlement chain currently configured (e.

Inferred read-only

code402_register_seller

Register a seller on the code402 gateway (or update its name — the payout wallet is immutable once set; re-binding requires EIP-191 proof): POST /v1/sellers with { id, wallet, name }.

Potential side effects

code402_create_listing

Create or update a paid listing for a registered seller: POST /v1/sellers/{sellerId}/services with { serviceId, upstream_url, price_usd, method?

Potential side effects

code402_get_seller_analytics

Fetch a seller's own settlement analytics (free): GET /v1/sellers/{sellerId}/analytics.

Inferred read-only

code402_get_seller_invoice

Compute a seller's platform-fee invoice from settled receipts: GET /v1/sellers/{sellerId}/invoice?

Potential side effects

CONNECT WITH APPROVAL

Client installation

Review this server and its permissions before adding it. Secret placeholders must be set locally.

Codex

~/.codex/config.toml

[mcp_servers.code402-mcp-server]
url = "https://mcp.code402.dev/mcp"
enabled = true

Claude Code

.mcp.json

{
  "mcpServers": {
    "code402-mcp-server": {
      "type": "http",
      "url": "https://mcp.code402.dev/mcp"
    }
  }
}

Claude Desktop

Settings → Connectors → Add custom connector

Name: code402-mcp-server
Remote MCP URL: https://mcp.code402.dev/mcp

Add this remote URL as a custom connector in Claude Desktop. Availability depends on the user plan and workspace policy.

Cursor

.cursor/mcp.json

{
  "mcpServers": {
    "code402-mcp-server": {
      "url": "https://mcp.code402.dev/mcp"
    }
  }
}

Visual Studio Code

.vscode/mcp.json

Add to Visual Studio Code

{
  "servers": {
    "code402-mcp-server": {
      "type": "http",
      "url": "https://mcp.code402.dev/mcp"
    }
  }
}

Generic MCP

Client-specific MCP configuration

{
  "name": "code402-mcp-server",
  "transport": "streamable-http",
  "url": "https://mcp.code402.dev/mcp"
}

MCP Inspector

Run the official MCP Inspector locally and enter the indexed Streamable HTTP endpoint.

TRUST AND VERIFICATION EVIDENCE

Loading Trust v2 evidence…

Checking the associated registrable domain. The BuiltWith key remains server-side.

Indexed

Evidence is source-attributed and does not guarantee that a third-party server is safe. Risk labels are conservative metadata heuristics.