AI Crawler Access Checker

io.github.Nero-EnginePublished by GitHub account Nero-Enginev0.1.0Updated Nov 1, 2026

Shows if GPTBot, ClaudeBot, PerplexityBot and other AI crawlers can read each site in a list.

VerifiedStreamable HTTPWeb executableWeb Search & Scraping

Overview

AI-generated overview

Apify-hosted remote MCP server that checks whether AI crawlers such as GPTBot, ClaudeBot and PerplexityBot can read each site in a list.

What you can do
  • Check AI crawler access for a list of sites, reporting whether crawlers like GPTBot, ClaudeBot and PerplexityBot are allowed to read each one.
  • Return per-site results for a batch of domains so access can be compared across a list.
When to use it
Useful when you want to know whether AI crawlers are blocked from your own or others' sites, for example before publishing content or auditing robots and crawler policies across several domains.
Requirements
A remote endpoint at mcp.apify.com over streamable HTTP, with OAuth authentication and an Apify API token sent in the Authorization header as a Bearer token. An Apify account is needed, and runs are billed per event.
Before you install
The Authorization header carries your Apify API token, a secret. Runs are billed per event to your Apify account, so repeated checks cost money. Site lists you submit are processed by the Apify-hosted service.

Installation

In SourceWeft

  1. Open AI Crawler Access Checker 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/io.github.Nero-Engine%2Fai-crawler-access-checker/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": {
    "ai-crawler-access-checker": {
      "type": "http",
      "url": "https://mcp.apify.com/?tools=nerolabs/ai-crawler-access-checker"
    }
  }
}

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. v0.1.0LatestNov 1, 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.