Robots Txt Ai Crawler Audit

io.github.jmshinhwaPublished by GitHub account jmshinhwav0.1.3Updated Oct 25, 2026

Checks robots.txt line by line and says what each AI crawler token actually controls - training, AI

The publisher's own server: audit.domains - Domain Valuation

VerifiedSTDIODesktop onlyWeb Search & Scraping

Overview

AI-generated overview

Local MCP server that audits a robots.txt file line by line and explains what each AI crawler token actually controls.

What you can do
  • Audit a robots.txt file line by line, checking each directive against AI crawler tokens.
  • Explain what each AI crawler token actually controls, such as training versus other AI uses.
  • Report findings so an assistant can discuss which crawlers are allowed or blocked.
When to use it
Useful when you want to know whether a site's robots.txt permits or blocks AI crawlers, for example before publishing content or reviewing crawler policy.
Requirements
Runs as a local process on the user's machine via npx from the npm package; desktop only, no web version. No authentication, environment variables or headers are declared.
Before you install
The supplied README does not describe this tool's usage and instead contains unrelated theme-project text, so verify what the package actually does before running it. No credentials are declared.

Installation

In SourceWeft

  1. Open Robots Txt Ai Crawler Audit 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

readystack-themes

Made by ReadyStack · free calculators and templates at getreadystack.com VS Code themes by ReadyStack

Source: README.md at commit ee1c884

Tools

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

Version history

2
  1. v0.1.3LatestSep 19, 2026
  2. v0.1.1Sep 16, 2026

Score

40% 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

    Declare a license in the repository or the registry entry.

Other Audit integrations