io.github.sharozdawa/robotstxt-ai
NPM · ROBOTSTXT-AI-MCP · SCANNED AUG 3
Analyze and generate robots.txt with AI crawler detection for 20+ bots like GPTBot and ClaudeBot.
Available components
How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score →
Supply Chain Security86
- No malware found by supply-chain analysis.Pass
- Only part of the dependency tree could be resolved (94 of 98), so this covers what we could see, not the whole tree.Partial
- No install/post-install scripts declared.Pass
- Only part of the dependency tree could be resolved (94 of 98), so this covers what we could see, not the whole tree. View diagnostics → Partial
Provenance & Transparency45
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Provenance check failed: no build-provenance attestation is published. See how to fix → View diagnostics → Fail
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 134 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability77
- AI-judged instruction clarity (excellent).Pass
- Tool/resource definitions use about 355 tokens (~71/item across 5 items; 5 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management23
- Stability observed for 7 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Add this component to your MCP client. Where a client-specific snippet is available, pick your client below and copy it straight into your config; otherwise use the connection detail shown.
npm · robotstxt-ai-mcp
claude mcp add sharozdawa-robotstxt-ai -- npx -y robotstxt-ai-mcp
codex mcp add sharozdawa-robotstxt-ai -- npx -y robotstxt-ai-mcp
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"sharozdawa-robotstxt-ai": {
"type": "local",
"command": [
"npx",
"-y",
"robotstxt-ai-mcp"
],
"enabled": true
}
}
} openclaw mcp add sharozdawa-robotstxt-ai --command npx --arg -y --arg robotstxt-ai-mcp
mcp_servers:
sharozdawa-robotstxt-ai:
command: "npx"
args: ["-y", "robotstxt-ai-mcp"] {
"mcpServers": {
"sharozdawa-robotstxt-ai": {
"command": "npx",
"args": [
"-y",
"robotstxt-ai-mcp"
]
}
}
} Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 3 Aug 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 20 to 23. That category is still filling its 30-day observation window: 6 days of observed history at the previous scan, 7 at this one. The score rises as the window fills, whether or not the server changes.
- 2 Aug 26 +47
- Provenance: unverified → fail ▼ security
- Known CVEs: unverified → partial ▲ security
- Install scripts: unverified → pass ▲ security
- Malware scan: unverified → pass ▲ security
- License: unverified → pass ▲ functional
- Stability: unverified → 0.20 ▲ functional
- MCP protocol: unverified → pass ▲ functional
- Maintenance: unverified → pass ▲ functional
- Dependency health: unverified → partial ▲ functional
- Schema quality: unverified → excellent ▲ functional
- Licence: MIT functional
- 31 Jul 26 −7
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 30 Jul 26 −40
- Known CVEs: partial → unverified ▼ security
- Malware scan: pass → unverified ▼ security
- Provenance: fail → unverified ▼ security
- Install scripts: pass → unverified ▼ security
- License: pass → unverified ▼ functional
- Dependency health: partial → unverified ▼ functional
- Maintenance: pass → unverified ▼ functional
- Licence: MIT functional
- 28 Jul 26 +22
- Provenance: unverified → fail ▼ security
- Known CVEs: unverified → partial ▲ security
- Install scripts: unverified → pass ▲ security
- Maintenance: unverified → pass ▲ functional
- Dependency health: unverified → partial ▲ functional
- License: unverified → pass ▲ functional
- Licence: MIT functional
- 27 Jul 26 46
First indexed and scored.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 3 Aug 2026 · Analysed npm/[email protected]
Provenance none
Ecosystem: npm · Outcome: none
Dependencies 94 packages
94 packages in the resolved dependency tree · 94 deprecated · 29 stale.
The dependency tree was only partially resolved, so these counts may be incomplete.
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability.
analyze_robots ~41
Analyze pasted robots.txt content. Returns which AI bots are blocked or allowed based on the rules.
| Name | Type | Req | Description |
|---|---|---|---|
| content | string | yes | The robots.txt content to analyze |
No output schema declared.
No examples provided.
check_bot_status ~86
Check if a specific bot is blocked or allowed on a given website by fetching and analyzing its robots.txt.
| Name | Type | Req | Description |
|---|---|---|---|
| bot_name | string | yes | The bot user-agent string to check (e.g. 'GPTBot', 'ClaudeBot'). Use list_ai_bots to see available names. |
| url | string | yes | The website URL to check (e.g. https://example.com) |
No output schema declared.
No examples provided.
fetch_robots ~52
Fetch and analyze a robots.txt file from a URL. Returns which AI bots are blocked or allowed.
| Name | Type | Req | Description |
|---|---|---|---|
| url | string | yes | The website URL to fetch robots.txt from (e.g. https://example.com) |
No output schema declared.
No examples provided.
generate_robots ~142
Generate a robots.txt file with specified blocked bots, sitemap URLs, and custom rules.
| Name | Type | Req | Description |
|---|---|---|---|
| block_all_ai | boolean | — | If true, blocks all known AI crawlers (but not search engines like Googlebot) |
| blocked_bots | array | — | Array of bot user-agent strings to block (e.g. ['GPTBot', 'ClaudeBot', 'CCBot']). Use list_ai_bots to see available user-agents. |
| custom_rules | string | — | Additional custom robots.txt rules to append (raw robots.txt syntax) |
| sitemap_urls | array | — | Array of sitemap URLs to include (e.g. ['https://example.com/sitemap.xml']) |
No output schema declared.
No examples provided.
list_ai_bots ~34
List all known AI bots with their user-agents, companies, and descriptions. Useful for deciding which bots to block.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.