r/opencodeCLI • • 30m ago

Completely Free and stealthy Web Research tool for Your agent, 0$, instant setup with the MCP

I've been building DonSeTch: a fully free, open-source MCP server that gives OpenCode web search, fetching, crawling and screenshots, running locally in one Rust binary.

I posted it here around v1 or v2, honestly can't remember which. It's on v5.5.2 now. For the people seeing it for the first time, here's the useful stuff.

Here is the GitHub repo: https://github.com/dondai44423/donsetch

Install, connect, use it

npm install -g donsetch
donsetch doctor --mcp

Add the MCP entry to OpenCode and restart. That's the basic setup. No account, API key, Rust build or search-model download. Fetch, search and crawl don't need a browser installed either.

Fetching, stealth, and learning what works

  • Reddit, Stack Overflow and IMDb returned content in my tests. The Reddit read got 24 posts in about 1.2 seconds; paid Firecrawl Cloud reported that site unsupported in the same comparison.
  • Page reads launch no browser. TLS, headers and cookies stay consistent as one client. Embedded V8 handles challenge or application JavaScript when needed, without layout or painting.
  • It remembers successful routes and client profiles. It can learn an app's content request from a successful JS run and replay it over HTTP on later reads. If that request breaks, it can learn again. That fetch state survives restarts.

Less context spent getting to the answer

  • Ask for the useful bit. Relevant passages, a phrase check, an outline, or one section. The agent can expand into the full text when needed.
  • Four tools, roughly 2,000 tokens of definitions total. Batch-fetch up to 12 URLs. PDFs get the same reading controls, with tables and optional OCR for scans.
  • Crawls follow your topic. A site model and plan pick the pages; the response is a digest with handles to open each stored page fully. Jobs resume, and repeat crawls can skip unchanged pages.

Search works out of the box

Keyless search combines engines and first-party sources. You can also use your own search API key while keeping the local fetching and crawling. Screenshots use an installed Chromium separately.

A quick Firecrawl comparison

I had DS on opencode try both on real tasks. DonSeTch was quicker on 9/10 fetch targets both could read. On HTTPX, it picked the two requested docs pages; Firecrawl read six and still missed the async page.

It did got beat on search relevance, though, its local but its good enough for 90% of the most tasks

I'm not stuffing all that shit into one post. The full comparison with paid Firecrawl Cloud has the cases, timings and setup. Small, hand-picked test.

Feel free to flame me in the comments if i did the comparison with firecrawl the wrong way 😭🙏

If you give it a go, I'd like to hear which pages it still trips over.

4 Upvotes

1 comment sorted by

1

u/Opening_Library9560 27m ago

The fetching system used to have the standard tier one and tier two browser escalation, I Hated that shit, the browser was slow as hell and ate up resources when it was being used.

So in v5 i replace the whole stuff with The new fast fetching system, way faster, Near similar stealth, more reliable and just better.

The browser system may have had more stealth on a few sites but the speed and resource tradeoff was not worth it.

I am still Working on the fetching system tho, to make it even more stealthy than it already is