Crawlbit

io.github.amati032-devPublished by GitHub account amati032-devv1.0.1Updated Oct 27, 2026

Four free tools to check if AI engines can find, read and recognise a site. No API key.

Overview

AI-generated overview

CrawlBit checks whether AI engines can find, read and recognise a website, exposing four free read-only analysis tools to an assistant.

What you can do
  • Check whether named AI crawlers can read a site via robots.txt
  • Assess whether a brand reads as a clear entity AI can recognise
  • Find where a brand is missing off-page, outside its own site
  • Inspect published structured data for AI shopping readiness
  • Compare two sites on AI crawler access
When to use it
Useful when auditing a site's AI visibility: whether AI crawlers are blocked, whether the brand is recognisable, where third-party mentions are missing, or whether product data is machine-readable. It measures conditions for citation, not actual citations.
Requirements
Node.js 18 or later to run the npm package locally over stdio. No account, API key or signup. Network access to the CrawlBit API; the optional CRAWLBIT_BASE_URL variable points it at another instance.
Before you install
The URL you ask about is sent to the CrawlBit API for analysis; nothing else leaves the machine and nothing is stored. Requests are rate-limited per IP. Results are limited: crawler checks read robots.txt only, entity checks read only the site's own pages, and no tool tests whether AI actually cites a brand.

Installation

In SourceWeft

  1. Open Crawlbit in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.

Other MCP clients

Follow the launch instructions in the repository.

README

CrawlBit MCP

Four free tools that answer one question: can AI engines find, read and recognise a website?

No account. No API key. No signup. Nothing here runs a language model, so nothing here costs you or us anything.

"Can ChatGPT read stripe.com?""Why does AI never mention my store?""Where is my brand missing outside my own site?"

Ask in plain language. Your AI client picks the right tool.


Install

Requires Node.js 18+.

Claude Code

bash
claude mcp add crawlbit -- npx -y crawlbit-mcp

Claude Desktop

Add to claude_desktop_config.json:

json
{  "mcpServers": {    "crawlbit": {      "command": "npx",      "args": ["-y", "crawlbit-mcp"]    }  }}

Cursor

Add to .cursor/mcp.json:

json
{  "mcpServers": {    "crawlbit": {      "command": "npx",      "args": ["-y", "crawlbit-mcp"]    }  }}

Restart your client. Four tools appear.


The four tools

ToolWhat it answers
crawlbit_crawler_watchCan GPTBot, OAI-SearchBot, ClaudeBot, PerplexityBot and Google-Extended read this site?
crawlbit_entity_checkDoes this brand read as a clear entity AI can recognise?
crawlbit_offpage_gapsWhere is this brand missing outside its own website?
crawlbit_shoppingCan AI shopping agents understand and recommend these products?

Try these

Check whether AI crawlers can read example.comDoes example.com read as a clear brand entity to AI?Where is example.com missing off-page, and which gap should we close first?Compare example.com and competitor.com on AI crawler access

The tools compose. A useful sequence is: crawler access first (a blocked crawler makes everything else pointless), then the entity check, then the off-page gaps.


What this does NOT do

Written plainly, because an SEO tool that overstates itself is worse than no tool.

  • It does not test whether AI actually cites a brand. That means running real buyer questions against ChatGPT, Perplexity and Claude, reading the answers, and reporting who gets named instead of you. It costs real money per run and is not part of this free surface. These four tools measure the conditions that make a citation possible, which is a smaller claim.
  • crawler_watch reads robots.txt only. It cannot see blocking done at the CDN, firewall or rate-limit layer. A site can pass here and still refuse the crawler in practice.
  • entity_check reads what the site publishes about itself. It says nothing about the brand's reputation across the rest of the web.
  • shopping inspects published structured data. It cannot see a merchant feed submitted privately to a platform.

If a site scores well on all four and still is not cited, the answer is almost always the same and it is not technical: too few third-party pages mention it. These tools will tell you that honestly rather than sell you a fix that does not exist.


Why only four tools

CrawlBit also runs a full technical audit and generates llms.txt. Both use a language model, so both cost money per run, and neither is exposed here.

That is a deliberate line rather than a teaser. A free tool whose bill grows with its popularity gets rate-limited, degraded or withdrawn the moment it succeeds, and the people who installed it are the ones who pay for that. Everything in this server costs nothing to run, so nothing here has to be taken back later. The audit and the llms.txt generator live at crawlbit.app if you want them.


Rate limit

The API rate-limits per IP. Normal conversational use does not come close, and the server runs on your machine, so the budget is yours rather than shared. If you do hit it, you get a plain sentence rather than a stack trace.


Configuration

VariableDefaultPurpose
CRAWLBIT_BASE_URLhttps://www.crawlbit.appPoint the server at another instance

Privacy

The server runs locally and stores nothing. The only data leaving your machine is the URL you ask about, sent to the CrawlBit API to be analysed. There is no account, so there is nothing to tie a request to a person.


About

Built by CrawlBit, which measures AI visibility and does the off-page work that earns citations. The free tools here are the measurement half. The paid work is the other half, and you are not required to look at it to use this.

MIT licensed. Issues and pull requests welcome.

Source: README.md at commit 0b58ce5

Tools

0
SourceWeft has not started this package in its sandbox yet, so its tools are not known.

Version history

1
  1. v1.0.1LatestSep 16, 2026

Score

50% 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 days25 pts

    Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.

  • Auth declared10 pts

    Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.

  • 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
  • License10 pts