Fetch (reference) vs DuckDuckGo search
Both are web search & scraping MCP servers, and we ran both through the same test (page read, web search) in each app. Fetch (reference) passed 3 of 4 apps we tested it in; DuckDuckGo search passed 3 of 4.
Test results side by side
| Fetch (reference) | DuckDuckGo search | |
|---|---|---|
| Claude Code | Passed 2026-10-19 | Failed 2026-10-13 |
| Cursor | Passed 2026-10-19 | Passed 2026-10-13 |
| Claude Desktop | Passed 2026-10-14 | Passed 2026-10-14 |
| ChatGPT (Codex) | Failed 2026-10-20 | Passed 2026-10-14 |
| Tools exposed (protocol check) | 1 tools | 3 tools |
| GitHub stars | 91,266 (shared repo) | 1,536 |
| License | NOASSERTION | MIT |
| Last push | 2026-10-13 | 2026-09-04 |
Results from our own harness runs, dated per cell. Stars and last push from GitHub at our last data refresh. We don’t pick a winner here: which one fits depends on your app and setup.
What each does
Fetch (reference): Fetches a web page and returns it as Markdown so the agent can read it.
DuckDuckGo search: Web search via DuckDuckGo plus page fetching, no API key.
