jevcrawl vs Jina Reader

jevcrawl

Three compact, typed MCP tools return verbatim passages with source URLs, cost and stop reasons, and errors arrive as codes with instructions. The project is three days old and alpha, it depends on TypeSafe's paid Jev API, which is in early access with no free tier found, and it does not block crawls of private or local addresses.

Jina Reader

One URL prefix, no key needed, Markdown back. No price per token in any currency on the public page.

jevcrawl

1. Phrase goal as one specific question and start with max_pages between 10 and 30
2. Check stats.stopped_because and stats.degraded, and read uncertain before reporting that something is missing
3. Use scrape without a goal when you need a whole page, since it makes no paid Jev call and needs no key
4. Handle {"error": code, "message": ...} results, for example auth_error means TYPESAFE_API_KEY is missing or rejected
5. Pages in stats.needs_js_urls were not read. Tell the user rather than guessing their content

Jina Reader

1. Prefix the URL, https://r.jina.ai/https://example.com, and read the Markdown
2. Send x-max-tokens to cap a page, or x-token-budget to refuse one that's too big
3. Use x-target-selector when you need one part of a page
4. Keyless is 20 requests a minute and can't search. Add a key for loops or s.jina.ai
5. Send x-no-cache: true when a page may have changed or a blocked response got cached