← Registry

General Tools

botx402.io

Provides general-purpose tools through the Model Context Protocol.

x402 supported1 endpoint4 known toolsFirst detected October 5, 2026Last detected October 5, 2026

ENDPOINT 1

https://api.botx402.io/mcp

No auth detected

MCP server metadata

Name
botx402
Version
0.1.0
Capabilities
tools
Server instructions

botx402 runs paid analysis bots for a human buyer. Flow: call list_bots, then validate_<bot>_inputs with {"inputs": {...}} until it says the inputs are valid (free, nothing is charged; it lists every problem at once), then start_<bot> with the same JSON plus the buyer's "email". start_<bot> never charges anyone; it returns a Stripe checkout link that a person opens and pays. Show the user the link and ask them to pay; nothing runs until they do. Then call get_run with the receipt_id and access_token from start_<bot> until the status is completed.

Known tools 4

list_bots

List the bots this server can run: what each one does, its price per run, what a run returns, its input schema, and the names of its validate_ and start_ tools.

Inferred read-only
validate_inventory_reorder_inputs

Check inputs for Inventory Reorder Snapshot before asking a human to pay.

Potential side effects
start_inventory_reorder

Start a paid Inventory Reorder Snapshot run ($19.

Inferred read-only
get_run

Check a run started with a start_ tool and fetch its results.

Inferred read-only

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.botx402]
url = "https://api.botx402.io/mcp"
enabled = true
Claude Code

.mcp.json

{
  "mcpServers": {
    "botx402": {
      "type": "http",
      "url": "https://api.botx402.io/mcp"
    }
  }
}
Claude Desktop

Settings → Connectors → Add custom connector

Name: botx402
Remote MCP URL: https://api.botx402.io/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": {
    "botx402": {
      "url": "https://api.botx402.io/mcp"
    }
  }
}
Visual Studio Code

.vscode/mcp.json

Add to Visual Studio Code
{
  "servers": {
    "botx402": {
      "type": "http",
      "url": "https://api.botx402.io/mcp"
    }
  }
}
Generic MCP

Client-specific MCP configuration

{
  "name": "botx402",
  "transport": "streamable-http",
  "url": "https://api.botx402.io/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.