Crawlerpeek
NPM · CRAWLERPEEK
Check whether AI crawlers (GPTBot, ClaudeBot, PerplexityBot) can access a URL. Read-only.
Available components
Last scanned (21 hours ago)
Scores higher than 48% of npm servers
Category Web Scraping
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 → Why this is hard to score →
Supply Chain Security100
- No malware found by supply-chain analysis.Pass
- No known CVEs affecting this package version or its production dependencies.Pass
- No install/post-install scripts declared.Pass
- No production dependencies, so there is no dependency health to assess. View diagnostics → Pass
Provenance & Transparency48
- 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 5 days ago).Pass
- Publishes a security disclosure policy (SECURITY.md).Pass
Schema Quality & AI Usability68
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 1119 tokens (~186/item across 6 items; 6 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management33
- Stability observed for 10 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
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 6 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 6 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
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.
- 2 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 23 to 27. That category is still filling its 30-day observation window: 7 days of observed history at the previous scan, 8 at this one. The score rises as the window fills, whether or not the server changes.
- 31 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 17 to 20. That category is still filling its 30-day observation window: 5 days of observed history at the previous scan, 6 at this one. The score rises as the window fills, whether or not the server changes.
- 30 Oct 26 +15
- Malware scan: unverified → pass ▲ security
- 29 Oct 26 −14
- Malware scan: pass → unverified ▼ security
- Schema quality: 746 → 1119 ▼ functional
- Package version: 0.2.0 → 0.3.1 functional
- 27 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 3 to 7. That category is still filling its 30-day observation window: 1 days of observed history at the previous scan, 2 at this one. The score rises as the window fills, whether or not the server changes.
- 26 Oct 26 +11
- Known CVEs: unverified → pass ▲ security
- Dependency health: unverified → pass ▲ functional
- 25 Oct 26 59
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 4 Nov 2026 · Analysed npm/crawlerpeek@0.3.1
Provenance No attestation
The registry publishes no build provenance for this version, so there is nothing to verify.
| Result | No attestation |
|---|---|
| Ecosystem | npm |
Background: How many MCP packages publish verified provenance →
Dependencies 0 packages
| Packages resolved | 0 |
|---|---|
| Tree resolution | Complete |
Background: SBOMs and build attestations, explained →
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. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
check_ai_access ~232
Check whether AI crawlers (GPTBot, ClaudeBot, PerplexityBot, Google-Extended and others) may access a URL: robots.txt decision per bot plus the live HTTP status when the page is fetched with each bot's user-agent string. Read-only; one request per bot.
| Name | Type | Req | Description |
|---|---|---|---|
| bots | array | – | Bot tokens to check, or omit for the default 15. Known: GPTBot, OAI-SearchBot, ChatGPT-User, ClaudeBot, Claude-SearchBot, Claude-User, PerplexityBot, Perplexity-User, Google-Extended, Applebot-Extend… |
| http | boolean | – | Also fetch the page with each bot's user agent (default true). false checks robots.txt only. |
| url | string | yes | Public http(s) URL of the page to check. |
No output schema declared.
No examples provided.
generate_robots_txt ~93
Generate a robots.txt that welcomes AI crawlers, with optional disallowed paths and bots to close. Pure text generation; makes no network requests.
| Name | Type | Req | Description |
|---|---|---|---|
| block_bots | array | – | Bot tokens to close completely, e.g. ["CCBot"]. |
| disallow | array | – | Paths no bot should fetch, e.g. ["/admin/"]. |
| sitemap | string | – | Absolute sitemap URL. |
No output schema declared.
No examples provided.
lint_robots_txt ~127
Lint a robots.txt for mistakes: HTML served instead of robots.txt, misspelled fields or bot tokens, rules before any User-agent, relative paths or sitemap URLs, duplicate or empty groups, directives Google ignores, every AI crawler blocked. Give the site's URL (fetches its /robots.txt) or the file's text. Findings carry stable codes, line numbers and a severity.
| Name | Type | Req | Description |
|---|---|---|---|
| text | string | – | The robots.txt content to lint, instead of url. |
| url | string | – | Public http(s) URL of the site; its /robots.txt is fetched. |
No output schema declared.
No examples provided.
scan_site ~246
Check robots.txt for many pages of one site at once: takes the URLs from its sitemap (listed in robots.txt, else /sitemap.xml; a sitemap index is followed one level) and reports per bot which URLs robots.txt blocks. Same host only, up to 200 URLs, .gz sitemaps are skipped. Read-only; fetches only robots.txt and the sitemap files, never the pages.
| Name | Type | Req | Description |
|---|---|---|---|
| bots | array | – | Bot tokens to check, or omit for the default 15. Known: GPTBot, OAI-SearchBot, ChatGPT-User, ClaudeBot, Claude-SearchBot, Claude-User, PerplexityBot, Perplexity-User, Google-Extended, Applebot-Extend… |
| limit | integer | – | How many sitemap URLs to check (default 25). |
| url | string | yes | Public http(s) URL on the site to scan. |
No output schema declared.
No examples provided.
see_as_bot ~197
Fetch one URL with a single bot's user-agent string from this machine and report status, final URL after redirects (max 5), content type, size, page title and whether the response looks like a block or challenge page. Does not prove what the real bot gets (operators verify IP ranges).
| Name | Type | Req | Description |
|---|---|---|---|
| bot | string | yes | Bot token, for example GPTBot. Known: GPTBot, OAI-SearchBot, ChatGPT-User, ClaudeBot, Claude-SearchBot, Claude-User, PerplexityBot, Perplexity-User, Google-Extended, Applebot-Extended, CCBot, meta-ex… |
| url | string | yes | Public http(s) URL. |
No output schema declared.
No examples provided.
verify_bot_ip ~224
Check whether an IP address really belongs to a crawler (for example one seen in server logs claiming to be Googlebot), using only what the operator documents: its published IP-range list or forward-confirmed reverse DNS. Without bot, checks every bot that has such a method. Reads the operators' public lists; never connects to the IP. verified null means it could not be decided.
| Name | Type | Req | Description |
|---|---|---|---|
| bot | string | – | Bot token to verify against, for example Googlebot. Omit to check all. Known: GPTBot, OAI-SearchBot, ChatGPT-User, ClaudeBot, Claude-SearchBot, Claude-User, PerplexityBot, Perplexity-User, Google-Ext… |
| ip | string | yes | IPv4 or IPv6 address. |
No output schema declared.
No examples provided.
How do I install the Crawlerpeek MCP server?
Crawlerpeek runs locally as an npm package, launched with npx -y crawlerpeek. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
npm · crawlerpeek
claude mcp add crawlerpeek-crawlerpeek -- npx -y crawlerpeek
What is the Crawlerpeek MCP server?
Crawlerpeek is an MCP server listed in the public MCP registry as io.github.crawlerpeek/crawlerpeek. Check whether AI crawlers (GPTBot, ClaudeBot, PerplexityBot) can access a URL. Read-only. This page covers its npm package (crawlerpeek).
Is the Crawlerpeek MCP server safe to use?
Crawlerpeek scores 74 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 4 November 2026. It declares no install or post-install scripts. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the Crawlerpeek MCP server expose?
Crawlerpeek exposes 6 tools: check_ai_access, see_as_bot, verify_bot_ip, generate_robots_txt, lint_robots_txt, scan_site. Their descriptions and schemas cost roughly 1,119 tokens of context every time the server is loaded.
Is the Crawlerpeek MCP server still maintained?
Crawlerpeek is still listed as active in the MCP registry. We last reached this channel on 4 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.
What licence is the Crawlerpeek MCP server under?
Crawlerpeek declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.