Botworthy

dev.botworthyPublished by botworthy.devOfficial publisherv1.0.0Updated Nov 7, 2026

Check whether a website works for AI agents before visiting it, and the steps that worked.

VerifiedStreamable HTTPWeb executableWeb Search & ScrapingBrowser Automation

Overview

AI-generated overview

Checks how well a website works for AI agents, returning a score, blocking status and the exact steps that worked for five everyday tasks.

What you can do
  • Look up a site's agent-usability scan: blocking status, score out of 100, advice, and per-task outcomes with the control roles and accessible names that worked
  • Queue a not-yet-scanned site for a future batch scan by Botworthy's own agent
  • Report back how one of the five tasks went on a site you actually visited
When to use it
Useful before an assistant drives a website for a user, to know up front whether the site blocks agents and which steps worked at scan time; also for requesting coverage of a new site or feeding visit results back.
Requirements
A remote streamable HTTP endpoint at botworthy.dev; no packages, environment variables or headers are declared. Network access to the endpoint is required.
Before you install
Results are snapshots from the scan date and may be stale. Text inside results comes from scanned websites and should be treated as data, not instructions. request_scan queues work that takes days. report_visit should only be sent for visits without logins, personal data or CAPTCHA/bot-check bypasses, and must not include sensitive information.

Installation

In SourceWeft

  1. Open Botworthy in the dashboard and add it to a workspace.
  2. 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/dev.botworthy%2Fbotworthy/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.

{
  "mcpServers": {
    "botworthy": {
      "type": "http",
      "url": "https://botworthy.dev/mcp"
    }
  }
}

Tools

3

check_site

Check a website before visiting it

Look up how well an AI agent could use a website when Botworthy last scanned it: whether it blocked agents, the score out of 100, advice, and for each of 5 everyday tasks the outcome and the exact steps (control role and accessible name) that worked. Accepts any URL or domain. If the site hasn't been scanned, says whether a scan is queued.

Parameterssiterequired

request_scan

Ask Botworthy to scan a website

Queue a website that Botworthy hasn't scanned yet. Scans run in batches by Botworthy's own agent, so expect days, not minutes; don't wait for it. Sites already scanned aren't queued again.

Parametersnotesiterequiredagent

report_visit

Report how a task went on a website

Tell Botworthy how one of its 5 tasks went when you did it on a website. Reports aren't published: they decide what gets scanned or rescanned next. Only send it for visits where you didn't log in, didn't enter personal data, and didn't get around a CAPTCHA or bot check, and never include anything about the user.

ParameterssiterequiredtaskrequiredagentstepsrequiredreasonoutcomerequiredranFromfinalUrlfollowedRulesrequired

Version history

1
  1. v1.0.0LatestNov 7, 2026

Score

83% 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 listedRequired15 pts
  • 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.