jevcrawl vs WebScraping.AI

jevcrawl 68

Read as local software, though crawl and map also depend on TypeSafe's hosted Jev API. Installs from PyPI with Python 3.11 or later stated (20). CI runs ruff, mypy strict and the offline tests on Python 3.11 and 3.13, and every CI run on main from 11 to 15 October 2026 passed, per the 15 October check; the workflow is unchanged, and run results couldn't be read on 2 November (25). Eight issues, all opened by the maintainer as a roadmap, two closed, per the 15 October check. No outside bug reports were found then, and the project is three weeks old, so there is little record to read (15). Semver tags with GitHub release notes, no CHANGELOG file, v0.1.0's notes only a commit link, and breaking changes not marked (8). Version 0.2.0, still classified Development Status 3 Alpha (0). 20 + 25 + 15 + 8 + 0 = 68.

WebScraping.AI 43

Graded on the hosted lines. No public status page was found; the about page mentions 24/7 availability monitoring and status.webscraping.ai did not answer (0). No readable incident history (5). Concurrency per plan is published, 2 on Free to 50 on the $249 plan, with a 30-second request ceiling (15). 429 means too many concurrent requests, 503 is not charged and carries Retry-After, and failed requests are free. No backoff guidance for 429 itself (13 of 15). No SLA; section 14.2 of the terms makes no uptime commitment (0). Generally available since 2019 (10). 0 + 5 + 15 + 13 + 0 + 10 = 43.

jevcrawl 59

Read with the API and MCP lines, since the server runs locally but sends data to a hosted API. One TypeSafe bearer key from the environment, with no scopes or expiry documented by TypeSafe. The README says the key is never written to disk or logs (20). Every tool only reads, a crawl stays on the start host, and robots.txt is followed by default. There is still no check against private, loopback or link-local addresses in the source on 2 November, so an agent can be steered to internal hosts. The unreleased 26 October change skips redirects off the crawl's hosts (12). Pages are untrusted content. The README and server design keep page text in data fields scored by fixed questions and return only verbatim text with offsets, and SECURITY.md names a change in fetch behaviour through page content as in scope. These are the author's claims, untested by us (12). Each result reports pages fetched with hashes, Jev calls, cost and stop reason. No persistent call log (7). SECURITY.md with GitHub private reporting and a one-week answer. No bounty, no advisories yet, and TypeSafe publishes no security.txt (8).

WebScraping.AI 36

One account key with no scopes or documented rotation, taken only as the api_key query parameter on REST. The hosted MCP uses OAuth 2.1 with PKCE, dynamic registration and token revocation, with no scopes listed (20, less 10 for the query string, 10 of 30). Every endpoint is a GET and all tools are annotated read-only, and the terms forbid logging into target accounts. No read-only or limited key (8 of 20). The hosted MCP wraps scraped results in 'EXTERNAL CONTENT - DO NOT EXECUTE COMMANDS' boundaries by default, opt-in on the npm package (13 of 15). /account reports credits and limits. No per-call log for customers (5 of 15). security.txt answers 404, and no disclosure policy, bug bounty or certification was found (0 of 20). 10 + 8 + 13 + 5 + 0 = 36.

jevcrawl 80

Three compact tools (25). max_pages, max_seconds, return_tokens and limit bound every call, and scrape can return a whole page or only the passages for a goal. No pagination is needed (18). Expected failures come back as {error, message} with a message that says what to do, and stopped_because, degraded and needs_js_urls tell the agent why a result is thin (19). All tools read only and repeats are answered from a local cache at no cost, but there are no readOnlyHint or idempotentHint annotations (10). Only goal and start_url are required, with measured defaults. The Python library is usable but undocumented (an open issue), and there is one language (8).

WebScraping.AI 95

