Koskamo

Bot403 MCP

An official MCP server that allows AI assistants to automate the setup of Bot403 bot protection for HTML forms. It enables agents to create sites, manage configurations, retrieve statistics, and verify form tokens programmatically, streamlining the integration of invisible bot shields without manual CAPTCHA challenges.

Endpoint and access

OAuth sign-in: the first time you connect, your client opens the vendor's own authorization prompt in a browser.

Bot403 MCP logo, by Bot403Vendor evidenceStreamable HTTPOAuth sign-inEndpoint checked 2026-11-01Operated by Bot403
You need:the site owner signs in at https://bot403.com/login and makes the key under Account, API keysSend the key as Authorization: Bearer sk_live_…Make the key under Account, API keys, with only the scopes the app needs
MCP endpoint (Streamable HTTP)
https://bot403.com/mcp
Vendor documentation

What you can do with it

  • Protect contact forms with invisible bot shield
  • Create and manage Bot403 sites via AI assistant
  • Verify form submission tokens programmatically
  • Check submission statistics and quota usage

Source and maintenance

Vendor evidenceRegistry 1.2.0

Tools

Reported by the attributed source; not independently observed by Koskamo.

No tool definitions available.

30-day availability

Aggregated from read-only remote checks; this is not a tool-execution or security guarantee.

Successful checks
1 of 1 (100%)
Average latency
787 ms
95th percentile latency
787 ms

Maintenance history

Public check and source-refresh events. Editorial and ownership records remain private.

  • · probe · passed · 787 ms · metadata changed · refuses unauthenticated initialize (HTTP 401)

Connect from your client

Each snippet registers the same endpoint; pick the client you use.

This server is operated by the named third party. Listing and endpoint checks are not an endorsement or a security audit. Review the operator's permissions, terms, and data handling before connecting. How listings are checked and corrected.

Claude Code

Run this once in a terminal. It registers the remote server. Use --scope project to write .mcp.json for the repo.
Claude Code configuration
claude mcp add --transport http bot403-mcp https://bot403.com/mcp

Codex

Run this once. Codex stores MCP servers in ~/.codex/config.toml (or .codex/config.toml in a trusted project).
Codex configuration
codex mcp add bot403-mcp --url https://bot403.com/mcp

Cursor

Merge this server into .cursor/mcp.json in your project, then enable bot403-mcp in your MCP settings.
Cursor configuration
{
  "mcpServers": {
    "bot403-mcp": {
      "url": "https://bot403.com/mcp"
    }
  }
}

Cline

Merge this into cline_mcp_settings.json (Cline → MCP Servers → Configure).
Cline configuration
{
  "mcpServers": {
    "bot403-mcp": {
      "type": "streamableHttp",
      "url": "https://bot403.com/mcp",
      "disabled": false
    }
  }
}

VS Code

Merge this server into .vscode/mcp.json. Use MCP: List Servers to start bot403-mcp and inspect its tools.
VS Code configuration
{
  "servers": {
    "bot403-mcp": {
      "type": "http",
      "url": "https://bot403.com/mcp"
    }
  }
}

Gemini CLI

Run this once. It writes .gemini/settings.json in the current project; pass --scope user for ~/.gemini/settings.json.
Gemini CLI configuration
gemini mcp add --transport http bot403-mcp https://bot403.com/mcp

Claude Desktop

Merge this into claude_desktop_config.json (macOS: ~/Library/Application Support/Claude/, Windows: %APPDATA%\Claude\), then restart Claude Desktop.
Claude Desktop configuration
{
  "mcpServers": {
    "bot403-mcp": {
      "url": "https://bot403.com/mcp"
    }
  }
}

Windsurf

Merge this into ~/.codeium/windsurf/mcp_config.json, then refresh MCP in Cascade. Windsurf remote servers use serverUrl, not url.
Windsurf configuration
{
  "mcpServers": {
    "bot403-mcp": {
      "serverUrl": "https://bot403.com/mcp"
    }
  }
}

Let your agent find its tools

Find servers like Bot403 MCP from your agent. Add Koskamo once to search the index for endpoints, access requirements, and client setup. Public discovery needs no key.

Do you run Bot403 MCP?

Prove ownership with a DNS record, a well-known file, or your Official MCP Registry entry, and your edits publish immediately. Proofs are re-checked weekly; admins can still hide or remove a listing.

Claim this listing