Bot403

com.bot403Published by bot403.comOfficial publisherv1.2.0Updated Oct 24, 2026

Invisible bot shield for HTML forms: the browser solves a proof of work and your server checks it.

VerifiedStreamable HTTPWeb executableSecurity & Monitoring

Overview

AI-generated overview

Remote MCP endpoint that adds an invisible proof-of-work bot shield to HTML forms, letting an assistant integrate and verify the challenge.

What you can do
Bot403 is a remote MCP server for an invisible bot shield aimed at HTML forms. According to its description, the browser solves a proof of work and the server side checks it, so the assistant can help wire up and validate that challenge flow. No individual tools are listed in the manifest, so the exact operations are not documented here.
When to use it
Consider it when you maintain HTML forms and want a bot-protection layer that runs without visible user interaction, and you want an assistant to help integrate or verify the proof-of-work check. It is less relevant if you need documented tool-level capabilities before adopting it.
Requirements
It is a remote streamable HTTP endpoint at bot403.com; nothing is installed locally and no packages are declared. Authentication is OAuth and is required. No environment variables or headers are declared. Network access to the endpoint is needed.
Before you install
OAuth is required, so the assistant will be granted access to whatever the authorization covers; review the scopes before approving. The manifest lists no tools, so what the server can read or change is unclear from this listing. The description does not state whether it writes, sends, or deletes data, or whether form data leaves your systems.

Installation

In SourceWeft

  1. Open Bot403 in the dashboard and add it to a workspace.
  2. Connect the required credentials. They are stored privately and never shown on public pages.
  3. Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/com.bot403%2Fbot403/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config. The client completes OAuth sign-in on first connect.

{
  "mcpServers": {
    "bot403": {
      "type": "http",
      "url": "https://bot403.com/mcp"
    }
  }
}

Tools

0
This server asks you to sign in, so SourceWeft could not read its tools without an account and has not indexed them. What a connected account sees can depend on that account and its permissions.

Version history

1
  1. v1.2.0LatestOct 23, 2026

Score

67% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 daysRequired25 pts
  • Auth declaredRequired10 pts
  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts

    Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.

  • LicenseNot applicable

    A hosted service is used under its provider's terms, so no license is expected here. This check is left out of the percentage.