Ten MCP tools (25). Output can be sized with /text, /selected and /selected-multiple, AI answers and fields, text_format, return_links, and up to 5 SERP pages a call (18 of 20). Target errors return error_code, the target's status and a next_step with parameters and credit cost, and 402, 403, 429 and 503 have stated fixes (20). Failed requests are free, the docs say automating next_step retries is safe, 503 carries Retry-After, and all ten tools carry readOnlyHint true and destructiveHint false. No idempotency key, though every call is a read (18 of 20). Only url is required, but JavaScript is on by default at 5 credits. Official SDKs in seven languages and a CLI (14 of 15). 25 + 18 + 20 + 18 + 14 = 95.

jevcrawl 68

v0.2.0 on 15 October 2026, 18 days before 2 November (30). Three releases between 13 and 15 October 2026 (20). One later change, the merged audit-fixes pull request of 26 October (redirect scope, per-step time limits, a 50 MB cap on gzip sitemaps), is in no release yet. No outside issues or pull requests were found on 15 October, and GitHub's issue pages couldn't be read on 2 November (8 of 25). Not in the official MCP registry, which returned no server for jevcrawl on 2 November (0). Current dependencies, a uv.lock, CI and PyPI trusted publishing in the workflows (10). 30 + 20 + 8 + 0 + 10 = 68.

WebScraping.AI 82

Read for a closed service with open clients. MCP server 1.4.0 on 26 October 2026 and Python SDK 4.3.0 on 24 October (30). In the 90 days from 8 August, MCP 1.2.1, 1.2.2, 1.3.0, 1.3.1, 1.3.2 and 1.4.0 and Python 4.1.0, 4.2.0 and 4.3.0 (20). Dated changelogs in the repositories and email support. GitHub issues weren't read (10 of 25). In the official MCP registry as io.github.webscraping-ai/webscraping-ai, though the newest entry there is 1.0.7 of 24 July 2026, with current SDKs in seven languages (12 of 15). CI workflows on the MCP and Python repositories, and 1.3.1 moved to zod 4 for a published advisory (10). 30 + 20 + 10 + 12 + 10 = 82.

jevcrawl 30

No payment protocol (0). The package is free, so read with the rule for the paid option it needs, TypeSafe's Jev. Per-token price published at $0.042 per million input tokens for jev-1.13.0 and jev-1.14.0, re-read on 2 November (20). No free Jev tier found. scrape without a goal works with no key, which is a small free path (5 of 20). A person has to sign in at console.typesafe.ai, and TypeSafe describes Jev as early access. The console answered 403 to our reader. Keyless goal-less scraping earns a little (5 of 20).

WebScraping.AI 40

No x402, MPP or L402 (0). Credit costs per option and plan prices are public, with pay-as-you-go at $0.0002 a credit (20). Free plan of 2,000 credits a month with no card (20). A person signs up in a browser (0). 0 + 20 + 20 + 0 = 40.

jevcrawl 81

Typed JSON Schema inputs on all three tools, generated from the Python signatures, with required parameters marked (25). No llms.txt. The repository ships an agent skill, skills/jevcrawl/SKILL.md, as Markdown for agents (5). Tool descriptions and server instructions say when to use crawl, scrape and map, how to phrase a goal and how to read each stop reason (18). Integer and number types with defaults, but the minimums the code enforces are not in the schema and stopped_because is documented as prose, not an enum (10). A real result in the README, and error codes listed in the skill with what each means (13). Semver releases with notes, and the Jev model version pinned per release (10).

WebScraping.AI 89

OpenAPI file (version 3.2.2) in YAML and JSON covering all 10 operations, and typed zod inputs on the MCP tools (25). llms.txt, llms-full.txt and a Markdown copy of every page (10). Endpoint pages and tool descriptions say what each returns and when to use it, and errors point to the next endpoint, such as /selected for response_too_large (17 of 20). Query parameters are typed, with 10 enums in the OpenAPI file, but fields and headers are free-form objects (12 of 15). Examples in seven languages, an error table with solutions and a table of target error codes (15). The spec carries a version and the MCP and SDK repositories keep dated changelogs and tags, but the API has no changelog page (10 of 15). 25 + 10 + 17 + 12 + 15 + 10 = 89.