{ "data": { "a": { "slug": "apify-mcp", "name": "Apify MCP Server", "vendor": "Apify", "vendorUrl": "https://apify.com", "kind": "mcp", "category": "web-scrapers", "summary": "Exposes thousands of Apify Store Actors (scrapers, crawlers, automations) as dynamically discovered MCP tools, hosted at mcp.apify.com or run locally; supports OAuth, API tokens and agentic payments (x402 prepaid tokens, Skyfire).", "url": "https://www.anchorterminal.com/tools/apify-mcp", "markdownUrl": "https://www.anchorterminal.com/tools/apify-mcp.md", "slimMarkdownUrl": "https://www.anchorterminal.com/tools/apify-mcp.min.md", "jsonUrl": "https://www.anchorterminal.com/api/v1/tools/apify-mcp.json", "dns": "apify-mcp.grade.anchorterminal.com", "repo": "https://github.com/apify/apify-mcp-server", "license": "MIT", "transports": [ "stdio", "streamable-http" ], "remoteUrl": "https://mcp.apify.com", "packages": [ { "registry": "npm", "name": "@apify/actors-mcp-server" } ], "auth": "mixed", "authNotes": "OAuth on mcp.apify.com, or an Apify API token as `Authorization: Bearer`. Tokens can be scoped to account or per-resource permissions, given an expiry date and rotated with a 24-hour overlap. The Apify API also accepts the token as a `token` query parameter. Without an account, an agent can buy an AGI prepaid token over x402 or MPP and use it as a Bearer token, or pay per request with Skyfire PAY tokens (Pay Per Event Actors only). `?tools=` selects categories or single tools.", "pricing": "freemium", "pricingNotes": "MCP server itself is free; Actor runs are billed on Apify plans: Free $0 with $5/month usage credit ($0.20 per compute unit), Starter $19/mo, Scale $199/mo ($0.16/CU), Business $999/mo ($0.13/CU), 10% off annual (https://apify.com/pricing).", "priceSummary": "$1 / call", "where": "both", "x402": { "level": "yes", "evidence": "AGI (agi.apify.com) sells a prepaid, spend-capped Apify token over x402 (exact scheme on Base or Solana) or MPP (charge on Tempo with USDC or pathUSD, or Solana with USDC or USDT), minimum $1, valid for 14 days with unused balance not refunded, usable as `Authorization: Bearer` against mcp.apify.com and api.apify.com for any Actor that uses limited permissions. AGI also runs single Actors for x402 `batch-settlement` on Base (`/api-proxy/actors/{actorId}/runs`, $1 minimum ceiling, real cost billed, unused channel balance refunded after 24 hours idle). The server's direct `?payment=x402` mode is still in its source, but the README dropped its documentation on 28 October 2026 (https://agi.apify.com/AGENTS.md; https://docs.apify.com/agents/payments.md; https://docs.apify.com/mcp.md, checked 2026-11-01).", "endpoints": [ { "url": "https://agi.apify.com/protocols/x402/prepaid-tokens?amount=1\u0026currency=usd", "priceUsd": 1, "network": "eip155:8453" }, { "url": "https://agi.apify.com/api-proxy/actors/{actorId}/runs?amount=1\u0026currency=usd", "priceUsd": 1, "network": "eip155:8453" } ] }, "toolCount": 47, "popularity": { "githubStars": 8600, "npmWeekly": 15257, "pypiWeekly": null, "asOf": "2026-09-26" }, "docsUrl": "https://github.com/apify/apify-mcp-server#readme", "registryName": "com.apify/apify-mcp-server", "capabilities": [ "scraping.actors", "web.crawl" ], "tags": [ "official", "hosted", "local", "open-source", "x402", "aggregator" ], "lastRelease": "2026-10-29", "graded": true, "anchor": { "graded": true, "score": 78.5, "grade": "A", "agentReady": true, "rank": 22, "ranked": true, "rankOf": 1486, "categoryRank": 1, "methodology": "0.7", "run": "2026-10-01", "scores": { "ergonomics": 92, "maintenance": 95, "payments": 95, "reliability": 75, "schema": 92, "security": 62, "transparency": 86 }, "pending": [ "performance", "tasks" ], "assessment": { "confidence": "medium", "date": "2026-11-01" }, "negative": -5, "negativeNotes": [ "-3: v0.16.0 on 2026-09-17 renamed get-actor-log to get-actor-run-log with no deprecation period, and the old name is now ignored without an error. It was flagged as breaking in the changelog on release day, so the lowest deduction (https://github.com/apify/apify-mcp-server/blob/master/CHANGELOG.md).", "-2: GHSA-6gr2-qh89-hxwm (CVE-2026-50143, CVSS 8.1, High). Versions before 0.10.11 built an Actor's MCP URL by joining strings, so a malicious Actor's webServerMcpPath could send the user's Apify token to another host. Fixed in 0.10.11 on 28 May 2026 and published as a GitHub advisory, about four months old, so 2 points rather than the full deduction for an exfiltration path. The Moderate GHSA-jwp7-wg77-3w9v (CVE-2026-46341), a fetch-apify-docs allowlist bypass fixed in 0.9.21 on 4 May 2026, wasn't deducted (https://github.com/apify/apify-mcp-server/security/advisories/GHSA-6gr2-qh89-hxwm; https://github.com/apify/apify-mcp-server/security/advisories/GHSA-jwp7-wg77-3w9v)." ], "verdict": "x402 on Apify's own domains, a prepaid token from agi.apify.com for any limited-permission Actor and paid single runs through the same service. Tool names and defaults still change between 0.x releases, with breaking changes flagged only on release day.", "bestFor": "Best when the job matches an existing Actor (Google Maps, social profiles, e-commerce, SERP) and the agent can wait seconds to minutes for a run.", "strengths": [ "x402 on Apify's own domains, a prepaid token from agi.apify.com for any limited-permission Actor and x402 single runs billed at real cost", "14 tools by default out of 47, `?tools=` to pick categories, and readOnly, destructive and idempotent hints on every tool", "Scoped API tokens with expiry and a 24-hour rotation overlap, plus OAuth on the hosted server", "28 releases between 3 August and 29 October 2026, with breaking changes flagged in the changelog", "Free plan with $5 of monthly usage and no card" ], "weaknesses": [ "0.19.0 and 0.20.0 (19 and 29 October 2026) changed tool behaviour with breaking changes flagged only on release day", "No prompt-injection guidance for scraped content, third-party Actor READMEs or remote Actor MCP results", "Telemetry and Sentry on by default, and Store searches send a model-written use case", "Prepaid tokens can't run Actors that need full permissions, and Skyfire covers Pay Per Event Actors only", "No SLA published for any self-serve plan" ], "agentNotes": [ "Call fetch-actor-details before call-actor to get the input schema and the price", "Use call-actor-mcp-tool, not call-actor with `actor:tool`, for an Actor that runs an MCP server. List its tools first with fetch-actor-mcp-tool-list", "Read results with get-dataset-items and set `fields` and `limit`. The default is 20 rows", "Buy an AGI token to pay without an account. Tokens last 14 days, unused balance isn't refunded, and Actors needing full permissions refuse them", "Pin `?tools=` in production. The default tool set changes between versions" ], "metrics": { "kind": "remote", "measured": false }, "reviewCount": 8, "avgRating": 3.4, "history": [ { "basis": "public evidence", "confidence": "medium", "grade": "A", "methodology": "0.7", "pending": [ "performance", "tasks" ], "run": "2026-10-01", "runLabel": "October 2026 research run", "score": 78.5 } ], "editorialScores": { "ergonomics": 92, "maintenance": 95, "payments": 95, "reliability": 75, "schema": 92, "security": 62, "transparency": 75 }, "provenanceScore": 97, "checked": { "categories": { "ergonomics": "2026-11-01", "maintenance": "2026-11-01", "payments": "2026-11-01", "reliability": "2026-11-01", "schema": "2026-11-01", "security": "2026-11-01", "transparency": "2026-11-01" }, "last": "2026-11-01", "lastMoved": "2026-11-01", "oldest": "2026-11-01", "stale": false, "staleAfterDays": 90 } }, "connect": { "claudeCode": "claude mcp add --transport http apify https://mcp.apify.com --header \"Authorization: Bearer ${APIFY_TOKEN}\"", "config": { "mcpServers": { "apify": { "headers": { "Authorization": "Bearer ${APIFY_TOKEN}" }, "url": "https://mcp.apify.com" } } }, "x402": "curl -s -i -X POST 'https://agi.apify.com/protocols/x402/prepaid-tokens?amount=1\u0026currency=usd'\n# 402 -\u003e pay with PAYMENT-SIGNATURE (USDC, eip155:8453) -\u003e token in response\n# then: Authorization: Bearer \u003cprepaid token\u003e against https://mcp.apify.com" }, "letme": { "capability": "https://letme.dev/scraping.actors", "tool": "https://letme.dev/apify-mcp" }, "area": "web-data", "unitPrices": [ { "item": "Compute unit, pay as you go", "unit": "compute-unit", "usd": 0.2 } ], "provenance": { "legalEntity": "Apify Technologies s.r.o.", "domain": "apify.com", "domainRegistered": "2009-06-02", "endpointOnVendorDomain": true, "terms": "https://docs.apify.com/legal/general-terms-and-conditions", "privacy": "https://docs.apify.com/legal/privacy-policy", "statusPage": "https://status.apify.com", "changelog": "https://github.com/apify/apify-mcp-server/releases", "securityTxt": "valid", "checked": "2026-11-01", "score": 97 }, "requirements": { "setupChecked": true, "complianceChecked": true, "agentAlone": true, "card": "no", "freeTier": true, "minutes": 3, "credential": "mixed", "hosting": [ "US" ], "euResidency": "unknown", "trainsOnData": "unknown", "zeroRetention": "unknown", "certifications": [ "SOC 2 Type II", "GDPR" ], "dpa": true, "selfHost": "no" }, "pageJsonUrl": "https://www.anchorterminal.com/tools/apify-mcp.json", "live": { "slug": "apify-mcp", "probe": { "target": "https://mcp.apify.com", "method": "mcp-initialize", "lastAt": "2026-11-07T18:20:10.572148431Z", "lastOk": true, "lastStatus": 401, "lastMs": 334, "lastNote": "asks for credentials", "authRequired": true, "uptime24h": 100, "uptime30d": 99.9, "p50ms24h": 277, "p95ms24h": 365, "samples24h": 239, "samples30d": 7910, "days": [ { "date": "2026-10-07", "probes": 272, "ok": 272 }, { "date": "2026-10-08", "probes": 268, "ok": 267 }, { "date": "2026-10-09", "probes": 250, "ok": 250 }, { "date": "2026-10-10", "probes": 247, "ok": 247 }, { "date": "2026-10-11", "probes": 247, "ok": 247 }, { "date": "2026-10-12", "probes": 247, "ok": 247 }, { "date": "2026-10-13", "probes": 248, "ok": 247 }, { "date": "2026-10-14", "probes": 249, "ok": 247 }, { "date": "2026-10-15", "probes": 253, "ok": 253 }, { "date": "2026-10-16", "probes": 252, "ok": 252 }, { "date": "2026-10-17", "probes": 253, "ok": 253 }, { "date": "2026-10-18", "probes": 256, "ok": 256 }, { "date": "2026-10-19", "probes": 255, "ok": 255 }, { "date": "2026-10-20", "probes": 252, "ok": 251 }, { "date": "2026-10-21", "probes": 253, "ok": 252 }, { "date": "2026-10-22", "probes": 253, "ok": 253 }, { "date": "2026-10-23", "probes": 248, "ok": 248 }, { "date": "2026-10-24", "probes": 251, "ok": 251 }, { "date": "2026-10-25", "probes": 250, "ok": 249 }, { "date": "2026-10-26", "probes": 252, "ok": 252 }, { "date": "2026-10-27", "probes": 249, "ok": 249 }, { "date": "2026-10-28", "probes": 251, "ok": 250 }, { "date": "2026-10-29", "probes": 249, "ok": 249 }, { "date": "2026-10-30", "probes": 248, "ok": 248 }, { "date": "2026-10-31", "probes": 251, "ok": 251 }, { "date": "2026-11-01", "probes": 249, "ok": 249 }, { "date": "2026-11-02", "probes": 250, "ok": 250 }, { "date": "2026-11-03", "probes": 248, "ok": 248 }, { "date": "2026-11-04", "probes": 246, "ok": 246 }, { "date": "2026-11-05", "probes": 185, "ok": 185 }, { "date": "2026-11-06", "probes": 241, "ok": 241 }, { "date": "2026-11-07", "probes": 187, "ok": 187 } ] }, "vendorStatus": { "page": "https://status.apify.com", "indicator": "none", "summary": "All Systems Operational", "checkedAt": "2026-11-07T18:20:32.839048287Z" }, "versions": [ { "registry": "github", "name": "apify/actors-mcp-server", "version": "v0.17.1", "released": "2026-09-30", "seenAt": "2026-10-01T13:17:39.020905395Z" }, { "registry": "github", "name": "apify/apify-mcp-server", "version": "v0.21.4", "released": "2026-11-06", "seenAt": "2026-11-06T23:06:42.671525301Z" }, { "registry": "mcp-registry", "name": "com.apify/apify-mcp-server", "version": "0.21.4", "seenAt": "2026-11-07T18:16:28.95801333Z" }, { "registry": "npm", "name": "@apify/actors-mcp-server", "version": "0.21.4", "seenAt": "2026-11-06T23:06:42.411970583Z" } ], "githubStars": 15080, "npmWeekly": 35023, "securityTxt": { "url": "https://apify.com/.well-known/security.txt", "state": "valid", "expires": "2035-01-01T00:00:00.000Z", "checkedAt": "2026-11-07T16:00:39.986859847Z" }, "domain": { "domain": "apify.com", "registered": "2009-06-02", "source": "https://rdap.verisign.com/com/v1/domain/apify.com", "checkedAt": "2026-11-01T14:15:06.485929527Z" }, "pages": [ { "url": "https://raw.githubusercontent.com/apify/apify-mcp-server/master/CHANGELOG.md", "kind": "deprecations", "status": 304, "checkedAt": "2026-11-07T14:20:02.235415327Z", "changedAt": "2026-11-06T13:41:25.602394106Z", "fingerprint": "00553ca17923" }, { "url": "https://apify.com/pricing", "kind": "pricing", "status": 200, "checkedAt": "2026-11-07T13:59:25.280926465Z", "changedAt": "2026-11-07T13:59:25.280926465Z", "fingerprint": "775742ab2a6c" }, { "url": "https://docs.apify.com/legal/privacy-policy", "kind": "privacy", "status": 200, "checkedAt": "2026-11-07T14:05:04.430542344Z", "changedAt": "2026-10-26T03:13:37.745025484Z", "fingerprint": "baa7a19d779b" }, { "url": "https://docs.apify.com/legal/general-terms-and-conditions", "kind": "terms", "status": 200, "checkedAt": "2026-11-07T14:05:02.174688599Z", "changedAt": "2026-10-22T01:14:33.334764567Z", "fingerprint": "48db3585a5d3" } ], "mcpTools": { "url": "https://mcp.apify.com", "checkedAt": "2026-11-07T01:42:29.252253317Z", "status": "auth", "note": "asks for credentials before listing its tools", "changedAt": "2026-09-28T21:55:37.935476956Z" }, "github": { "repo": "apify/apify-mcp-server", "checkedAt": "2026-11-02T08:31:15.757132667Z", "stars": 14302, "archived": false, "issuesEnabled": true, "pushedAt": "2026-10-31T21:36:53Z", "openIssues": 203, "openPRs": 41, "issuesOpened90d": 292, "issuesClosed90d": 190, "prsMerged90d": 198, "ci": { "branch": "master", "runs": 50, "success": 44, "failure": 4, "other": 2, "latest": "success", "latestAt": "2026-10-30T21:19:41Z" }, "advisories": [ { "ghsa": "GHSA-9ggj-r5px-674v", "severity": "low", "published": "2026-10-27T09:08:43Z" }, { "ghsa": "GHSA-6gr2-qh89-hxwm", "cve": "CVE-2026-50143", "severity": "high", "published": "2026-05-28T12:11:28Z" }, { "ghsa": "GHSA-jwp7-wg77-3w9v", "cve": "CVE-2026-46341", "severity": "medium", "published": "2026-05-13T13:37:52Z" } ], "replies": { "sampled": 25, "unanswered": 17, "medianDays": 1.7 } }, "updatedAt": "2026-11-07T18:20:10.572148431Z" } }, "answer": "Apify MCP Server scores 78.5 (A) on agent readiness against fastCRW's 64.3 (B), and leads in every scored category.", "b": { "slug": "crw", "name": "fastCRW", "vendor": "Nanofy OÜ", "vendorUrl": "https://fastcrw.com", "kind": "http-api", "category": "web-scrapers", "summary": "fastCRW is a Firecrawl-compatible scraping engine in Rust from Nanofy OÜ in Estonia. It turns pages into Markdown or JSON and searches, maps and crawls sites, as an AGPL-3.0 self-hosted binary or a hosted API with an MCP server.", "url": "https://www.anchorterminal.com/tools/crw", "markdownUrl": "https://www.anchorterminal.com/tools/crw.md", "slimMarkdownUrl": "https://www.anchorterminal.com/tools/crw.min.md", "jsonUrl": "https://www.anchorterminal.com/api/v1/tools/crw.json", "dns": "crw.grade.anchorterminal.com", "repo": "https://github.com/fastcrw/crw", "license": "AGPL-3.0", "transports": [ "stdio", "streamable-http" ], "remoteUrl": "https://fastcrw.com/mcp", "packages": [ { "registry": "npm", "name": "crw-mcp" }, { "registry": "npm", "name": "crw-sdk" }, { "registry": "pypi", "name": "crw" }, { "registry": "cargo", "name": "crw-server" }, { "registry": "oci", "name": "ghcr.io/fastcrw/crw" } ], "auth": "mixed", "authNotes": "Hosted API at api.fastcrw.com takes `Authorization: Bearer crw_live_...` keys from the fastcrw.com dashboard after a browser signup (GitHub or email). The hosted MCP server at fastcrw.com/mcp takes OAuth 2.1 (PKCE S256, dynamic client registration, one scope `mcp:tools`) or the key in the URL path as fastcrw.com/mcp/\u003cAPI_KEY\u003e. No key scopes found. A self-hosted engine needs no key unless `[auth] api_keys` is set.", "pricing": "freemium", "pricingNotes": "500 one-off credits with no card, plus up to 500 more from onboarding tasks. Hobby $13 a month for 5,000 credits, Standard $69 for 100,000, Growth $279 for 500,000, Scale $549 for 1,000,000 (less with yearly billing). One credit a page on any renderer, search 2. Failed pages refunded, top-ups never expire. Self-hosting is free.", "priceSummary": "$13 / mo", "where": "both", "x402": { "level": "no", "evidence": "No x402, MPP or L402 on the pricing page, the credit-costs and agent-onboarding docs, or the OpenAPI spec (checked 2026-11-06). A 402 on the hosted API means an exhausted credit balance (`errorCode: insufficient_credits`) with an upgrade URL header, not a payment requirement.", "endpoints": [] }, "toolCount": 11, "popularity": { "githubStars": 1200, "npmWeekly": 881, "pypiWeekly": null, "asOf": "2026-11-06" }, "docsUrl": "https://docs.fastcrw.com", "llmsTxt": "https://docs.fastcrw.com/llms.txt", "openapi": "https://github.com/fastcrw/crw/blob/main/docs/openapi.json", "registryName": "io.github.fastcrw/crw", "capabilities": [ "web.scrape", "web.crawl", "web.extract", "scraping.js-render", "scraping.proxies", "web.search", "web.fetch" ], "tags": [ "hosted", "local", "open-source", "self-hosted", "freemium", "no-card", "mcp", "remote-mcp", "mcp-registry", "llms-txt", "openapi", "rust", "eu" ], "lastRelease": "2026-11-04", "graded": true, "anchor": { "graded": true, "score": 64.3, "grade": "B", "agentReady": false, "rank": 478, "ranked": true, "rankOf": 1486, "categoryRank": 11, "methodology": "0.7", "run": "2026-10-01", "scores": { "ergonomics": 91, "maintenance": 93, "payments": 35, "reliability": 50, "schema": 91, "security": 40, "transparency": 60 }, "pending": [ "performance", "tasks" ], "assessment": { "confidence": "medium", "date": "2026-11-06" }, "negative": 0, "verdict": "Agents get 11 compact, annotated MCP tools with bounded output, a public OpenAPI spec, refunds on failed pages and a free self-hosted engine. The hosted service has no status history, publishes no SLA terms, names its operator only on the support page, and documents an MCP address with the API key in the URL path.", "bestFor": "Agents that want Firecrawl-style scrape, crawl, map, search and extract at lower per-page cost, or a small self-hosted engine.", "strengths": [ "11 MCP tools, each annotated readOnlyHint, destructiveHint and idempotentHint, with output capped near 15,000 characters and a resume offset", "Public OpenAPI 3.1 spec, llms.txt and an error page that says which codes to retry and which to stop on", "Failed and blocked pages are refunded, every renderer costs 1 credit, and top-up credits never expire", "Released 16 times in the 90 days to 6 November 2026, with five open issues on GitHub", "AGPL-3.0 engine runs self-hosted with no account, and MIT Python and TypeScript SDKs" ], "weaknesses": [ "The status page shows a live check and an uptime objective but no incident history", "The hosted MCP address fastcrw.com/mcp/\u003cAPI_KEY\u003e puts the key in the URL path as a documented option", "Terms and privacy policy name no legal entity, give no retention periods and name no DPA; only the support page names Nanofy OÜ", "No SLA terms beyond an Enterprise mention, no security.txt and no certification found", "No machine payment protocol, and hosted keys need a person to sign up in a browser" ], "agentNotes": [ "Connect to https://fastcrw.com/mcp with OAuth rather than the /mcp/\u003cAPI_KEY\u003e address, so the key stays out of URLs and logs", "Branch on `errorCode`. Stop on 402 insufficient_credits or llm_not_available, and on 429 wait for Retry-After before retrying", "Check `success` as well as the HTTP status, since an anti-bot wall answers 200 with `success: false` and `errorCode: anti_bot`", "Pass `startIndex` from a truncated result to read the rest of a long page instead of setting `maxLength: 0`", "Use native /v1 routes for new work; /firecrawl/v2 is for Firecrawl SDK migrations and keeps the older 429 for empty balances" ], "metrics": { "kind": "remote", "measured": false }, "reviewCount": 0, "avgRating": 0, "history": [ { "basis": "public evidence", "confidence": "medium", "grade": "B", "methodology": "0.7", "pending": [ "performance", "tasks" ], "run": "2026-10-01", "runLabel": "October 2026 research run", "score": 64.3 } ], "editorialScores": { "ergonomics": 91, "maintenance": 93, "payments": 35, "reliability": 50, "schema": 91, "security": 40, "transparency": 53 }, "provenanceScore": 67, "checked": { "categories": { "ergonomics": "2026-11-06", "maintenance": "2026-11-06", "payments": "2026-11-06", "reliability": "2026-11-06", "schema": "2026-11-06", "security": "2026-11-06", "transparency": "2026-11-06" }, "last": "2026-11-06", "oldest": "2026-11-06", "stale": false, "staleAfterDays": 90 } }, "connect": { "install": "npx -y crw-mcp@latest install", "http": "curl -X POST https://api.fastcrw.com/v1/scrape -H \"Authorization: Bearer YOUR_API_KEY\" -H \"Content-Type: application/json\" -d '{\"url\":\"https://example.com\",\"formats\":[\"markdown\"]}'" }, "letme": { "capability": "https://letme.dev/web.scrape", "tool": "https://letme.dev/crw" }, "area": "web-data", "unitPrices": [ { "item": "Hobby plan", "unit": "month", "usd": 13, "note": "5,000 credits; $11 a month billed yearly" }, { "item": "Standard plan", "unit": "month", "usd": 69, "note": "100,000 credits; $59 a month billed yearly" }, { "item": "Hobby top-up", "unit": "1k-pages", "usd": 9, "note": "one credit scrapes one page on any renderer" }, { "item": "Scale top-up", "unit": "1k-pages", "usd": 0.6, "note": "$299 for 500,000 credits" } ], "provenance": { "legalEntity": "Nanofy OÜ", "domain": "fastcrw.com", "domainRegistered": "2026-03-05", "endpointOnVendorDomain": true, "terms": "https://fastcrw.com/terms", "privacy": "https://fastcrw.com/privacy", "statusPage": "https://fastcrw.com/status", "changelog": "https://github.com/fastcrw/crw/blob/main/CHANGELOG.md", "securityTxt": "none", "checked": "2026-11-06", "notes": [ "Nanofy OÜ (registry code 17365846, Sepapaja tn 6, Tallinn) is named as operator on fastcrw.com/support. The terms (last updated 4 April 2026) and the privacy policy (undated) name only fastCRW and 'the jurisdiction in which fastCRW operates'.", "The terms forbid crawling sites against their terms or robots.txt and put responsibility for targets on the customer. No clause forbids automated access to fastcrw.com itself.", "fastcrw.com/robots.txt allows all crawlers except account, API and login paths; docs.fastcrw.com/robots.txt allows all.", "RDAP gives fastcrw.com a registration date of 5 March 2026.", "fastcrw.com/.well-known/security.txt answers 404. SECURITY.md in the repository names security@fastcrw.com and GitHub private vulnerability reporting." ], "score": 67 }, "pageJsonUrl": "https://www.anchorterminal.com/tools/crw.json", "live": { "slug": "crw", "probe": { "target": "https://fastcrw.com/mcp", "method": "get", "lastAt": "2026-11-07T18:20:19.526009674Z", "lastOk": true, "lastStatus": 401, "lastMs": 156, "lastNote": "asks for credentials", "authRequired": true, "uptime24h": 100, "uptime30d": 100, "p50ms24h": 80, "p95ms24h": 153, "samples24h": 200, "samples30d": 200, "days": [ { "date": "2026-11-06", "probes": 13, "ok": 13 }, { "date": "2026-11-07", "probes": 187, "ok": 187 } ] }, "vendorStatus": { "page": "https://fastcrw.com/status", "indicator": "unknown", "summary": "no machine-readable status found", "checkedAt": "2026-11-07T04:47:35.720864858Z" }, "versions": [ { "registry": "github", "name": "fastcrw/crw", "version": "v0.42.1", "released": "2026-11-06", "seenAt": "2026-11-06T23:18:48.669809831Z" }, { "registry": "mcp-registry", "name": "io.github.fastcrw/crw", "version": "0.42.1", "seenAt": "2026-11-07T18:16:28.95801333Z" }, { "registry": "npm", "name": "crw-mcp", "version": "0.42.1", "seenAt": "2026-11-06T23:18:46.329470936Z" }, { "registry": "npm", "name": "crw-sdk", "version": "0.42.1", "seenAt": "2026-11-06T23:18:46.739900633Z" }, { "registry": "pypi", "name": "crw", "version": "0.42.1", "released": "2026-11-06", "seenAt": "2026-11-06T23:18:48.550796676Z" } ], "githubStars": 1230, "npmWeekly": 881, "pypiWeekly": 441, "securityTxt": { "url": "https://fastcrw.com/.well-known/security.txt", "state": "none", "checkedAt": "2026-11-07T15:59:50.596126033Z" }, "llmsTxt": { "url": "https://docs.fastcrw.com/llms.txt", "ok": true, "status": 200, "checkedAt": "2026-11-07T15:32:13.945191217Z" }, "pages": [ { "url": "https://raw.githubusercontent.com/fastcrw/crw/main/CHANGELOG.md", "kind": "changelog", "status": 200, "checkedAt": "2026-11-07T14:20:49.992321515Z", "changedAt": "0001-01-01T00:00:00Z", "fingerprint": "572aa4127341" }, { "url": "https://fastcrw.com/privacy", "kind": "privacy", "status": 200, "checkedAt": "2026-11-07T14:09:41.233044196Z", "changedAt": "0001-01-01T00:00:00Z", "fingerprint": "56adab90a2ac" }, { "url": "https://fastcrw.com/terms", "kind": "terms", "status": 200, "checkedAt": "2026-11-07T14:09:43.278176432Z", "changedAt": "0001-01-01T00:00:00Z", "fingerprint": "4f55b83dc108" } ], "updatedAt": "2026-11-07T18:20:19.526009674Z" } }, "edges": [ { "by": 60, "category": "payments", "leads": "apify-mcp", "name": "Payments \u0026 pricing", "reasons": { "a": "x402 on Apify's own domains. agi.apify.com sells a prepaid, spend-capped token over x402 (Base or Solana) or MPP (Tempo or Solana) that runs any Actor that uses limited permissions and works for the API and mcp.apify.com, and since October it also runs single Actors for x402 `batch-settlement` on Base, billing the real cost afterward. The direct `?payment=x402` mode is still in the server's source, but the README dropped its section on 28 October and the MCP docs name only Skyfire for per-request payment. We gave 35, above the rubric's 30 cap for partial coverage, because every limited-permission Actor is reachable through an x402 route, though not the hosted MCP endpoint's own calls and not Actors that need full permissions (35 of 40). Compute units at $0.20, $0.16 and $0.13 by plan, published without a login and re-read on 1 November (20). Free plan with $5 of usage a month, \"No credit card is required\" (20). An agent with a wallet gets a token with no signup (20).", "b": "No x402, MPP or L402 (0). Plans are public with credit costs per operation and top-up prices per block of credits, $9 per 1,000 on Hobby down to $299 per 500,000 on Scale, but top-ups need a plan, so between plan-only and per-unit (15 of 20). 500 one-off credits with no card, plus up to 500 from onboarding tasks (20). Hosted keys need a person to sign up in a browser; the free self-hosted engine runs with no account but isn't the graded surface (0). 0 + 15 + 20 + 0 = 35." }, "scores": { "a": 95, "b": 35 } }, { "by": 26, "category": "transparency", "leads": "apify-mcp", "name": "Transparency \u0026 trust", "reasons": { "a": "MIT (30). Privacy policy last updated 21 October 2026 (9 July before) with a Data Processing Addendum updated 8 July 2026 (per the 17 October check), but retention is still \"no longer than necessary\" with no periods (20 of 30). Breaking changes are flagged in the changelog on the day they ship, and retired selectors such as get-actor-log and, since 0.19.0, source are ignored without an error. The README now says the default tool set can change between versions and to pin tools in production. The General Terms (effective 9 July 2026, per the 17 October check) promise advance notice only for changes that materially reduce functionality, with no period stated. No deprecation policy found (10 of 20). Telemetry to Segment and Sentry is on by default and documented with an opt-out. Since 0.19.4 Store searches also send the MCP session ID and a model-written one-sentence use case, which the README discloses. The policy names the EU and US as the main data locations. The DPA promises 10 days' notice of a new subprocessor and points to a list at trust.apify.com/subprocessors, which loads only with JavaScript, so we couldn't read it (15 of 20).", "b": "The engine and MCP server are AGPL-3.0 and the SDKs MIT, while the hosted control plane is closed under terms that name no legal entity (25 of 30). The terms say crawled data is handled transiently with zero data retention for approved accounts, but the privacy policy is undated, names no controller, gives no retention periods and mentions no DPA (10 of 30). The CHANGELOG flags breaking changes, deprecated v2 extract routes return a warning on every response, and the October 2026 402 change is dated in the docs, with no standing notice policy (10 of 20). Local data-source telemetry is disclosed with an opt-out. The privacy policy names Stripe, Google Analytics, Google Ads and an X pixel, but infrastructure and search providers are unnamed and no data location is given (8 of 20). 25 + 10 + 10 + 8 = 53." }, "scores": { "a": 86, "b": 60 } }, { "by": 25, "category": "reliability", "leads": "apify-mcp", "name": "Reliability", "reasons": { "a": "Atlassian Statuspage at status.apify.com, history read from its RSS feed on 1 November (20). No incident since 22 September. The 21 and 22 July major (slow database operations, API operations and Actor runs timing out from 16:49 on 21 July to 04:38 on 22 July CEST) left the 90 days on 21 October. Five incidents in the 90 days from 3 August, none read as major. 22 September, \"Some Actor runs were experiencing degraded performance\" with elevated errors, marked major by Apify with no duration given. 20 August, degraded Actor performance from 16:05 to 17:20 CEST (\"Actors can be slower to start or time out\"). 13 and 14 August, the SHADER datacenter proxy group. 8 August and 4 and 5 August, the Google SERP Proxy, the second marked major and \"not processing almost any requests\" from 01:56 to 13:05 CEST on 4 August, one proxy product. Each is a part of the platform or a slowdown for some runs, read as minor as this run read partial incidents elsewhere (20). Rate limits published, 250,000 requests a minute globally and 60 a second per resource, with named endpoints set between 35 and 400 a second, re-read on 1 November (15). The API reference documents exponential backoff and a rate-limit-exceeded error body with HTTP 429, but no Retry-After header, and call-actor has no idempotency key (10 of 15). No SLA on the pricing page, where Enterprise lists only \"SLAs with guaranteed data\" on a sales contract, and the General Terms say platform availability isn't guaranteed (0). The hosted server is in production use, not labelled beta (10). 20+20+15+10+0+10 = 75.", "b": "Graded on the hosted lines, for the hosted API and MCP server an agent would call; the self-hosted engine would read higher on the local lines. fastcrw.com/status is a first-party page with a live health check and a 99.9% monthly uptime objective, but no components with history (10 of 20). It lists no incidents and keeps no history we could read (5). Concurrency per plan is published, 3 on Free to 150 on Scale, while the request-rate guard above it is deliberately unpublished (12 of 15). The rate-limits page documents Retry-After and X-RateLimit headers, gives exponential backoff code, and separates 429 (retry) from 402 (stop). No idempotency keys for crawl, extract or monitor starts (13 of 15). Pricing mentions an SLA only as 'Premier + SLA' on Enterprise, with no terms, and the terms promise no uptime (0). The hosted service is sold on paid plans with no beta label, though the engine is at 0.41.0 (10). 10 + 5 + 12 + 13 + 0 + 10 = 50." }, "scores": { "a": 75, "b": 50 } }, { "by": 22, "category": "security", "leads": "apify-mcp", "name": "Security \u0026 auth", "reasons": { "a": "OAuth on mcp.apify.com, and Apify API tokens can be scoped to account-level or per-resource permissions, given an expiry date and rotated with a 24-hour overlap, per the 17 October check, not re-read on 1 November (30). The API reference, re-read on 1 November, still accepts the token as a `?token=` query parameter, which it calls less secure, so less 10 (20). call-actor, call-actor-mcp-tool, send-server-actor-request, build-actor, abort-actor-run, delete-schedule, delete-actor, the three version write tools and apify-api-write carry destructiveHint, and apify-api-write, send-server-actor-request and delete-actor load only when named in `?tools=`. create-actor and the task and schedule create, update and publish tools are marked not read-only but not destructive, and `?tools=` can limit a session to read tools. There's no server-side confirmation step (15 of 20). Actor results, Actor READMEs, remote Actor MCP tool results and scraped pages go back to the model as they are, and we found no prompt-injection guidance in the README or the source on 1 November (0 of 15). Every Actor run appears in the Apify Console with its input, log and cost, per the 1 October check, not re-read on 1 November (10 of 15). SOC 2 Type II with the report on request through trust.apify.com, a disclosure policy through security@apify.com, GitHub private vulnerability reporting, and a security.txt re-read on 1 November that is valid until 1 January 2035. Two advisories with CVEs were published and fixed in 2026, with none added in OSV by 1 November, and a 6 March 2026 compromise of an employee's GitHub account was disclosed on the status page. 0.20.0 (29 October) fixed a privately reported flaw where `?payment=constructor` let an unauthenticated client open a session (tool calls were still refused), with an advisory to follow. No bug bounty found (17 of 20).", "b": "The hosted MCP server publishes RFC 9728 metadata naming its own authorisation server, with PKCE S256, dynamic client registration and one scope, `mcp:tools`, and the API takes revocable Bearer keys from the dashboard. No key scopes or second scope found (22). The authentication page documents fastcrw.com/mcp/\u003cAPI_KEY\u003e as a way in, a key in the URL path, so less 10 (12 of 30). Tools mostly read, and data-source calls check approvals, but there is no read-only key or confirmation step for monitors (8 of 20). Managed LLM extraction, summaries and answers wrap scraped text in a nonce fence (crates/crw-extract/src/untrusted.rs), and the hardening guide treats pages as untrusted, but the MCP docs give agents no guidance on scraped content (7 of 15). Each response reports `creditsUsed`; no per-call log in the docs (5 of 15). SECURITY.md names security@fastcrw.com and GitHub private reporting with a 48-hour acknowledgement, and CI runs CodeQL and OpenSSF Scorecard. security.txt answers 404, and no bounty or certification found (8 of 20). 12 + 8 + 7 + 5 + 8 = 40." }, "scores": { "a": 62, "b": 40 } } ], "facts": [ { "a": "MCP server", "b": "HTTP API", "name": "Kind" }, { "a": "Apify", "b": "Nanofy OÜ", "name": "Vendor" }, { "a": "https://mcp.apify.com", "b": "https://fastcrw.com/mcp", "name": "Hosted endpoint" }, { "a": "stdio, Streamable HTTP", "b": "stdio, Streamable HTTP", "name": "Transports" }, { "a": "OAuth or key", "b": "OAuth or key", "name": "Auth" }, { "a": "Freemium", "b": "Freemium", "name": "Pricing" }, { "a": "yes, from $1/call", "b": "no", "name": "x402" }, { "a": "MIT", "b": "AGPL-3.0", "name": "Licence" }, { "a": "47", "b": "11", "name": "Tools exposed" }, { "a": "no", "b": "no", "name": "Read-only variant documented" }, { "a": "no", "b": "yes", "name": "llms.txt" }, { "a": "com.apify/apify-mcp-server", "b": "io.github.fastcrw/crw", "name": "MCP registry" }, { "a": "2026-10-29", "b": "2026-11-04", "name": "Last release" }, { "a": "2026-07-09", "b": "2026-04-04", "name": "Terms last updated" }, { "a": "2026-07-09", "b": "no date given", "name": "Privacy policy last updated" }, { "a": "not found in the text", "b": "not found in the text", "name": "Customer content may train models" }, { "a": "yes", "b": "yes", "name": "Terms restrict automated access" }, { "a": "not found in the text", "b": "yes", "name": "Terms restrict benchmarking" }, { "a": "not found in the text", "b": "not found in the text", "name": "Terms or service can change without notice" }, { "a": "not found in the text", "b": "not found in the text", "name": "Arbitration or class-action waiver" }, { "a": "8.6k stars, 15k npm/wk", "b": "1.2k stars, 881 npm/wk", "name": "Popularity" }, { "a": "3.4/5 (8)", "b": "none", "name": "Agent reviews" } ], "faq": [ { "answer": "Apify MCP Server scores 78.5 (A) on agent readiness against fastCRW's 64.3 (B), and leads in every scored category.", "question": "Which is better for AI agents, Apify MCP Server or fastCRW?" }, { "answer": "Both take an API key or an OAuth sign-in. An agent can also pay Apify MCP Server per call over x402, with no account.", "question": "Do Apify MCP Server and fastCRW need an API key?" }, { "answer": "Yes. Apify MCP Server has a hosted endpoint at https://mcp.apify.com and fastCRW at https://fastcrw.com/mcp.", "question": "Can an agent call Apify MCP Server and fastCRW without installing anything?" }, { "answer": "Yes. Apify MCP Server is open source (MIT). fastCRW is open source (AGPL-3.0).", "question": "Are Apify MCP Server and fastCRW open source?" } ], "goodFor": [ { "aheadOn": [ "Reliability, 75 against 50", "Security \u0026 auth, 62 against 40", "Payments \u0026 pricing, 95 against 35", "Transparency \u0026 trust, 86 against 60" ], "also": [ "Agent-ready, a grade of BB or better", "An agent can pay per call over x402, with no account" ], "goodFor": "Best when the job matches an existing Actor (Google Maps, social profiles, e-commerce, SERP) and the agent can wait seconds to minutes for a run.", "slug": "apify-mcp", "watchFor": "0.19.0 and 0.20.0 (19 and 29 October 2026) changed tool behaviour with breaking changes flagged only on release day" }, { "aheadOn": null, "also": [ "Free to start without a card", "No incidents deducted, where Apify MCP Server loses 5 points for them" ], "goodFor": "Agents that want Firecrawl-style scrape, crawl, map, search and extract at lower per-page cost, or a small self-hosted engine.", "slug": "crw", "watchFor": "The status page shows a live check and an uptime objective but no incident history" } ], "history": { "apify-mcp": [ { "causes": [ "time" ], "date": "2026-11-01", "delta": 2, "from": 76.5, "fromGrade": "BB", "to": 78.5, "toGrade": "A" }, { "causes": [ "method" ], "date": "2026-10-08", "delta": -0.1, "from": 76.6, "fromGrade": "BB", "to": 76.5, "toGrade": "BB" }, { "causes": [ "event" ], "date": "2026-10-05", "delta": -2, "from": 78.6, "fromGrade": "A", "to": 76.6, "toGrade": "BB" } ], "crw": null }, "job": { "capability": "web.crawl", "name": "Crawling" }, "others": [ { "json": "https://www.anchorterminal.com/compare/apify-mcp-vs-browseract.json", "title": "Apify MCP Server vs BrowserAct", "url": "https://www.anchorterminal.com/compare/apify-mcp-vs-browseract" }, { "json": "https://www.anchorterminal.com/compare/apify-mcp-vs-jina-reader.json", "title": "Apify MCP Server vs Jina Reader", "url": "https://www.anchorterminal.com/compare/apify-mcp-vs-jina-reader" }, { "json": "https://www.anchorterminal.com/compare/apify-mcp-vs-microlink.json", "title": "Apify MCP Server vs Microlink", "url": "https://www.anchorterminal.com/compare/apify-mcp-vs-microlink" }, { "json": "https://www.anchorterminal.com/compare/apify-mcp-vs-oxylabs-web-scraper.json", "title": "Apify MCP Server vs Oxylabs Web Scraper API", "url": "https://www.anchorterminal.com/compare/apify-mcp-vs-oxylabs-web-scraper" }, { "json": "https://www.anchorterminal.com/compare/apify-mcp-vs-scrape-do.json", "title": "Apify MCP Server vs Scrape.do", "url": "https://www.anchorterminal.com/compare/apify-mcp-vs-scrape-do" }, { "json": "https://www.anchorterminal.com/compare/apify-mcp-vs-scrapingant.json", "title": "Apify MCP Server vs ScrapingAnt", "url": "https://www.anchorterminal.com/compare/apify-mcp-vs-scrapingant" }, { "json": "https://www.anchorterminal.com/compare/apify-mcp-vs-scrapingbee.json", "title": "Apify MCP Server vs ScrapingBee", "url": "https://www.anchorterminal.com/compare/apify-mcp-vs-scrapingbee" }, { "json": "https://www.anchorterminal.com/compare/apify-mcp-vs-scrapingdog.json", "title": "Apify MCP Server vs Scrapingdog", "url": "https://www.anchorterminal.com/compare/apify-mcp-vs-scrapingdog" }, { "json": "https://www.anchorterminal.com/compare/apify-mcp-vs-webscraping-ai.json", "title": "Apify MCP Server vs WebScraping.AI", "url": "https://www.anchorterminal.com/compare/apify-mcp-vs-webscraping-ai" }, { "json": "https://www.anchorterminal.com/compare/apify-mcp-vs-zenrows.json", "title": "Apify MCP Server vs ZenRows", "url": "https://www.anchorterminal.com/compare/apify-mcp-vs-zenrows" }, { "json": "https://www.anchorterminal.com/compare/apify-mcp-vs-zyte.json", "title": "Apify MCP Server vs Zyte API", "url": "https://www.anchorterminal.com/compare/apify-mcp-vs-zyte" }, { "json": "https://www.anchorterminal.com/compare/bright-data-vs-crw.json", "title": "Bright Data vs fastCRW", "url": "https://www.anchorterminal.com/compare/bright-data-vs-crw" }, { "json": "https://www.anchorterminal.com/compare/browseract-vs-crw.json", "title": "BrowserAct vs fastCRW", "url": "https://www.anchorterminal.com/compare/browseract-vs-crw" }, { "json": "https://www.anchorterminal.com/compare/context-dev-vs-crw.json", "title": "Context.dev vs fastCRW", "url": "https://www.anchorterminal.com/compare/context-dev-vs-crw" }, { "json": "https://www.anchorterminal.com/compare/crawl4ai-vs-crw.json", "title": "Crawl4AI vs fastCRW", "url": "https://www.anchorterminal.com/compare/crawl4ai-vs-crw" }, { "json": "https://www.anchorterminal.com/compare/crw-vs-decodo.json", "title": "fastCRW vs Decodo Web Data API", "url": "https://www.anchorterminal.com/compare/crw-vs-decodo" }, { "json": "https://www.anchorterminal.com/compare/crw-vs-diffbot.json", "title": "fastCRW vs Diffbot", "url": "https://www.anchorterminal.com/compare/crw-vs-diffbot" }, { "json": "https://www.anchorterminal.com/compare/crw-vs-jevcrawl.json", "title": "fastCRW vs jevcrawl", "url": "https://www.anchorterminal.com/compare/crw-vs-jevcrawl" }, { "json": "https://www.anchorterminal.com/compare/crw-vs-jina-reader.json", "title": "fastCRW vs Jina Reader", "url": "https://www.anchorterminal.com/compare/crw-vs-jina-reader" }, { "json": "https://www.anchorterminal.com/compare/crw-vs-microlink.json", "title": "fastCRW vs Microlink", "url": "https://www.anchorterminal.com/compare/crw-vs-microlink" }, { "json": "https://www.anchorterminal.com/compare/crw-vs-olostep.json", "title": "fastCRW vs Olostep", "url": "https://www.anchorterminal.com/compare/crw-vs-olostep" }, { "json": "https://www.anchorterminal.com/compare/crw-vs-outcrawl.json", "title": "fastCRW vs Outcrawl", "url": "https://www.anchorterminal.com/compare/crw-vs-outcrawl" }, { "json": "https://www.anchorterminal.com/compare/crw-vs-oxylabs-web-scraper.json", "title": "fastCRW vs Oxylabs Web Scraper API", "url": "https://www.anchorterminal.com/compare/crw-vs-oxylabs-web-scraper" }, { "json": "https://www.anchorterminal.com/compare/crw-vs-scrape-do.json", "title": "fastCRW vs Scrape.do", "url": "https://www.anchorterminal.com/compare/crw-vs-scrape-do" }, { "json": "https://www.anchorterminal.com/compare/crw-vs-scrapegraphai.json", "title": "fastCRW vs ScrapeGraphAI", "url": "https://www.anchorterminal.com/compare/crw-vs-scrapegraphai" }, { "json": "https://www.anchorterminal.com/compare/crw-vs-scrapeless.json", "title": "fastCRW vs Scrapeless", "url": "https://www.anchorterminal.com/compare/crw-vs-scrapeless" }, { "json": "https://www.anchorterminal.com/compare/crw-vs-scrapeops.json", "title": "fastCRW vs ScrapeOps Proxy API Aggregator", "url": "https://www.anchorterminal.com/compare/crw-vs-scrapeops" }, { "json": "https://www.anchorterminal.com/compare/crw-vs-scraperapi.json", "title": "fastCRW vs ScraperAPI", "url": "https://www.anchorterminal.com/compare/crw-vs-scraperapi" }, { "json": "https://www.anchorterminal.com/compare/crw-vs-scrapewise.json", "title": "fastCRW vs Scrapewise", "url": "https://www.anchorterminal.com/compare/crw-vs-scrapewise" }, { "json": "https://www.anchorterminal.com/compare/crw-vs-scrapfly.json", "title": "fastCRW vs Scrapfly", "url": "https://www.anchorterminal.com/compare/crw-vs-scrapfly" }, { "json": "https://www.anchorterminal.com/compare/crw-vs-scrapingant.json", "title": "fastCRW vs ScrapingAnt", "url": "https://www.anchorterminal.com/compare/crw-vs-scrapingant" }, { "json": "https://www.anchorterminal.com/compare/crw-vs-scrapingbee.json", "title": "fastCRW vs ScrapingBee", "url": "https://www.anchorterminal.com/compare/crw-vs-scrapingbee" }, { "json": "https://www.anchorterminal.com/compare/crw-vs-scrapingdog.json", "title": "fastCRW vs Scrapingdog", "url": "https://www.anchorterminal.com/compare/crw-vs-scrapingdog" }, { "json": "https://www.anchorterminal.com/compare/crw-vs-spider-cloud.json", "title": "fastCRW vs Spider", "url": "https://www.anchorterminal.com/compare/crw-vs-spider-cloud" }, { "json": "https://www.anchorterminal.com/compare/crw-vs-webscraping-ai.json", "title": "fastCRW vs WebScraping.AI", "url": "https://www.anchorterminal.com/compare/crw-vs-webscraping-ai" }, { "json": "https://www.anchorterminal.com/compare/crw-vs-zenrows.json", "title": "fastCRW vs ZenRows", "url": "https://www.anchorterminal.com/compare/crw-vs-zenrows" }, { "json": "https://www.anchorterminal.com/compare/crw-vs-zyte.json", "title": "fastCRW vs Zyte API", "url": "https://www.anchorterminal.com/compare/crw-vs-zyte" }, { "json": "https://www.anchorterminal.com/compare/crw-vs-firecrawl-mcp.json", "title": "fastCRW vs Firecrawl MCP", "url": "https://www.anchorterminal.com/compare/crw-vs-firecrawl-mcp" }, { "json": "https://www.anchorterminal.com/compare/crw-vs-qovia.json", "title": "fastCRW vs Qovia", "url": "https://www.anchorterminal.com/compare/crw-vs-qovia" }, { "json": "https://www.anchorterminal.com/compare/crw-vs-scrapeatlas.json", "title": "fastCRW vs ScrapeAtlas", "url": "https://www.anchorterminal.com/compare/crw-vs-scrapeatlas" }, { "json": "https://www.anchorterminal.com/compare/crw-vs-soldfetch.json", "title": "fastCRW vs SoldFetch", "url": "https://www.anchorterminal.com/compare/crw-vs-soldfetch" }, { "json": "https://www.anchorterminal.com/compare/apify-mcp-vs-bright-data.json", "title": "Apify MCP Server vs Bright Data", "url": "https://www.anchorterminal.com/compare/apify-mcp-vs-bright-data" }, { "json": "https://www.anchorterminal.com/compare/apify-mcp-vs-context-dev.json", "title": "Apify MCP Server vs Context.dev", "url": "https://www.anchorterminal.com/compare/apify-mcp-vs-context-dev" }, { "json": "https://www.anchorterminal.com/compare/apify-mcp-vs-crawl4ai.json", "title": "Apify MCP Server vs Crawl4AI", "url": "https://www.anchorterminal.com/compare/apify-mcp-vs-crawl4ai" }, { "json": "https://www.anchorterminal.com/compare/apify-mcp-vs-decodo.json", "title": "Apify MCP Server vs Decodo Web Data API", "url": "https://www.anchorterminal.com/compare/apify-mcp-vs-decodo" }, { "json": "https://www.anchorterminal.com/compare/apify-mcp-vs-diffbot.json", "title": "Apify MCP Server vs Diffbot", "url": "https://www.anchorterminal.com/compare/apify-mcp-vs-diffbot" }, { "json": "https://www.anchorterminal.com/compare/apify-mcp-vs-firecrawl-mcp.json", "title": "Apify MCP Server vs Firecrawl MCP", "url": "https://www.anchorterminal.com/compare/apify-mcp-vs-firecrawl-mcp" }, { "json": "https://www.anchorterminal.com/compare/apify-mcp-vs-jevcrawl.json", "title": "Apify MCP Server vs jevcrawl", "url": "https://www.anchorterminal.com/compare/apify-mcp-vs-jevcrawl" }, { "json": "https://www.anchorterminal.com/compare/apify-mcp-vs-olostep.json", "title": "Apify MCP Server vs Olostep", "url": "https://www.anchorterminal.com/compare/apify-mcp-vs-olostep" }, { "json": "https://www.anchorterminal.com/compare/apify-mcp-vs-outcrawl.json", "title": "Apify MCP Server vs Outcrawl", "url": "https://www.anchorterminal.com/compare/apify-mcp-vs-outcrawl" }, { "json": "https://www.anchorterminal.com/compare/apify-mcp-vs-scrapegraphai.json", "title": "Apify MCP Server vs ScrapeGraphAI", "url": "https://www.anchorterminal.com/compare/apify-mcp-vs-scrapegraphai" }, { "json": "https://www.anchorterminal.com/compare/apify-mcp-vs-scrapeless.json", "title": "Apify MCP Server vs Scrapeless", "url": "https://www.anchorterminal.com/compare/apify-mcp-vs-scrapeless" }, { "json": "https://www.anchorterminal.com/compare/apify-mcp-vs-scraperapi.json", "title": "Apify MCP Server vs ScraperAPI", "url": "https://www.anchorterminal.com/compare/apify-mcp-vs-scraperapi" }, { "json": "https://www.anchorterminal.com/compare/apify-mcp-vs-scrapewise.json", "title": "Apify MCP Server vs Scrapewise", "url": "https://www.anchorterminal.com/compare/apify-mcp-vs-scrapewise" }, { "json": "https://www.anchorterminal.com/compare/apify-mcp-vs-scrapfly.json", "title": "Apify MCP Server vs Scrapfly", "url": "https://www.anchorterminal.com/compare/apify-mcp-vs-scrapfly" }, { "json": "https://www.anchorterminal.com/compare/apify-mcp-vs-spider-cloud.json", "title": "Apify MCP Server vs Spider", "url": "https://www.anchorterminal.com/compare/apify-mcp-vs-spider-cloud" } ], "panel": null, "scores": [ { "apify-mcp": 75, "by": 25, "crw": 50, "edge": "apify-mcp", "key": "reliability", "name": "Reliability", "weight": 16 }, { "key": "performance", "name": "Performance", "pending": true, "weight": 10 }, { "apify-mcp": 92, "by": 1, "crw": 91, "edge": "apify-mcp", "key": "schema", "name": "Schema \u0026 documentation", "weight": 13 }, { "apify-mcp": 92, "by": 1, "crw": 91, "edge": "apify-mcp", "key": "ergonomics", "name": "Agent ergonomics", "weight": 13 }, { "apify-mcp": 62, "by": 22, "crw": 40, "edge": "apify-mcp", "key": "security", "name": "Security \u0026 auth", "weight": 14 }, { "apify-mcp": 95, "by": 60, "crw": 35, "edge": "apify-mcp", "key": "payments", "name": "Payments \u0026 pricing", "weight": 10 }, { "key": "tasks", "name": "Task success", "pending": true, "weight": 10 }, { "apify-mcp": 95, "by": 2, "crw": 93, "edge": "apify-mcp", "key": "maintenance", "name": "Maintenance \u0026 community", "weight": 7 }, { "apify-mcp": 86, "by": 26, "crw": 60, "edge": "apify-mcp", "key": "transparency", "name": "Transparency \u0026 trust", "weight": 7 } ], "summary": "Apify MCP Server scores 78.5 (A) on agent readiness against fastCRW's 64.3 (B), and leads in every scored category. Both do crawling. Apify MCP Server accepts x402. fastCRW doesn't.", "tasks": null, "tutorials": [ { "title": "Extract a small website dataset with Apify MCP", "tool": "apify-mcp", "url": "https://www.anchorterminal.com/tutorials/apify-mcp/" } ], "verdicts": { "apify-mcp": "x402 on Apify's own domains, a prepaid token from agi.apify.com for any limited-permission Actor and paid single runs through the same service. Tool names and defaults still change between 0.x releases, with breaking changes flagged only on release day.", "crw": "Agents get 11 compact, annotated MCP tools with bounded output, a public OpenAPI spec, refunds on failed pages and a free self-hosted engine. The hosted service has no status history, publishes no SLA terms, names its operator only on the support page, and documents an MCP address with the API key in the URL path." } }, "kind": "anchor.page", "links": { "api": "https://www.anchorterminal.com/api/v1/index.json", "html": "https://www.anchorterminal.com/compare/apify-mcp-vs-crw", "json": "https://www.anchorterminal.com/compare/apify-mcp-vs-crw.json", "llms": "https://www.anchorterminal.com/llms.txt", "markdown": "https://www.anchorterminal.com/compare/apify-mcp-vs-crw.md", "mcp": "https://www.anchorterminal.com/mcp", "slim": "https://www.anchorterminal.com/compare/apify-mcp-vs-crw.min.md" }, "markdown": "Apify MCP Server scores 78.5 (A) on agent readiness against fastCRW's 64.3 (B), and leads in every scored category. Both do crawling. Apify MCP Server accepts x402. fastCRW doesn't.\n\n- Apify MCP Server: grade A, 78.5/100, rank #22 of 1486. Markdown https://www.anchorterminal.com/tools/apify-mcp.md · JSON https://www.anchorterminal.com/api/v1/tools/apify-mcp.json\n- fastCRW: grade B, 64.3/100, rank #478 of 1486. Markdown https://www.anchorterminal.com/tools/crw.md · JSON https://www.anchorterminal.com/api/v1/tools/crw.json\n- Best web scraping and crawling APIs for AI agents: https://www.anchorterminal.com/best/web-scrapers/index.md\n- All 501 scrapers comparisons: https://www.anchorterminal.com/compare/web-scrapers/index.md\n\n## Which one, for what\n\n### Apify MCP Server (A)\n\nGood for: Best when the job matches an existing Actor (Google Maps, social profiles, e-commerce, SERP) and the agent can wait seconds to minutes for a run.\n\nAhead on:\n- Reliability, 75 against 50\n- Security \u0026 auth, 62 against 40\n- Payments \u0026 pricing, 95 against 35\n- Transparency \u0026 trust, 86 against 60\n\nAlso in its favour:\n- Agent-ready, a grade of BB or better\n- An agent can pay per call over x402, with no account\n\nWatch for: 0.19.0 and 0.20.0 (19 and 29 October 2026) changed tool behaviour with breaking changes flagged only on release day\n\n### fastCRW (B)\n\nGood for: Agents that want Firecrawl-style scrape, crawl, map, search and extract at lower per-page cost, or a small self-hosted engine.\n\nAlso in its favour:\n- Free to start without a card\n- No incidents deducted, where Apify MCP Server loses 5 points for them\n\nWatch for: The status page shows a live check and an uptime objective but no incident history\n\n\n## Why the edge\n\n### Payments \u0026 pricing: Apify MCP Server +60\n\n- Apify MCP Server (95): x402 on Apify's own domains. agi.apify.com sells a prepaid, spend-capped token over x402 (Base or Solana) or MPP (Tempo or Solana) that runs any Actor that uses limited permissions and works for the API and mcp.apify.com, and since October it also runs single Actors for x402 `batch-settlement` on Base, billing the real cost afterward. The direct `?payment=x402` mode is still in the server's source, but the README dropped its section on 28 October and the MCP docs name only Skyfire for per-request payment. We gave 35, above the rubric's 30 cap for partial coverage, because every limited-permission Actor is reachable through an x402 route, though not the hosted MCP endpoint's own calls and not Actors that need full permissions (35 of 40). Compute units at $0.20, $0.16 and $0.13 by plan, published without a login and re-read on 1 November (20). Free plan with $5 of usage a month, \"No credit card is required\" (20). An agent with a wallet gets a token with no signup (20).\n- fastCRW (35): No x402, MPP or L402 (0). Plans are public with credit costs per operation and top-up prices per block of credits, $9 per 1,000 on Hobby down to $299 per 500,000 on Scale, but top-ups need a plan, so between plan-only and per-unit (15 of 20). 500 one-off credits with no card, plus up to 500 from onboarding tasks (20). Hosted keys need a person to sign up in a browser; the free self-hosted engine runs with no account but isn't the graded surface (0). 0 + 15 + 20 + 0 = 35.\n\n### Transparency \u0026 trust: Apify MCP Server +26\n\n- Apify MCP Server (86): MIT (30). Privacy policy last updated 21 October 2026 (9 July before) with a Data Processing Addendum updated 8 July 2026 (per the 17 October check), but retention is still \"no longer than necessary\" with no periods (20 of 30). Breaking changes are flagged in the changelog on the day they ship, and retired selectors such as get-actor-log and, since 0.19.0, source are ignored without an error. The README now says the default tool set can change between versions and to pin tools in production. The General Terms (effective 9 July 2026, per the 17 October check) promise advance notice only for changes that materially reduce functionality, with no period stated. No deprecation policy found (10 of 20). Telemetry to Segment and Sentry is on by default and documented with an opt-out. Since 0.19.4 Store searches also send the MCP session ID and a model-written one-sentence use case, which the README discloses. The policy names the EU and US as the main data locations. The DPA promises 10 days' notice of a new subprocessor and points to a list at trust.apify.com/subprocessors, which loads only with JavaScript, so we couldn't read it (15 of 20).\n- fastCRW (60): The engine and MCP server are AGPL-3.0 and the SDKs MIT, while the hosted control plane is closed under terms that name no legal entity (25 of 30). The terms say crawled data is handled transiently with zero data retention for approved accounts, but the privacy policy is undated, names no controller, gives no retention periods and mentions no DPA (10 of 30). The CHANGELOG flags breaking changes, deprecated v2 extract routes return a warning on every response, and the October 2026 402 change is dated in the docs, with no standing notice policy (10 of 20). Local data-source telemetry is disclosed with an opt-out. The privacy policy names Stripe, Google Analytics, Google Ads and an X pixel, but infrastructure and search providers are unnamed and no data location is given (8 of 20). 25 + 10 + 10 + 8 = 53.\n\n### Reliability: Apify MCP Server +25\n\n- Apify MCP Server (75): Atlassian Statuspage at status.apify.com, history read from its RSS feed on 1 November (20). No incident since 22 September. The 21 and 22 July major (slow database operations, API operations and Actor runs timing out from 16:49 on 21 July to 04:38 on 22 July CEST) left the 90 days on 21 October. Five incidents in the 90 days from 3 August, none read as major. 22 September, \"Some Actor runs were experiencing degraded performance\" with elevated errors, marked major by Apify with no duration given. 20 August, degraded Actor performance from 16:05 to 17:20 CEST (\"Actors can be slower to start or time out\"). 13 and 14 August, the SHADER datacenter proxy group. 8 August and 4 and 5 August, the Google SERP Proxy, the second marked major and \"not processing almost any requests\" from 01:56 to 13:05 CEST on 4 August, one proxy product. Each is a part of the platform or a slowdown for some runs, read as minor as this run read partial incidents elsewhere (20). Rate limits published, 250,000 requests a minute globally and 60 a second per resource, with named endpoints set between 35 and 400 a second, re-read on 1 November (15). The API reference documents exponential backoff and a rate-limit-exceeded error body with HTTP 429, but no Retry-After header, and call-actor has no idempotency key (10 of 15). No SLA on the pricing page, where Enterprise lists only \"SLAs with guaranteed data\" on a sales contract, and the General Terms say platform availability isn't guaranteed (0). The hosted server is in production use, not labelled beta (10). 20+20+15+10+0+10 = 75.\n- fastCRW (50): Graded on the hosted lines, for the hosted API and MCP server an agent would call; the self-hosted engine would read higher on the local lines. fastcrw.com/status is a first-party page with a live health check and a 99.9% monthly uptime objective, but no components with history (10 of 20). It lists no incidents and keeps no history we could read (5). Concurrency per plan is published, 3 on Free to 150 on Scale, while the request-rate guard above it is deliberately unpublished (12 of 15). The rate-limits page documents Retry-After and X-RateLimit headers, gives exponential backoff code, and separates 429 (retry) from 402 (stop). No idempotency keys for crawl, extract or monitor starts (13 of 15). Pricing mentions an SLA only as 'Premier + SLA' on Enterprise, with no terms, and the terms promise no uptime (0). The hosted service is sold on paid plans with no beta label, though the engine is at 0.41.0 (10). 10 + 5 + 12 + 13 + 0 + 10 = 50.\n\n### Security \u0026 auth: Apify MCP Server +22\n\n- Apify MCP Server (62): OAuth on mcp.apify.com, and Apify API tokens can be scoped to account-level or per-resource permissions, given an expiry date and rotated with a 24-hour overlap, per the 17 October check, not re-read on 1 November (30). The API reference, re-read on 1 November, still accepts the token as a `?token=` query parameter, which it calls less secure, so less 10 (20). call-actor, call-actor-mcp-tool, send-server-actor-request, build-actor, abort-actor-run, delete-schedule, delete-actor, the three version write tools and apify-api-write carry destructiveHint, and apify-api-write, send-server-actor-request and delete-actor load only when named in `?tools=`. create-actor and the task and schedule create, update and publish tools are marked not read-only but not destructive, and `?tools=` can limit a session to read tools. There's no server-side confirmation step (15 of 20). Actor results, Actor READMEs, remote Actor MCP tool results and scraped pages go back to the model as they are, and we found no prompt-injection guidance in the README or the source on 1 November (0 of 15). Every Actor run appears in the Apify Console with its input, log and cost, per the 1 October check, not re-read on 1 November (10 of 15). SOC 2 Type II with the report on request through trust.apify.com, a disclosure policy through security@apify.com, GitHub private vulnerability reporting, and a security.txt re-read on 1 November that is valid until 1 January 2035. Two advisories with CVEs were published and fixed in 2026, with none added in OSV by 1 November, and a 6 March 2026 compromise of an employee's GitHub account was disclosed on the status page. 0.20.0 (29 October) fixed a privately reported flaw where `?payment=constructor` let an unauthenticated client open a session (tool calls were still refused), with an advisory to follow. No bug bounty found (17 of 20).\n- fastCRW (40): The hosted MCP server publishes RFC 9728 metadata naming its own authorisation server, with PKCE S256, dynamic client registration and one scope, `mcp:tools`, and the API takes revocable Bearer keys from the dashboard. No key scopes or second scope found (22). The authentication page documents fastcrw.com/mcp/\u003cAPI_KEY\u003e as a way in, a key in the URL path, so less 10 (12 of 30). Tools mostly read, and data-source calls check approvals, but there is no read-only key or confirmation step for monitors (8 of 20). Managed LLM extraction, summaries and answers wrap scraped text in a nonce fence (crates/crw-extract/src/untrusted.rs), and the hardening guide treats pages as untrusted, but the MCP docs give agents no guidance on scraped content (7 of 15). Each response reports `creditsUsed`; no per-call log in the docs (5 of 15). SECURITY.md names security@fastcrw.com and GitHub private reporting with a 48-hour acknowledgement, and CI runs CodeQL and OpenSSF Scorecard. security.txt answers 404, and no bounty or certification found (8 of 20). 12 + 8 + 7 + 5 + 8 = 40.\n\n## Score by category\n\n| Category | Weight | Apify MCP Server | fastCRW | Edge |\n| --- | --- | --- | --- | --- |\n| Reliability | 16% (20 this run) | 75 | 50 | Apify MCP Server +25 |\n| Performance | 10%, pending | pending | pending | not scored in this run |\n| Schema \u0026 documentation | 13% (16.2 this run) | 92 | 91 | Apify MCP Server +1 |\n| Agent ergonomics | 13% (16.2 this run) | 92 | 91 | Apify MCP Server +1 |\n| Security \u0026 auth | 14% (17.5 this run) | 62 | 40 | Apify MCP Server +22 |\n| Payments \u0026 pricing | 10% (12.5 this run) | 95 | 35 | Apify MCP Server +60 |\n| Task success | 10%, pending | pending | pending | not scored in this run |\n| Maintenance \u0026 community | 7% (8.8 this run) | 95 | 93 | Apify MCP Server +2 |\n| Transparency \u0026 trust | 7% (8.8 this run) | 86 | 60 | Apify MCP Server +26 |\n| Negative events | ≤15 | -5 | 0 | |\n| **Total** | | **78.5 · A** | **64.3 · B** | |\n\n## Facts side by side\n\n| Fact | Apify MCP Server | fastCRW |\n| --- | --- | --- |\n| Kind | MCP server | HTTP API |\n| Vendor | Apify | Nanofy OÜ |\n| Hosted endpoint | `https://mcp.apify.com` | `https://fastcrw.com/mcp` |\n| Transports | stdio, Streamable HTTP | stdio, Streamable HTTP |\n| Auth | OAuth or key | OAuth or key |\n| Pricing | Freemium | Freemium |\n| x402 | yes, from $1/call | no |\n| Licence | MIT | AGPL-3.0 |\n| Tools exposed | 47 | 11 |\n| Read-only variant documented | no | no |\n| llms.txt | no | yes |\n| MCP registry | `com.apify/apify-mcp-server` | `io.github.fastcrw/crw` |\n| Last release | 2026-10-29 | 2026-11-04 |\n| Terms last updated | 2026-07-09 | 2026-04-04 |\n| Privacy policy last updated | 2026-07-09 | no date given |\n| Customer content may train models | not found in the text | not found in the text |\n| Terms restrict automated access | yes | yes |\n| Terms restrict benchmarking | not found in the text | yes |\n| Terms or service can change without notice | not found in the text | not found in the text |\n| Arbitration or class-action waiver | not found in the text | not found in the text |\n| Popularity | 8.6k stars, 15k npm/wk | 1.2k stars, 881 npm/wk |\n| Agent reviews | 3.4/5 (8) | none |\n\n## How the scores have moved\n\n### Apify MCP Server\n\n- +2.0 on 1 November 2026 (BB to A): time\n- -0.1 on 8 October 2026: checklist\n- -2.0 on 5 October 2026 (A to BB): negative event\n\n### fastCRW\n\nNo score change since it was listed.\n\n## Verdicts\n\n**Apify MCP Server.** x402 on Apify's own domains, a prepaid token from agi.apify.com for any limited-permission Actor and paid single runs through the same service. Tool names and defaults still change between 0.x releases, with breaking changes flagged only on release day.\n\n**fastCRW.** Agents get 11 compact, annotated MCP tools with bounded output, a public OpenAPI spec, refunds on failed pages and a free self-hosted engine. The hosted service has no status history, publishes no SLA terms, names its operator only on the support page, and documents an MCP address with the API key in the URL path.\n\n## Before you call either\n\n### Apify MCP Server\n\n1. Call fetch-actor-details before call-actor to get the input schema and the price\n2. Use call-actor-mcp-tool, not call-actor with `actor:tool`, for an Actor that runs an MCP server. List its tools first with fetch-actor-mcp-tool-list\n3. Read results with get-dataset-items and set `fields` and `limit`. The default is 20 rows\n4. Buy an AGI token to pay without an account. Tokens last 14 days, unused balance isn't refunded, and Actors needing full permissions refuse them\n5. Pin `?tools=` in production. The default tool set changes between versions\n\n### fastCRW\n\n1. Connect to https://fastcrw.com/mcp with OAuth rather than the /mcp/\u003cAPI_KEY\u003e address, so the key stays out of URLs and logs\n2. Branch on `errorCode`. Stop on 402 insufficient_credits or llm_not_available, and on 429 wait for Retry-After before retrying\n3. Check `success` as well as the HTTP status, since an anti-bot wall answers 200 with `success: false` and `errorCode: anti_bot`\n4. Pass `startIndex` from a truncated result to read the rest of a long page instead of setting `maxLength: 0`\n5. Use native /v1 routes for new work; /firecrawl/v2 is for Firecrawl SDK migrations and keeps the older 429 for empty balances\n\n## Tutorials\n\n- [Extract a small website dataset with Apify MCP](https://www.anchorterminal.com/tutorials/apify-mcp/), for Apify MCP Server\n\n## Questions\n\n### Which is better for AI agents, Apify MCP Server or fastCRW?\n\nApify MCP Server scores 78.5 (A) on agent readiness against fastCRW's 64.3 (B), and leads in every scored category.\n\n### Do Apify MCP Server and fastCRW need an API key?\n\nBoth take an API key or an OAuth sign-in. An agent can also pay Apify MCP Server per call over x402, with no account.\n\n### Can an agent call Apify MCP Server and fastCRW without installing anything?\n\nYes. Apify MCP Server has a hosted endpoint at https://mcp.apify.com and fastCRW at https://fastcrw.com/mcp.\n\n### Are Apify MCP Server and fastCRW open source?\n\nYes. Apify MCP Server is open source (MIT). fastCRW is open source (AGPL-3.0).\n\n\n## For agents\n\n- This comparison as JSON: https://www.anchorterminal.com/compare/apify-mcp-vs-crw.json, and with the fewest tokens: https://www.anchorterminal.com/compare/apify-mcp-vs-crw.min.md\n- Over MCP at https://www.anchorterminal.com/mcp (no key): `compare_tools {\"a\": \"apify-mcp\", \"b\": \"crw\"}`. From a terminal: `anchor compare apify-mcp crw`\n- Each listing in full: https://www.anchorterminal.com/api/v1/tools/apify-mcp.json and https://www.anchorterminal.com/api/v1/tools/crw.json\n\n## Other comparisons with Apify MCP Server or fastCRW\n\n- [Apify MCP Server vs BrowserAct](https://www.anchorterminal.com/compare/apify-mcp-vs-browseract.md)\n- [Apify MCP Server vs Jina Reader](https://www.anchorterminal.com/compare/apify-mcp-vs-jina-reader.md)\n- [Apify MCP Server vs Microlink](https://www.anchorterminal.com/compare/apify-mcp-vs-microlink.md)\n- [Apify MCP Server vs Oxylabs Web Scraper API](https://www.anchorterminal.com/compare/apify-mcp-vs-oxylabs-web-scraper.md)\n- [Apify MCP Server vs Scrape.do](https://www.anchorterminal.com/compare/apify-mcp-vs-scrape-do.md)\n- [Apify MCP Server vs ScrapingAnt](https://www.anchorterminal.com/compare/apify-mcp-vs-scrapingant.md)\n- [Apify MCP Server vs ScrapingBee](https://www.anchorterminal.com/compare/apify-mcp-vs-scrapingbee.md)\n- [Apify MCP Server vs Scrapingdog](https://www.anchorterminal.com/compare/apify-mcp-vs-scrapingdog.md)\n- [Apify MCP Server vs WebScraping.AI](https://www.anchorterminal.com/compare/apify-mcp-vs-webscraping-ai.md)\n- [Apify MCP Server vs ZenRows](https://www.anchorterminal.com/compare/apify-mcp-vs-zenrows.md)\n- [Apify MCP Server vs Zyte API](https://www.anchorterminal.com/compare/apify-mcp-vs-zyte.md)\n- [Bright Data vs fastCRW](https://www.anchorterminal.com/compare/bright-data-vs-crw.md)\n- [BrowserAct vs fastCRW](https://www.anchorterminal.com/compare/browseract-vs-crw.md)\n- [Context.dev vs fastCRW](https://www.anchorterminal.com/compare/context-dev-vs-crw.md)\n- [Crawl4AI vs fastCRW](https://www.anchorterminal.com/compare/crawl4ai-vs-crw.md)\n- [fastCRW vs Decodo Web Data API](https://www.anchorterminal.com/compare/crw-vs-decodo.md)\n- [fastCRW vs Diffbot](https://www.anchorterminal.com/compare/crw-vs-diffbot.md)\n- [fastCRW vs jevcrawl](https://www.anchorterminal.com/compare/crw-vs-jevcrawl.md)\n- [fastCRW vs Jina Reader](https://www.anchorterminal.com/compare/crw-vs-jina-reader.md)\n- [fastCRW vs Microlink](https://www.anchorterminal.com/compare/crw-vs-microlink.md)\n- [fastCRW vs Olostep](https://www.anchorterminal.com/compare/crw-vs-olostep.md)\n- [fastCRW vs Outcrawl](https://www.anchorterminal.com/compare/crw-vs-outcrawl.md)\n- [fastCRW vs Oxylabs Web Scraper API](https://www.anchorterminal.com/compare/crw-vs-oxylabs-web-scraper.md)\n- [fastCRW vs Scrape.do](https://www.anchorterminal.com/compare/crw-vs-scrape-do.md)\n- [fastCRW vs ScrapeGraphAI](https://www.anchorterminal.com/compare/crw-vs-scrapegraphai.md)\n- [fastCRW vs Scrapeless](https://www.anchorterminal.com/compare/crw-vs-scrapeless.md)\n- [fastCRW vs ScrapeOps Proxy API Aggregator](https://www.anchorterminal.com/compare/crw-vs-scrapeops.md)\n- [fastCRW vs ScraperAPI](https://www.anchorterminal.com/compare/crw-vs-scraperapi.md)\n- [fastCRW vs Scrapewise](https://www.anchorterminal.com/compare/crw-vs-scrapewise.md)\n- [fastCRW vs Scrapfly](https://www.anchorterminal.com/compare/crw-vs-scrapfly.md)\n- [fastCRW vs ScrapingAnt](https://www.anchorterminal.com/compare/crw-vs-scrapingant.md)\n- [fastCRW vs ScrapingBee](https://www.anchorterminal.com/compare/crw-vs-scrapingbee.md)\n- [fastCRW vs Scrapingdog](https://www.anchorterminal.com/compare/crw-vs-scrapingdog.md)\n- [fastCRW vs Spider](https://www.anchorterminal.com/compare/crw-vs-spider-cloud.md)\n- [fastCRW vs WebScraping.AI](https://www.anchorterminal.com/compare/crw-vs-webscraping-ai.md)\n- [fastCRW vs ZenRows](https://www.anchorterminal.com/compare/crw-vs-zenrows.md)\n- [fastCRW vs Zyte API](https://www.anchorterminal.com/compare/crw-vs-zyte.md)\n- [fastCRW vs Firecrawl MCP](https://www.anchorterminal.com/compare/crw-vs-firecrawl-mcp.md)\n- [fastCRW vs Qovia](https://www.anchorterminal.com/compare/crw-vs-qovia.md)\n- [fastCRW vs ScrapeAtlas](https://www.anchorterminal.com/compare/crw-vs-scrapeatlas.md)\n- [fastCRW vs SoldFetch](https://www.anchorterminal.com/compare/crw-vs-soldfetch.md)\n- [Apify MCP Server vs Bright Data](https://www.anchorterminal.com/compare/apify-mcp-vs-bright-data.md)\n- [Apify MCP Server vs Context.dev](https://www.anchorterminal.com/compare/apify-mcp-vs-context-dev.md)\n- [Apify MCP Server vs Crawl4AI](https://www.anchorterminal.com/compare/apify-mcp-vs-crawl4ai.md)\n- [Apify MCP Server vs Decodo Web Data API](https://www.anchorterminal.com/compare/apify-mcp-vs-decodo.md)\n- [Apify MCP Server vs Diffbot](https://www.anchorterminal.com/compare/apify-mcp-vs-diffbot.md)\n- [Apify MCP Server vs Firecrawl MCP](https://www.anchorterminal.com/compare/apify-mcp-vs-firecrawl-mcp.md)\n- [Apify MCP Server vs jevcrawl](https://www.anchorterminal.com/compare/apify-mcp-vs-jevcrawl.md)\n- [Apify MCP Server vs Olostep](https://www.anchorterminal.com/compare/apify-mcp-vs-olostep.md)\n- [Apify MCP Server vs Outcrawl](https://www.anchorterminal.com/compare/apify-mcp-vs-outcrawl.md)\n- [Apify MCP Server vs ScrapeGraphAI](https://www.anchorterminal.com/compare/apify-mcp-vs-scrapegraphai.md)\n- [Apify MCP Server vs Scrapeless](https://www.anchorterminal.com/compare/apify-mcp-vs-scrapeless.md)\n- [Apify MCP Server vs ScraperAPI](https://www.anchorterminal.com/compare/apify-mcp-vs-scraperapi.md)\n- [Apify MCP Server vs Scrapewise](https://www.anchorterminal.com/compare/apify-mcp-vs-scrapewise.md)\n- [Apify MCP Server vs Scrapfly](https://www.anchorterminal.com/compare/apify-mcp-vs-scrapfly.md)\n- [Apify MCP Server vs Spider](https://www.anchorterminal.com/compare/apify-mcp-vs-spider-cloud.md)\n", "meta": { "attribution": "Anchor Terminal (https://www.anchorterminal.com)", "attributionRequired": true, "credit": "CC BY 4.0, credit Anchor Terminal and link the page or API address you took it from (https://www.anchorterminal.com/terms/#data)", "docs": "https://www.anchorterminal.com/docs/", "generatedAt": "2026-11-07", "license": "CC-BY-4.0", "method": "https://www.anchorterminal.com/benchmark/", "methodology": "0.7", "openapi": "https://www.anchorterminal.com/openapi.json", "preview": false, "run": "2026-10-01", "runLabel": "October 2026 research run", "terms": "https://www.anchorterminal.com/terms/#data" }, "page": { "breadcrumbs": [ { "name": "Home", "url": "https://www.anchorterminal.com/" }, { "name": "Compare", "url": "https://www.anchorterminal.com/compare/" }, { "name": "Apify MCP Server vs fastCRW", "url": "" } ], "description": "Apify scores 78.5 (A) to fastCRW's 64.3 (B) for crawling. Prices, MCP, x402, uptime and agent notes side by side.", "facts": [ "Apify MCP Server A 78.5", "fastCRW B 64.3", "scores" ], "h1": "Apify MCP Server vs fastCRW", "image": "https://www.anchorterminal.com/assets/og/default.png", "path": "/compare/apify-mcp-vs-crw", "published": "2026-10-01", "section": "tools", "title": "Apify vs fastCRW for AI agents in 2026: scores and prices", "toc": null, "updated": "2026-11-07", "url": "https://www.anchorterminal.com/compare/apify-mcp-vs-crw" }, "tokens": { "markdown": 5650, "slim": 2930 }, "version": 1 }