Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

io.github.amati032-dev/crawlbit

NPM · CRAWLBIT-MCP

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

Available components

0 this week 80 Trust /100

Last scanned (12 hours ago)

Scores higher than 66% of npm servers

Category Marketing and SEO

Trust breakdown (7 categories)

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 Security81
  • No malware found by supply-chain analysis.Pass
  • CVE check failed: a known high-severity CVE affects zod 3.25.76, a direct dependency. A fixed version is available. View diagnostics → Fail
  • No install/post-install scripts declared.Pass
  • 31 of 93 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency45
Schema Quality & AI Usability83
  • AI-judged instruction clarity (excellent).Pass
  • Tool/resource definitions use about 492 tokens (~123/item across 4 items; 4 tools + 0 resources), lean.Pass
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management100
  • No destabilizing schema changes in the last 30 days.Pass
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 4 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 4 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
What we tested

Checks we ran (16)

  • Malware scan
  • Known CVEs
  • Install scripts
  • Dependency health
  • Source repository
  • Provenance
  • License
  • Maintenance
  • Security disclosure
  • Schema quality
  • Stability
  • Tool coverage
  • Injection markers
  • Destructive annotations
  • Judged manipulation
  • MCP protocol

Does not apply to this package (2)

  • Endpoint SecurityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.
  • Transport & ReachabilityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.

The score does not measure everything. What the score does not measure →

Changelog

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.

  • 19 Nov 26 0
    • Stability: 0.97 → pass security
  • 18 Nov 26 0
    • Stability: pass → 0.97 functional
  • 12 Nov 26 0
    • Stability: 0.97 → pass security
  • 11 Nov 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 93 to 97. That category is still filling its 30-day observation window: 28 days of observed history at the previous scan, 29 at this one. The score rises as the window fills, whether or not the server changes.

  • 9 Nov 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 87 to 90. That category is still filling its 30-day observation window: 26 days of observed history at the previous scan, 27 at this one. The score rises as the window fills, whether or not the server changes.

  • 8 Nov 26 −2
    • Stability: pass → 0.87 functional
  • 2 Nov 26 0
    • Stability: 0.97 → pass security
  • 1 Nov 26 0
    • Stability: pass → 0.97 functional
Diagnostics

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 21 Nov 2026 · Analysed npm/crawlbit-mcp@1.0.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 →

Vulnerabilities 1 finding
ID CVE Severity Vector Fix available
GHSA-mrhx-c7xc-m3w5 CVE-2023-54404 high CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H yes

Background: What a vulnerability scan can and cannot prove →

Dependencies 93 packages
Packages resolved 93
Stale 31
Tree resolution Complete

Background: SBOMs and build attestations, explained →

MCP tools · 4 exposed · ~492 tokens

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 →

Tool Tokens
crawlbit_crawler_watch ~142

Checks whether AI crawlers are allowed to read a site: GPTBot, OAI-SearchBot, ChatGPT-User, ClaudeBot, PerplexityBot and Google-Extended. Reads the site's robots.txt and reports, per crawler, whether it is fully allowed, partially blocked or blocked entirely. Use this when someone asks why AI never mentions their site, or before any other AI-visibility work: a blocked crawler makes everything else pointless. Reflects robots.txt only, so it cannot detect blocking done at the CDN or firewall layer.

NameTypeReqDescription
urlstringyesThe site to analyse, e.g. example.com or https://example.com

No output schema declared.

No examples provided.

crawlbit_entity_check ~118

Checks whether a brand reads as a clear, consistent entity that AI can recognise: Organization schema, a consistent name, a description, a logo and linked profiles (sameAs). AI engines struggle to name a brand they cannot identify as a distinct thing. Use this when a brand is confused with another, or described vaguely, in AI answers. Measures the signals published on the site itself, not the brand's reputation across the web.

NameTypeReqDescription
urlstringyesThe site to analyse, e.g. example.com or https://example.com

No output schema declared.

No examples provided.

crawlbit_offpage_gaps ~126

Finds where a brand is missing OUTSIDE its own website: review platforms, directories, communities and 'best of' roundups relevant to its category. Off-page mentions on third-party pages are the strongest known predictor of AI citations, because engines weight what others say about a brand far above what the brand says about itself. Use this when a site is technically perfect yet still never cited. Returns the gaps and priorities; it does not publish anything or contact anyone.

NameTypeReqDescription
urlstringyesThe site to analyse, e.g. example.com or https://example.com

No output schema declared.

No examples provided.

crawlbit_shopping ~106

Checks whether AI shopping agents such as ChatGPT Shopping can find, understand and recommend a store's products: product schema completeness, price and availability signals, and the attributes those agents read. Use this for e-commerce sites, especially Shopify, when products never surface in AI recommendations. Inspects published structured data, so it cannot see a merchant feed submitted privately to a platform.

NameTypeReqDescription
urlstringyesThe site to analyse, e.g. example.com or https://example.com

No output schema declared.

No examples provided.

Install

How do I install the io.github.amati032-dev/crawlbit MCP server?

io.github.amati032-dev/crawlbit runs locally as an npm package, launched with npx -y crawlbit-mcp. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

npm · crawlbit-mcp

# add to Claude Code
claude mcp add amati032-dev-crawlbit -- npx -y crawlbit-mcp
Common questions

What is the io.github.amati032-dev/crawlbit MCP server?

io.github.amati032-dev/crawlbit is an MCP server listed in the public MCP registry as io.github.amati032-dev/crawlbit. Four free tools to check if AI engines can find, read and recognise a site. No API key. This page covers its npm package (crawlbit-mcp).

Is the io.github.amati032-dev/crawlbit MCP server safe to use?

io.github.amati032-dev/crawlbit scores 80 out of 100 on VerifyMCP. We recorded 1 known advisory against it as of 21 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 io.github.amati032-dev/crawlbit MCP server expose?

io.github.amati032-dev/crawlbit exposes 4 tools: crawlbit_crawler_watch, crawlbit_entity_check, crawlbit_offpage_gaps, crawlbit_shopping. Their descriptions and schemas cost roughly 492 tokens of context every time the server is loaded.

Is the io.github.amati032-dev/crawlbit MCP server still maintained?

io.github.amati032-dev/crawlbit is still listed as active in the MCP registry. We last reached this channel on 21 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 io.github.amati032-dev/crawlbit MCP server under?

io.github.amati032-dev/crawlbit declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.

What did VerifyMCP test on the io.github.amati032-dev/crawlbit MCP server?

VerifyMCP ran 16 checks on io.github.amati032-dev/crawlbit, covering Malware scan, Known CVEs, Install scripts, Dependency health and 12 more. Endpoint Security and Transport & Reachability do not apply to an npm package, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.