DEV.co
MCP Servers · deedy5

ddgs

DDGS is a Python metasearch library that aggregates web search results from multiple backends (Bing, DuckDuckGo, Google, Brave, etc.) via a unified API. It offers CLI, REST API (FastAPI), and MCP server interfaces, supporting text, image, video, news, and book searches with region and safe-search filtering.

Source: GitHub — github.com/deedy5/ddgs
2.8k
GitHub stars
267
Forks
Python
Primary language
MIT
License (OSI-approved)

Key facts

Objective fields from the source. Values we can't verify are shown as “Unknown” rather than guessed.

FieldValue
Repositorydeedy5/ddgs
Ownerdeedy5
Primary languagePython
LicenseMIT — OSI-approved
Stars2.8k
Forks267
Open issues21
Latest releasev9.14.4 (2026-05-15)
Last updated2026-05-23
Sourcehttps://github.com/deedy5/ddgs

What ddgs is

Python ≥3.10 metasearch aggregator supporting 10+ backend engines with lazy-loaded DDGS class, proxy/timeout configuration, and pluggable transport layers (HTTP, stdio via MCP). Exposes search functions returning structured JSON lists with filtering by region, safe-search level, time limit, and custom backend selection.

Quickstart

Get the ddgs source

Clone the repository and explore it locally.

terminalbash
git clone https://github.com/deedy5/ddgs.gitcd ddgs# follow the project's README for install & configuration

Need it deployed, integrated, or customized instead? DEV.co ships production installs.

Best use cases

Multi-source search aggregation in AI/LLM applications

Use MCP server integration with Claude Desktop or Cursor to provide LLMs access to diverse search backends without vendor lock-in. Enables fallback search across 10+ engines if one is unavailable or censored.

Privacy-respecting metasearch infrastructure

Deploy as self-hosted REST API or CLI tool to aggregate searches while controlling data retention, proxy rules, and backend selection. Useful for organizations preferring distributed search vs. single-vendor dependency.

Content extraction and multi-media search pipelines

Combine text(), images(), videos(), news(), and extract() methods in data pipelines for automated research, price monitoring, or threat intelligence workflows requiring diverse result types.

Implementation considerations

  • Requires Python ≥3.10; plan for environment setup and dependency management (base install vs. [api] or [mcp] extras).
  • Third-party backend availability and rate-limiting are outside DDGS control—implement circuit-breaker patterns and timeout tuning (default 5s) for resilience.
  • Proxy support (http/https/socks5) available; ensure proxy infrastructure is in place if using behind corporate firewalls or for geographic distribution.
  • Backend auto-selection ('auto' default) may silently degrade if a preferred engine is unavailable; explicitly specify backends for production reliability.
  • Result structure varies by engine and search type; normalize/validate output before downstream consumption (title, href/url, body fields not guaranteed across all backends).

When to avoid it — and what to weigh

  • Requiring guaranteed uptime or commercial SLA — DDGS depends on third-party search engines (Bing, DuckDuckGo, Google, etc.) that may block, rate-limit, or change APIs. No guarantee of service availability or support from the library maintainer.
  • Need for strict legal compliance with search engine ToS — Automated aggregation of results from multiple search engines may violate their terms of service. Organizations with strict legal requirements should review and obtain explicit permission from each backend provider.
  • Expecting real-time, high-volume enterprise search — Metasearch introduces latency aggregating multiple backends and is subject to rate-limiting by upstream services. Not designed for high-throughput production search where single-engine reliability and performance SLA matter.
  • Operating in restricted jurisdictions or with banned engines — Some backends (Google, Bing) are blocked in certain countries. DDGS' fallback model helps but does not guarantee access; verify backend availability in your target region before deployment.

License & commercial use

MIT License (permissive OSI-compliant). Allows unrestricted use, modification, and distribution with attribution. No copyleft restrictions; suitable for proprietary and open-source projects.

MIT License permits commercial use without restriction. However, commercial viability depends entirely on third-party search engine availability, ToS compliance, and rate-limit tolerance. Verify that aggregating and reselling search results from Bing, Google, DuckDuckGo, etc. complies with their terms of service. No indemnification or support from the DDGS project. Requires legal review before monetization.

DEV.co evaluation signals

Editorial assessment — not user reviews. Directional, with an explicit confidence level.

SignalAssessment
MaintenanceActive
DocumentationAdequate
License clarityClear
Deployment complexityLow
DEV.co fitGood
Assessment confidenceHigh
Security considerations

DDGS itself has no authentication or authorization layer; deploy REST API behind reverse proxy with TLS, API keys, and access controls. Proxy parameter allows SOCKS5/HTTPS but no secret management guidance provided. Aggregating search results may expose user queries and result metadata; ensure logging/retention policies comply with data-protection regulations (GDPR, CCPA). Dependency on third-party engines means upstream security incidents (e.g., engine compromised, man-in-the-middle on results) inherit directly. No audit trail or encrypted storage. Verify dependencies (FastAPI, httpx, etc.) for CVEs before production use.

Alternatives to consider

SearXNG

Open-source metasearch engine with web UI, more mature ecosystem, stronger focus on privacy. Heavier deployment (Jinja2, Redis optional). Better for end-user-facing search; DDGS better for programmatic integration.

Brave Search API

Single commercial search engine with indexing, API, and official support. No aggregation, but more reliable uptime and ToS clarity. Trade-off: vendor lock-in vs. DDGS' flexibility.

Google Custom Search Engine (CSE)

Official Google API with ToS, quotas, and support. Limited free tier; paid model. No aggregation. Better for enterprise needing guaranteed availability and compliance; DDGS suits cost-sensitive / open-source use.

Software development agency

Build on ddgs with DEV.co software developers

DDGS is MIT-licensed and production-ready for programmatic search aggregation. Start with pip install ddgs, review search engine ToS compliance, and scale via REST API or MCP integration.

Talk to DEV.co

Related open-source tools

Surfaced by semantic similarity across the DEV.co open-source index.

Related on DEV.co

Explore the category and the services that help you build with it.

ddgs FAQ

Will aggregating search results from Bing, Google, DuckDuckGo, etc. violate their ToS?
Potentially. Most search engines prohibit automated scraping or commercial redistribution without permission. DDGS is a tool; legal responsibility is yours. Contact each engine provider or consult legal counsel before commercial deployment.
What happens if one backend is unavailable or rate-limited?
With backend='auto', DDGS will try other engines; results degrade gracefully but latency may increase. Explicitly specifying a backend (e.g., backend='duckduckgo') will fail if that engine is unreachable. Implement timeouts and fallback logic in your application.
Can I use DDGS in a commercial product?
MIT License permits it. You must verify compliance with search engine ToS and ensure you have the right to aggregate and redistribute their results. No warranty or support from DDGS maintainers. Legal review strongly recommended.
How do I deploy DDGS for high availability?
Use REST API with multiple instances behind a load balancer and reverse proxy (nginx). Add caching, circuit-breakers, and custom timeout tuning. For LLM integration, MCP server is simpler but single-process; run replicas and manage at orchestration layer (Docker, Kubernetes).

Software development & web development with DEV.co

Need help beyond evaluating ddgs? DEV.co is a software development agency offering software development services and web development for teams of every size. Our software developers and web developers build custom software, web applications, APIs, and mcp servers integrations — and maintain them long-term.

Ready to build a metasearch solution?

DDGS is MIT-licensed and production-ready for programmatic search aggregation. Start with pip install ddgs, review search engine ToS compliance, and scale via REST API or MCP integration.