@crawlbrulee/mcp

MCPattested
v1.1.0io.github.crawlbruleeApache-2.0Updated 2d agonpmGitHub

official mcp server for crawlbrulee — EU-native web scraping for AI agents & developers. native scrape and map tools for your agent.

Works in
ClaudeCursorCopilotGemini

Inferred from the transports this listing declares (stdio). A client not listed here hasn’t been ruled out — it just isn’t something Forge can confirm.

Attested build
A verified provenance attestation binds this artifact to the listed repository. Nobody has claimed the listing yet — this proves where the code was built, not who stands behind it.
585Downloads/wk
2d agoLast update
Needs 1 credential before it runs
  • CRAWLBRULEE_API_KEYAPI keyrequired

    your crawlbrulee api key. get a free one at https://dashboard.crawlbrulee.com

Declared by the author in the official MCP registry. Forge does not store, broker, or ever see these values — the config below is scaffolded with placeholders you fill in locally.

Package
Authorio.github.crawlbrulee
LicenseApache-2.0
Version1.1.0
Sourcenpm+mcp-registry
npm@crawlbrulee/mcp
GitHubcrawlbrulee/crawlbrulee-mcp
SBOMCycloneDX 1.6 ↓
Trust Status
A
85/100Trusted
✓Listed in Forge index+10/10
✓Identity verified · attested build+20/20
—Ed25519 publish signature+0/5
→ Included automatically when the publisher runs `forge publish`
—Domain verification+0/5
→ Publisher: host /.well-known/forge.json on the package homepage with { "publisher": "<github-login>" }
✓npm Trusted Publishing (Sigstore)+5/5
—npm maintainer match+0/5
→ Publisher: add the verified GitHub login to the npm package's maintainers (npm owner add <login>)
✓CVE scan · clean+30/30
✓Static analysis · clean+20/20
Paste into Claude Code, Cursor, or any AI assistant to fix all gaps
StatusIdentity verified
PublisherUnverified
SignatureUnsigned
Domain—
Provenance✓ Sigstore-verified · f60dfc1
Dependencies✓ 60 resolved+ · none vulnerable
Tool surface7 tools · none privileged
Security scan✓ Cleanv1.0.2 · 10d agoHow well does this scan work?
EvalsNone
IndexedSep 23, 2026

Verification confirms publisher identity (repo ownership), not code safety. The security scan covers known CVEs and suspicious install scripts.

Tools

7 tools · none privileged
Statically extracted from the published packagev1.0.2 · 10d ago

Read out of the source npm actually ships, at scan time. The package was never executed. Tools registered dynamically at runtime, or hidden inside bundled or minified code, can be missed — so this is a floor on the tool surface, not a complete census of it.

mapNo description published

This tool published no description. Forge does not invent one.

scrapeNo description published

This tool published no description. Forge does not invent one.

scrape_asyncNo description published

This tool published no description. Forge does not invent one.

scrape_resultNo description published

This tool published no description. Forge does not invent one.

scrape_statusNo description published

This tool published no description. Forge does not invent one.

usageNo description published

This tool published no description. Forge does not invent one.

whoamiNo description published

This tool published no description. Forge does not invent one.

0 of 7 tools published a description.

Tool names and descriptions are written by the publisher and shown verbatim as inert text. They are the strings an MCP client passes to a model, so Forge scans them for prompt-injection patterns — any finding appears with the security scan above. “Privileged” is a keyword match on the tool name, not an audit of what the tool does: a benign-sounding name can still do anything.

About

official mcp server for crawlbrulee — EU-native web scraping for AI agents & developers. native scrape and map tools for your agent.

Keywords
crawlbruleemcpmodel-context-protocolscrapescrapingcrawlerweb-scrapingscreenshotsitemapclaudecursorcodexeugdprai-agentsllmragmarkdown
Alternatives
Comparing tool surfaces…

Tools exposed

7 tools · none privileged · observed by static extraction. A tool surface is what one scan read on one day, not a live capability list.

Linked names open Forge’s index of every entry observed exposing that tool. Browse all indexed tools.

Dependency tree

What one Forge scan resolved from npm metadata on 2026-09-23 — observed resolution, not a publisher declaration.

60 packages resolved · 3 direct · none carrying advisories Resolution stops at depth 4 and 60 packages.

The crawl stopped at the depth-4 limit. Anything below that level was never resolved.

The crawl stopped at the 60-package limit. The rest of the tree was never resolved.

36 more resolved packages are not drawn here (display cap: 24). Every dependency carrying an advisory is drawn regardless of the cap. Full inventory (CycloneDX SBOM)

Declared but not resolved

54 declared dependencies never landed in the tree. They are missing from Forge's resolution, not from the package.

+42 more not listed. The counts by reason above cover all of them.

Not followed: peerDependencies. This tree covers runtime dependencies only, so anything those pull in was never resolved.

Topics

Related in images, video & audio