exa vs apify-mcp-server
In run 20260717T113200Z-7113, exa passed 7 of 7 applicable suite tasks (median tool-call latency 221 ms) and apify-mcp-server passed 6 of 7 (median 15737 ms). Both received byte-identical task inputs under identical timeout, retry, and concurrency rules.
| exa Tested | apify-mcp-server Tested | |
|---|---|---|
| Results | ||
| Suite success rate | 100% (7 applicable tasks) ▲ leads | 86% (7 applicable tasks) |
| Performance | ||
| Median latency (p50) | 221 ms ▲ leads | 15737 ms |
| Tail latency (p95) | 462 ms ▲ leads | 22809 ms |
| Cost | ||
| Cost per task | ~$0.007 (1 requests) | ~$0.004 |
| Capabilities | ||
| Suite task types supported | scrape_markdown, web_search | scrape_markdown, web_search |
Cost is shown in each service's native billing unit and is never compared numerically across services. Full methodology: how these numbers are produced.