SkillAgentSearch skills...

jevcrawl

MCP server and CLI that crawls websites for AI agents: finds the answer page 2x more often than Crawl4AI, 10x cheaper per answer than letting Claude crawl.

Install / Use

claude mcp add RayenMlayeh -- npx -y github:RayenMlayeh/jevcrawl

If the server publishes to npm under a different name, use that package instead — check the repo README.

About this skill
🔌

MCP Server

Model Context Protocol server

Quality Score

87/100

Supported Platforms

Claude Code
Claude Desktop

Our assessment of jevcrawl

jevcrawl scores 87/100 on our quality scale, 504th of 977 AI & Machine Learning skills we index.

Its MCP Server is 13 KB long, well organised into 14 sections with 5 code examples: a thorough specification that gives an agent plenty to work with.

It has 47 GitHub stars, so there is little community track record yet; judge it on its content.

Substance
30/30
Structure
20/20
Description
15/15
Adoption
7/20
Freshness
15/15

Maintenance, license and trust

  • The repository was last updated today, so jevcrawl is actively maintained.
  • It is released under the Apache-2.0 license, a permissive license that allows use, modification and commercial use with attribution.
  • Its trust signals score 97/100, with no cautions. These come from repository metadata, not a code audit — read the skill file before letting an agent act on it.

jevcrawl compared with similar skills

All 4 of these similar skills score higher than jevcrawl; compare them before choosing.

SkillScoreStarsUpdatedFormat
jevcrawl (this skill)by RayenMlayeh8747todayMCP Server
claude-memby thedotmack100100.6ktodayCLAUDE.md
Agent-Reachby Panniantong10097.2k6d agoCLAUDE.md
Understand-Anythingby Egonex-AI10086.2k2d agoCLAUDE.md
headroomby headroomlabs-ai10075.3ktodayCLAUDE.md

Frequently asked questions

How do I install jevcrawl?
Run claude mcp add RayenMlayeh -- npx -y github:RayenMlayeh/jevcrawl. The install tabs above show the steps for each supported agent.
Which AI agents does jevcrawl work with?
It is written for Claude Code and Claude Desktop, as a MCP Server file. Other agents that read the same format can often use it too.
Is jevcrawl safe to use?
It is Apache-2.0-licensed and scores 97/100 on trust signals. Skills are instructions an agent will follow, so read the file before installing it and do not approve commands you do not understand.
Is jevcrawl still maintained?
The repository was last updated today, so jevcrawl is actively maintained.
<div align="center"> <picture> <source media="(prefers-color-scheme: dark)" srcset="assets/logo-dark.svg"> <img alt="jevcrawl" src="assets/logo-light.svg" width="400"> </picture>

The web crawler for AI agents that finds the answer, not just pages.

A small decision model picks every link and every passage, so your agent's LLM reads only what answers its question at a few cents per crawl.

PyPI CI License Python MCP server Benchmark Cost

Quick start · Benchmarks · Tools · How it works · Configuration

</div> <br> <p align="center"> <img alt="Demo: jevcrawl crawls docs.python.org for 'What does the walrus operator := do and which Python version added it?' and returns the What's New In Python 3.8 passage. 6 pages, 80,034 tokens reduced to 1,873, $0.0069, 8.3 seconds." src="assets/demo.svg" width="100%"> </p> <picture> <source media="(prefers-color-scheme: dark)" srcset="assets/scoreboard-dark.svg"> <img alt="On 50 WebWalkerQA tasks jevcrawl answered 40% correctly and found the answer page 54% of the time for $0.025 per task, against 30%, 33% and $0.194 when Claude picks every link and 8%, 11% and $0.228 for a breadth-first crawl." src="assets/scoreboard-light.svg" width="100%"> </picture>

Why jevcrawl

Agents that browse a site have two bad options. They can read everything a crawler fetches, which buries the answer in navigation and boilerplate and burns tokens. Or they can let the LLM pick each link, which is slow and costs dollars per question. jevcrawl does neither:

  • 🎯 Finds the answer page more often. 54% of tasks vs 33% when Claude picks the links, and 2x as often as Crawl4AI's goal-directed crawl.
  • 💸 About 8x cheaper per task, 10x per correct answer. The crawl decisions cost about a cent.
  • ⚡ 2x faster than an LLM-driven crawl. Four pages at a time, one decision request per page.
  • 📜 Verbatim, with sources. Every passage is copied from the page with its URL, heading path and character offsets. The decision model only scores, so it cannot invent text.
  • 🛡️ Safe against prompt injection by design. Page text is only ever scored, never followed.
  • 🔌 Works everywhere MCP does: Claude Code, Claude Desktop, Cursor, or the CLI.

