Apify MCP Server vs jevcrawl

Apify MCP Server

x402 on Apify's own domains, a prepaid token from agi.apify.com for any Actor and per-run payment on mcp.apify.com for Pay Per Event Actors. API and Actor runs timed out for about 12 hours on 21 and 22 July 2026.

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.

Apify MCP Server

1. Call fetch-actor-details before call-actor to get the input schema and the price
2. Use apify--web-fetch for one known URL and apify--rag-web-browser for search and read
3. Read results with get-dataset-items and set fields and limit. The default is 20 rows
4. Buy an AGI token for anything that isn't a Pay Per Event Actor, since direct ?payment=x402 refuses the rest. Tokens last 14 days and unused balance isn't refunded
5. Ask for get-actor-run-log, not get-actor-log. The old name is ignored without an error

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