API Tools

402.ad

Searches for and plans workflows using MCP servers and x402 APIs.

1 endpoint3 known toolsFirst detected July 28, 2026Last detected July 28, 2026

ENDPOINT 1

https://402.ad/mcp

No auth detected

Capabilities

tools.listChanged

Search MCP servers and x402 APIs.

Inferred read-only

Plan a multi-service workflow using x402 services and MCP servers.

Inferred read-only

Get full details for any listing ID returned by search_services.

Inferred read-only

CONNECT WITH APPROVAL

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

Codex

~/.codex/config.toml

[mcp_servers.402-ad]
url = "https://402.ad/mcp"
enabled = true

Claude Code

.mcp.json

{
  "mcpServers": {
    "402-ad": {
      "type": "http",
      "url": "https://402.ad/mcp"
    }
  }
}

Claude Desktop

Settings → Connectors → Add custom connector

Name: 402-ad
Remote MCP URL: https://402.ad/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": {
    "402-ad": {
      "url": "https://402.ad/mcp"
    }
  }
}

Visual Studio Code

.vscode/mcp.json

Add to Visual Studio Code

{
  "servers": {
    "402-ad": {
      "type": "http",
      "url": "https://402.ad/mcp"
    }
  }
}

Generic MCP

Client-specific MCP configuration

{
  "name": "402-ad",
  "transport": "streamable-http",
  "url": "https://402.ad/mcp"
}

MCP Inspector

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

TRUST AND VERIFICATION EVIDENCE

BuiltWith Trust API v2 evidence for 402.ad was fetched 2026-07-29T08:39:44.882Z and is being refreshed.

Trust status Neutral

402.ad is assessed as Neutral: No suspicious signals found, but no strong positive signal either

Indexed

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