DSH Free Search vs Modsearch
These two listings overlap in this directory — they share a category or a use case, so they are candidates for the same job. Below is every field this directory checked, side by side: verification level, security scan, compatibility target and install command. Under the table: editorial notes on when to pick each side, and when neither is the right install.
DSH Free Search
DDDMUC
A multi-engine web search provider for DeepSeek Harness — free engines, Bing by default, no API key needed to start.
Read the listingModsearch
liustack
Free web search for DSH with no signup or key: structured JSON with citations, plus X search once Grok is installed.
Read the listing| Field | DSH Free Search | Modsearch |
|---|---|---|
| Verification | L3 · Install spec | L2 · Structured |
| Security scan | Unverified | Unverified |
| Health | Active | Active |
| dshTarget | 0.1.1-rc.1 || 0.1.1-rc.2 || 0.1.2-alpha.2 || 0.1.2-alpha.3 || 0.1.2-alpha.4 || 0.1.2-rc.1 || 0.1.5-rc.1 || 0.1.5-rc.2 | — |
| Last checked | 2026-09-18 | 2026-09-18 |
| Licence | MIT | MIT |
| Language | TypeScript | TypeScript |
| Stars (context only) | 201 | 501 |
| Categories | Tools & Capabilities | Tools & Capabilities |
| Use cases | Web Search | Web Search |
| Install command | dsh plugin --profile web add dsh-free-search | dsh plugin --profile web add @liustack/modsearch |
Every row is a public field of the two listings. This page does not score plugin quality.
Scenario notes
Both are free, MIT-licensed multi-engine search plugins with failover. Modsearch publishes SSRF-hardened fetch, per-engine key rotation, and takes no outside PRs. Free Search is more permissive about keys, ships a richer in-chat settings UI, and is explicit that web_fetch has no SSRF protection — plan to move to a keyed provider once search is load-bearing. Pick for fetch safety and citation shape, not for the word “free.”
When to pick DSH Free Search
Choose Modsearch when fetch safety and citation shape matter most: hardened path, documented engines, and a contract you can put in front of a parser. Prefer it for anything that will be cited back to humans or stored in a report.
When to pick Modsearch
Choose Free Search when you want a friendly default, in-chat settings, multi-engine failover without key ceremony, and you will constrain fetch yourself until the workflow is trusted. It is fine for experiments; upgrade the provider when search becomes critical path.
When neither fits
Neither is a reason to skip SSRF review. Keyless convenience is a trade, not a feature badge. If you already have a paid search API, wire that first and keep these as fallbacks — do not stack three search providers in the same prompt without naming which tool owns citations.
Which to pick
- DSH Free Search carries the higher verification level (L3 vs L2), meaning its install path was exercised further.
- They declare different harness targets (0.1.1-rc.1 || 0.1.1-rc.2 || 0.1.2-alpha.2 || 0.1.2-alpha.3 || 0.1.2-alpha.4 || 0.1.2-rc.1 || 0.1.5-rc.1 || 0.1.5-rc.2 vs undefined); the older target may simply not have caught up with the current preview line.
- Modsearch has the larger community (501 stars), though star counts measure attention rather than safety or quality.
Questions
- Are DSH Free Search and Modsearch interchangeable?
- They overlap in what they do (they share at least one category or use case), but they differ in install path and how far they were checked: DSH Free Search is L3, Modsearch is L2. Confirm the install command in the table above, then try it in an isolated profile.
- Which one is more current?
- DSH Free Search was checked more recently (2026-09-18 against 2026-09-18). That date is when this directory last verified the listing, not when the plugin last shipped a release.
- Can I install both?
- Sometimes — if they do not fight for the same tool name or UI slot. DSH Free Search is unverified and declares 0.1.1-rc.1 || 0.1.1-rc.2 || 0.1.2-alpha.2 || 0.1.2-alpha.3 || 0.1.2-alpha.4 || 0.1.2-rc.1 || 0.1.5-rc.1 || 0.1.5-rc.2; Modsearch is unverified and declares no harness target. A later install that re-registers the same capability can silently override the first. Safer path: try each in an isolated profile, compare the registered tools, then combine only what does not collide.