Quick start

You need a Jev API key from console.typesafe.ai and uv.

Claude Code

claude mcp add jevcrawl -e TYPESAFE_API_KEY=<your key> -- uvx jevcrawl

Claude Desktop, Cursor and other MCP clients (mcpServers in the client's config file)

{
  "mcpServers": {
    "jevcrawl": {
      "command": "uvx",
      "args": ["jevcrawl"],
      "env": { "TYPESAFE_API_KEY": "<your key>" }
    }
  }
}

Then ask your agent something like "Use jevcrawl to find which Python version added the walrus operator, starting from docs.python.org". Check the setup with uvx jevcrawl doctor. Agents that load skills can also use skills/jevcrawl/SKILL.md.

Benchmarks

Every system starts on a site's home page with the same 30-page budget and the same question. What each one collects goes to the same answering LLM, and the same judge grades the answer, so the crawler is the only thing that changes.

<picture> <source media="(prefers-color-scheme: dark)" srcset="assets/cost-dark.svg"> <img alt="Cost of one correct answer: jevcrawl $0.06, Claude picking every link $0.65, breadth-first crawl $2.85." src="assets/cost-light.svg" width="100%"> </picture>

jevcrawl vs Crawl4AI

Crawl4AI is one of the most popular open-source crawlers for LLMs. Its BestFirstCrawlingStrategy with a keyword scorer is its way to crawl toward a question without an LLM, so we compared the two on whether they fetch the page that holds the answer.

<picture> <source media="(prefers-color-scheme: dark)" srcset="assets/crawl4ai-dark.svg"> <img alt="On 20 tasks jevcrawl found an answer page 10 times and Crawl4AI 5 times; every answer page 5 vs 2; median crawl time 29 s vs 43 s; sites that failed to load 0 vs 3. jevcrawl found 6 answer pages Crawl4AI missed, Crawl4AI found 1 jevcrawl missed." src="assets/crawl4ai-light.svg" width="100%"> </picture>

Where the numbers come from

| | | |---|---| | Tasks | WebWalkerQA from WebWalker: Benchmarking LLMs in Web Traversal (Wu et al., Alibaba Tongyi Lab, ACL 2025): questions whose answers sit several clicks deep in real websites (conferences, universities, organizations, games), in English and Chinese. | | Task selection | Each task was re-checked live before the run: the site and answer page still load and still contain the reference answer. Tasks looked at while developing are excluded (bench/tasks/seen-ids.txt). | | Accuracy run | 50 tasks, 2026-10-12. Answering model claude-opus-5-5, judge claude-sonnet-5-5. | | Crawl4AI run | 20 different tasks, 2026-10-13, Crawl4AI 0.9.4. Crawl only, no LLM: did the crawler fetch the gold page? In the accuracy run, whether a system fetched the gold page closely tracked whether it answered correctly. | | Baselines | Claude picks every link: Claude reads each page and chooses the next link. Breadth-first: every page to depth 2. All systems share jevcrawl's fetcher and remove navigation and footers. | | Costs | Jev cost is billed and exact. LLM costs are token counts at list price. | | Caveats | 50 and 20 tasks are small samples: the cost gap is large and stable, the accuracy gap less so. Crawl4AI drives a real browser, jevcrawl does not run JavaScript. |

The benchmark code and how to reproduce every number: bench/.

Tools

| Tool | Use it for | |---|---| | crawl(goal, start_url, max_pages=30, max_seconds=120, return_tokens=4000, max_decision_usd=0.05) | The answer may be several pages deep. Returns the relevant passages. | | scrape(url, goal=None) | One known page. With a goal, only the relevant passages; without one, all content and no Jev call. | | map(start_url, goal, limit=50, max_pages=10) | Ranked URLs only, to decide what to scrape. |

<details> <summary><b>A real result</b> (docs.python.org, "What does the walrus operator := do and which Python version added it?")</summary>
{"blocks": [{"url": "https://docs.python.org/3/whatsnew/3.8.html",
             "heading_path": "What’s New In Python 3.8 > New Features > Assignment expressions",
             "text": "There is new syntax := that assigns values to variables as part of a larger expression. ...",
             "char_start": 307, "char_end": 580, "relevance": 0.97}],
 "uncertain": [],
 "pages": [{"url": "https://docs.python.org/3/", "title": "3.15.0 Documentation", "lang": "en",
            "text_sha256": "b624ce93..."}],
 "stats": {"pages_fetched": 6, "tokens_raw": 80034, "tokens_returned": 1873, "jev_calls": 11,
           "cache_hits": 0, "jev_input_tokens": 164139, "jev_cost_usd": 0.0069,
           "model": "jev-1.13.0", "degraded": false, "degraded_reason": null,
           "needs_js_urls": [], "stopped_because": "answered", "elapsed_seconds": 8.3}}

Trimmed to one block and one page. 80,034 tokens of pages became 1,873 tokens of answer, for $0.0069, in 8.3 seconds.

  • blocks are the relevant passages, best first; uncertain are borderline ones worth reading before concluding something is missing.
  • char_start/char_end index into the page text whose sha256 is in pages, so a quote can be checked later.
  • stopped_because is answered, frontier_empty, max_pages, max_seconds, budget or auth_error.
  • Expected failures come back as {"error": "<code>", "message": "<what to do>"}; the tools never raise into the agent's session.
</details>

The same operations work from the command line (uv tool install jevcrawl or pip install jevcrawl puts jevcrawl on your path):

jevcrawl crawl https://docs.python.org/3/ --goal "What does the walrus operator do?" [--json]
jevcrawl scrape https://example.com/help/returns [--goal "..."] [--json]
jevcrawl map https://example.com --goal "..." [--limit 20]
jevcrawl doctor

How it works

<picture> <source media="(prefers-color-scheme: dark)" srcset="assets/how-dark.svg"> <img alt="A crawl in six steps: seed from the sitemap, fetch the best 4 pages, segment them into passages, filter boilerplate for free, Jev scores every passage and link in one request per page, Jev checks whether the kept passages answer the goal. If not, it follows the next best links. The docs.python.org example turned 80,034 tokens of pages into 1,873 tokens for $0.0069 in 8.3 s." src="assets/how-light.svg" width="100%"> </picture>
  • Jev decides, it does not write. Jev returns a probability per yes/no question, so it cannot produce text. Everything you get back is copied from the page.
  • Page text is data, never instructions. It travels only in data fields of a question; every question sentence is a fixed string written by jevcrawl. An injected "ignore previous instructions" can at worst bias a score.
  • Links below the priority floor are kept in reserve, not dropped, so a crawl never stops early while it still has page budget.
  • Failures degrade, they do not hide. After three failed Jev requests the crawl continues breadth-first, returns every block unscored in uncertain, and sets stats.degraded.
  • Repeats are free. Jev's answers are cached locally (~/.jevcrawl/cache), so the same goal on the same pages costs nothing.

Configuration

| Environment variable | Meaning | Default | |---|---|---| | TYPESAFE_API_KEY | Jev API key (required) | none | | JEVCRAWL_BASE_URL | Jev-compatible endpoint | https://api.typesafe.ai | | JEVCRAWL_MODEL | model id | jev-1.13.0 (pinned: thresholds are calibrated per version) | | JEVCRAWL_CACHE_DIR | answer cache | ~/.jevcrawl/cache | | JEVCRAWL_RESPECT_ROBOTS | skip URLs the site's robots.txt disallows (0 turns it off) | 1 |

Everything else (thresholds, links per page, concurrency) has a measured default in jevcrawl/config.py, and Python callers can pass their own Config.

Cost and privacy

Jev charges for input tokens only, $0.042 per million for jev-1.13.0; in the benchmark a crawl cost $0.011 on average. max_decision_usd is a hard limit: a request that could pass it is never sent, and the crawl stops with budget. Every result reports jev_cost_usd, and tokens_raw (what a plain crawl would hand your LLM) against tokens_returned.

Page text is sent to TypeSafe (blocks, link labels and URLs) to be scored. The API key is read from the environment and never written to disk or logs.

Crawling responsibly

jevcrawl follows each site's robots.txt by default (set JEVCRAWL_RESPECT_ROBOTS=0 to turn that off) and does not rate-limit itself beyond fetching four pages at a time. You are responsible for the sites you crawl, their terms of service and the law that applies to you. It never logs in, does not try to get past paywalls or

Truncated for display — read the full file on GitHub.

Related Skills

View on GitHub
GitHub Stars47
CategoryAI
Updated3h ago
Forks4

Languages

Python

Trust signals

97/100

From repository metadata: license, adoption, age and documentation. Not a code audit — see the Safety scan above for what the skill file itself contains.

1 info