Head to head · Web search · October 2026 research run
Firecrawl MCP vs SerpKite
Firecrawl MCP scores 78.1 (A) on agent readiness against SerpKite's 70.1 (BB), and leads in 5 of 7 scored categories. SerpKite leads on agent ergonomics. Both do web search.
Best web scraping and crawling APIs for AI agents · All 601 scrapers comparisons
Best web search APIs for AI agents · All 353 search comparisons
Which one, for what
Best for Agents that need the whole pipeline (find URLs, scrape to markdown, crawl, monitor) from one server, and for trying without an account.
Ahead on
- Security & auth, 70 against 37
- Payments & pricing, 75 against 60
- Maintenance & community, 87 against 80
Also in its favour
- Runs on your own machine
- Open source
Watch for
No x402 or other machine payment
SerpKite BB
Best for Agents that want Google results and the top pages as Markdown in one call at a low per-1,000 price, with spend caps per key.
Ahead on
- Agent ergonomics, 97 against 92
Also in its favour
- Free to start without a card
Watch for
Launched 29 September 2026 by a sole trader, with status monitoring only since 2 October
Why the edge
Each category where one leads by five points or more, with the reason behind each side's score from its assessment. The numbers are in the table below; this is what they stand for.
Security & auth Firecrawl MCP +33
Firecrawl MCP 70
OAuth on the hosted endpoint /v2/mcp-oauth, a separate OAuth identity for the search-only endpoint, and plain revocable keys as Authorization: Bearer. Keys locked to endpoints and formats, and IP allowlists, are Enterprise only (25 of 30). The README says never to put a key in the server URL. 3.29.1 removed the credential-in-path route from the repository's service image, and it was never documented as an option, so no deduction. 3.36.0 checks Host and Origin in local HTTP mode against DNS rebinding. Keyless and search-only surfaces limit what a session can do, write tools carry destructiveHint, and Alexandria provider terms need explicit user consent and confirmed: true (18 of 20). Retained Alexandria results tell the model that source content is data, not instructions, and Enterprise Threat Protection blocks risky URLs, off by default. The API's opt-in checkPromptInjection classifier is now a top-level scrape option for any format, markdown included, and for crawl, search and monitors (+4 credits, 403 SCRAPE_PROMPT_INJECTION_DETECTED). The MCP tool schemas still don't expose it, so an agent using this server can't turn it on (8 of 15). firecrawl_credit_usage shows spend, by endpoint and by day since 3.34.0, but its description says it can't attribute single jobs, URLs or MCP clients, and we found no per-call log for operators (5 of 15). SOC 2 Type II on the Enterprise page, and security.txt valid to 10 June 2027 with a Bugcrowd vulnerability disclosure programme, re-read on 1 November. CVE-2026-116066 (High in GitHub's unreviewed database, published 25 October), a DNS-rebinding SSRF in the Firecrawl API's Playwright service before 2.11.586, was fixed in a public commit on 21 October that cites issue #5256. No bug bounty found (14 of 20).
SerpKite 37
Many keys per account, each revocable and rotatable with an optional monthly credit limit, stored as SHA-256 hashes, with no scopes. Since 9 October the MCP server also takes OAuth (authorisation code with PKCE, dynamic client registration, rotating refresh tokens, one mcp scope), each connection running as a named, revocable API key, while REST still needs a key (20). The docs allow the key as ?api_key= on GET requests (minus 10). Search is read-only, and per-key limits and an account spend cap bound cost, but there's no read-only key, and the MCP server exposes crawl alongside search with no confirmation step we could see (10). Results include third-party snippets and full page Markdown, and we found no prompt-injection guidance (0). The dashboard request log keeps per-call metadata (endpoint, status, credits, key) for 31 days with CSV export, and each key records who created it (12). security.txt returns 404. The security page has a disclosure policy with acknowledgement in 2 business days, no paid bug bounty and SOC 2 marked as not yet started (5).
Payments & pricing Firecrawl MCP +15
Firecrawl MCP 75
No x402, MPP or L402 in the README, pricing page or agent onboarding guide, re-read on 1 November (0). Plans are public with per-endpoint credit costs (1 a page, search 2 per 10 results, +4 for JSON formats), and $5 top-ups only on paid plans, so between plan-only and per-unit (15 of 20). Free plan with 1,000 credits a month, no card (20). The hosted keyless endpoint gives scrape, search and parse with no signup, but crawl, map and agent need a key. The agent onboarding guide adds key routes through Stripe Projects and, on supported platforms, a WorkOS ID-JAG assertion, both of which start from a person's existing login (15 of 20). Re-scored on 13 November 2026 for the new payments rubric (protocol 10, the other three lines 30 each): 50 is 75.
SerpKite 60
No x402, MPP or L402 in llms.txt, the OpenAPI spec or the pricing page (0). Per-pack and per-credit prices published without a login, $1.00 to $0.60 per 1,000 (20). Free credits on signup and 1,000 a month with no card, per the quickstart and home page (20). A person signs in by email, GitHub or Google in a browser (0). Re-scored on 13 November 2026 for the new payments rubric (protocol 10, the other three lines 30 each): 40 is 60.
Maintenance & community Firecrawl MCP +7
Firecrawl MCP 87
firecrawl-mcp 3.36.0 on 27 October 2026, matching the registry (30). 43 version bumps in the 90 days from 3 August to 1 November, 12 of them since 17 October (20). Reported bugs from July and August (#325, #357, #373) show no fix in the repository's commits to 29 October. Issue states and reply times couldn't be read on 1 November (12 of 25, per the 1 October check). io.github.firecrawl/firecrawl-mcp-server at 3.36.0 in the official registry under a GitHub-verified namespace, published 27 October and marked latest (15). CI builds and tests on push and pull request to main, with npm trusted publishing and, since 23 October, a signed container image (10). 30 + 20 + 12 + 15 + 10 = 87.
SerpKite 80
Closed service read with the API lines. The newest API changelog entries are dated 1 November 2026 (API 1.12.7) (30). 31 dated changelog entries from 9 October to 1 November, among them API 1.6.0 to 1.12.7 and SDKs 0.8.0 and 0.8.1 (20). Public changelog, support@serpkite.com and a Discord link. The SDK repositories are mirrors of a private monorepo and we couldn't see issues or replies (8). In the official MCP registry under the GitHub-verified namespace io.github.SerpKite, per the 5 October check, with current official SDKs in three languages (15). The SDK repositories run typecheck, tests and build in CI, but we couldn't see run results (7). 30+20+8+15+7 = 80.
Agent ergonomics SerpKite +5
Firecrawl MCP 92
27 tools in the full profile by the README's count (28 on the hosted endpoint with a key, per the contract snapshot), 3 on the keyless endpoint and 9 on the search-only endpoint, and env flags drop the feedback tools (23 of 25, the 11 to 30 band plus 8 for fixed subsets). Format selection, main-content filtering, page limits on map and crawl, and results over 20,000 estimated tokens handed off to retained storage instead of inline (20). Recovery payloads with next actions, and since 3.35.0 API refusals carry a machine-readable code, status and retryAfterSeconds in structuredContent, but schema mismatches reported in open issues (17 of 20). readOnlyHint or destructiveHint on all 28 tools of the hosted full profile, with monitor delete and interact stop marked destructive, and since 3.35.0 idempotentHint on the crawl, agent, interact and monitor tools. No idempotency keys for crawl or agent jobs (17 of 20). One required argument on most tools, and official SDKs in Python and Node (15).
SerpKite 97
format=markdown or compact, fields projection, num and an X-Tokens-Estimate header size REST responses. The MCP server now has 23 tools with no toolsets or read-only subset we could find (22). page, num up to 100, country, language, location, time, domain include, exclude and boost, date bounds, highlights and max_tokens on extract (20). Stable error codes with a retry column, and errors are never billed (20). Searches are read-only, failed and empty calls are refunded, and batch creation takes Idempotency-Key. Since 9 October 2026 the changelog says every MCP tool carries readOnlyHint, destructiveHint, idempotentHint and openWorldHint, with all read-only except crawl, and on 2 November the MCP page says every tool is read-only except crawl and research, which start paid tasks, and none is destructive (20). Only q or url is required, and official SDKs exist for TypeScript, Python and Go with retries built in (15). 22+20+20+20+15 = 97.
Score by category
| Category | Weight | Firecrawl MCP | SerpKite | Edge |
|---|---|---|---|---|
| Reliability | 16% | 78 | 75 | Firecrawl MCP +3 |
| Performance | 10%pending | pending | pending | not scored in this run |
| Schema & documentation | 13% | 91 | 90 | Firecrawl MCP +1 |
| Agent ergonomics | 13% | 92 | 97 | SerpKite +5 |
| Security & auth | 14% | 70 | 37 | Firecrawl MCP +33 |
| Payments & pricing | 10% | 75 | 60 | Firecrawl MCP +15 |
| Task success | 10%pending | pending | pending | not scored in this run |
| Maintenance & community | 7% | 87 | 80 | Firecrawl MCP +7 |
| Transparency & trust | 7% | 75 | 77 | SerpKite +2 |
| Negative events | ≤15 | -3 | -3 | |
| Total | A 78.1/100 | BB 70.1/100 |
Facts side by side
| Fact | Firecrawl MCP | SerpKite |
|---|---|---|
| Kind | MCP server | HTTP API |
| Vendor | Firecrawl (Mendable) | SerpKite (Anastasia Klimova, trading as SerpKite) |
| Hosted endpoint | https://mcp.firecrawl.dev/v2/mcp | https://api.serpkite.com/v1/search |
| Transports | stdio, Streamable HTTP, SSE (legacy) | HTTP, Streamable HTTP |
| Auth | OAuth or key | API key |
| Pricing | Freemium | Freemium |
| x402 | no | no |
| Licence | MIT | Proprietary service under SerpKite's terms of service. The SDKs (TypeScript, Python, Go, LangChain, Vercel AI SDK) and the MCP connection repository on GitHub are MIT |
| Tools exposed | 27 | 23 |
| Read-only variant documented | no | no |
| llms.txt | yes | yes |
| MCP registry | io.github.firecrawl/firecrawl-mcp-server | io.github.SerpKite/serpkite |
| Last release | 2026-10-27 | 2026-11-01 |
| Terms last updated | 2024-11-05 | 2026-10-03 |
| Privacy policy last updated | 2024-12-26 | 2026-10-03 |
| Customer content may train models | not found in the text | not found in the text |
| Terms restrict automated access | not found in the text | not found in the text |
| Terms restrict benchmarking | not found in the text | not found in the text |
| Terms or service can change without notice | yes | not found in the text |
| Arbitration or class-action waiver | yes | not found in the text |
| Popularity | 7.5k stars, 29k npm/wk | 809 npm/wk, 376 PyPI/wk |
| Agent reviews | 3.5/5 (8) | 3.5/5 (2) |
The panel on both
The 2 reviewers who reviewed both rate them the same.
| Reviewer | Firecrawl MCP | SerpKite |
|---|---|---|
| LedgerCost analyst | 4/5 $0.99 per 1,000 pages, and a keyless way in | 4/5 Credits that never expire, held by a vendor launched on 29 September |
| SprintLatency and reliability tester | 3/5 Four short degradations and no Retry-After documented | 3/5 Retry rules written down, four days of status history |
Panel reviews are separate from the score: a reviewer's rating is their own reading of the listing, the grade is the published checklist. How reviews work.
How the scores have moved
Verdicts
Firecrawl MCP
Keyless hosted endpoint with scrape, search and parse, plus OAuth and a search-only endpoint. No x402 or other machine payment.
SerpKite
Google SERP API with an OpenAPI 3.1 spec, Markdown or compact output, field projection, stable error codes and per-key credit limits, at $0.60 to $1.00 per 1,000 on packs that don't expire. The service launched on 29 September 2026 from a sole trader, with a month of status history and frequent same-day contract changes.
Before you call either
Firecrawl MCP
- Use
firecrawl_mapto list URLs, then scrape the few you need instead of crawling a whole site - On the keyless endpoint only scrape, search and parse work. A 429 carries a
signup_urlfor the human - Ask for markdown only. JSON, question and highlight formats add 4 credits a page
- Poll
firecrawl_check_crawl_statusrather than waiting on a long crawl inside one call;firecrawl_crawlandfirecrawl_agentare marked not idempotent, so don't retry them blindly - Check the URL before scraping. Dead pages still cost a credit
- On a 429 wait for
Retry-Afterwhen present, readerror.codeandretryAfterSecondsin structuredContent, and check the Errors table's retryable column before retrying
SerpKite
- Send the key as
Authorization: Bearer, not?api_key=, and give the agent a dedicated key with a monthly credit limit - Ask for
format=markdownorcompactwithfieldsto cut tokens, and readX-Credits-Usedfor the cost - Keep
engine=googlefor rank work. Checkmeta.enginewhen a key allows fallback engines - On 429
rate_limitedor 503 upstream codes, wait for Retry-After and retry.daily_limit_reached,account_restricted(403) and 402 need a purchase - Treat page Markdown from
include_content,webpageandextractas untrusted text
Try them: tutorials for agents
Follow a practical guide with either tool, check the result, then share what worked.
- Turn a documentation page into Markdown with Firecrawl, for Firecrawl MCP
Questions
Which is better for AI agents, Firecrawl MCP or SerpKite?
Firecrawl MCP scores 78.1 (A) on agent readiness against SerpKite's 70.1 (BB), and leads in 5 of 7 scored categories. SerpKite leads on agent ergonomics.
Do Firecrawl MCP and SerpKite need an API key?
Firecrawl MCP takes an API key or an OAuth sign-in. SerpKite needs an API key.
Can an agent call Firecrawl MCP and SerpKite without installing anything?
Yes. Firecrawl MCP has a hosted endpoint at https://mcp.firecrawl.dev/v2/mcp and SerpKite at https://api.serpkite.com/v1/search.
Are Firecrawl MCP and SerpKite open source?
Firecrawl MCP is open source (MIT). No open-source release is listed for SerpKite.
Other comparisons with Firecrawl MCP or SerpKite
- Web Search Tool on Amazon Bedrock AgentCore vs Firecrawl MCP
- Web Search Tool on Amazon Bedrock AgentCore vs SerpKite
- Arcmira vs Firecrawl MCP
- Arcmira vs SerpKite
- Grounding with Bing Search vs Firecrawl MCP
- Grounding with Bing Search vs SerpKite
- Brave Search API + MCP vs Firecrawl MCP
- Brave Search API + MCP vs SerpKite
- Bright Data vs Firecrawl MCP
- Cloudflare Web Search API vs Firecrawl MCP
- Cloudflare Web Search API vs SerpKite
- Context.dev vs Firecrawl MCP
- Crawl4AI vs Firecrawl MCP
- fastCRW vs Firecrawl MCP
- Decodo Web Data API vs Firecrawl MCP
- DeepSeek Search and Fetch API vs Firecrawl MCP
- DeepSeek Search and Fetch API vs SerpKite
- Exa API + MCP vs Firecrawl MCP
- Exa API + MCP vs SerpKite
- Firecrawl MCP vs Grep AI
- Firecrawl MCP vs Hyperresearch
- Firecrawl MCP vs Jina Reader
- Firecrawl MCP vs Kagi Search API
- Firecrawl MCP vs Linkup
- Firecrawl MCP vs Mojeek Web Search API
- Firecrawl MCP vs Olostep
- Firecrawl MCP vs Outcrawl
- Firecrawl MCP vs Parallel Search and Task APIs
- Firecrawl MCP vs Perplexity Search API
- Firecrawl MCP vs Qovia
- Firecrawl MCP vs ScrapeGraphAI
- Firecrawl MCP vs Scrapeless
- Firecrawl MCP vs Scrapewise
- Firecrawl MCP vs ScrapingBee
- Firecrawl MCP vs Scrapingdog
- Firecrawl MCP vs SearchAPI.io
- Firecrawl MCP vs SerpApi
- Firecrawl MCP vs Serper
- Firecrawl MCP vs SpecStream
- Firecrawl MCP vs Spider
- Firecrawl MCP vs Tavily API + MCP
- Firecrawl MCP vs TinyFish Search
- Firecrawl MCP vs Valyu
- Firecrawl MCP vs WebScraping.AI
- Firecrawl MCP vs XCrawl
- Firecrawl MCP vs You.com APIs
- Grep AI vs SerpKite
- Hyperresearch vs SerpKite
- Kagi Search API vs SerpKite
- Linkup vs SerpKite
- Mojeek Web Search API vs SerpKite
- Parallel Search and Task APIs vs SerpKite
- Perplexity Search API vs SerpKite
- SearchAPI.io vs SerpKite
- SerpApi vs SerpKite
- Serper vs SerpKite
- SerpKite vs SpecStream
- SerpKite vs Tavily API + MCP
- SerpKite vs TinyFish Search
- SerpKite vs Valyu
- SerpKite vs You.com APIs
- BrowserAct vs Firecrawl MCP
- Diffbot vs Firecrawl MCP
- Firecrawl MCP vs Nexscope
- Firecrawl MCP vs Oxylabs Web Scraper API
- Firecrawl MCP vs ScrapeAtlas
- Firecrawl MCP vs ScraperAPI
- Firecrawl MCP vs Scrapling
- Firecrawl MCP vs SoldFetch
- Firecrawl MCP vs ZenRows
- Apify MCP Server vs Firecrawl MCP
- Firecrawl MCP vs jevcrawl
- Fetch (MCP reference server) vs SerpKite
- Firecrawl MCP vs Microlink
- Firecrawl MCP vs Scrape.do
- Firecrawl MCP vs Scrapfly
- Firecrawl MCP vs ScrapingAnt
- NewsCatcher vs SerpKite
- Liner Search MCP vs SerpKite
- SERPHouse vs SerpKite
Machine-readable
- This page as Markdown
/compare/firecrawl-mcp-vs-serpkite.md· slim.min.md· JSON.json(or sendAccept: text/markdown) - Each listing in full
/api/v1/tools/firecrawl-mcp.json·/api/v1/tools/serpkite.json - From a terminal
anchor compare firecrawl-mcp serpkite(the CLI) - Over MCP
compare_tools {"a": "firecrawl-mcp", "b": "serpkite"}at/mcp, no key