Skip to main content
Glama
ddgs-mcp

ddgs-mcp

by marcinkuk

ddgs-mcp

A Model Context Protocol (MCP) server that exposes DDGS (Dux Distributed Global Search) — a keyless, multi-engine web metasearch — to AI agents.

It is a drop-in, more reliable alternative to a single SearXNG instance: instead of one upstream that gets IP-banned and poisons every query, DDGS fans each call out over several backends (DuckDuckGo, Bing, Brave, Google, Mojeek, Startpage, Yahoo, Wikipedia, ...) and deduplicates the union. If one engine rate-limits you, the others still answer.

No API key. No account. Runs over stdio via uvx, matching the other MCP servers in this stack.

Install / run

uvx ddgs-mcp                 # from PyPI (once published)
uvx --from git+https://github.com/marcinkuk/ddgs-mcp.git ddgs-mcp   # direct from git

For local development:

cd ddgs-mcp
uv sync
uv run ddgs-mcp

Related MCP server: Alka Search MCP

Tools

Tool

Purpose

web_search

General web results (title, url, snippet).

news_search

News results with source + date.

image_search

Image results with direct image/thumbnail URLs.

video_search

Video results with embed URL, duration, publisher.

web_extract

Read full readable content (markdown) of 1-5 URLs.

search_status

Diagnostics: version, configured backend/region, per-category backends, live ping.

Each search tool accepts backend="auto" (randomized multi-engine, the default and most resilient) or a specific backend name, plus region, timelimit (d/w/m/y) and max_results.

All tools return a uniform envelope {"ok": bool, "engine": str, "count": int, "results": [...]}; on failure ok=false with a hint telling the agent how to retry (e.g. switch to auto or a different region).

Configuration (environment)

Variable

Default

Meaning

DDGS_BACKEND

auto

Default backend for search calls.

DDGS_REGION

us-en

Default region code (pl-pl, de-de, wt-wt ...).

DDGS_TIMEOUT

10

Per-request timeout (seconds).

DDGS_PROXY

(unset)

Proxy URL passed to DDGS (e.g. http://127.0.0.1:1080). Useful behind a rotating proxy to avoid bans.

DDGS_MCP_LOG_LEVEL

INFO

Server log verbosity.

Agent Canvas registration

Register with a stdio MCP entry (no secrets required):

{
  "ddgs": {
    "transport": "stdio",
    "command": "uvx",
    "args": ["--from", "git+https://github.com/marcinkuk/ddgs-mcp.git", "ddgs-mcp"],
    "enabled": true,
    "description": "Keyless DDGS metasearch (DuckDuckGo/Bing/Brave/Google) + page extraction. Resilient SearXNG alternative."
  }
}

If you want ban-resistance, add an env entry for a rotating proxy:

"env": {"DDGS_PROXY": "http://127.0.0.1:1080"}

The value is stored through the normal MCP config path (Fernet-encrypted at rest like the other secrets) — never commit it to this repo.

Why this over SearXNG?

  • Resilience: multi-backend aggregation survives single-engine bans (your exact banuję mnie symptom).

  • No key / no server: nothing to host; uvx self-heals on container/image upgrades like trailsearch-mcp.

  • Extraction: web_extract gives clean markdown of a page in one call.

Keep searxng registered alongside it if you like; the two can coexist and you can pick per query.

License

MIT.

Available Tools

6 tools
search_statusA

Health/diagnostics: DDGS version, configured backend/region/timeout/proxy, available backends per category, and a live ping search.

Inputs: no named parameters. Returns: object

web_extractA

Extract readable content from 1-5 web pages (markdown by default).

Use after web_search/news_search to read the actual page content.

Args: urls: 1-5 absolute http(s) URLs to extract. max_chars: max characters of content returned per page (default 6000). fmt: "text_markdown" | "text_plain" | "text_rich" | "text" (raw HTML) | "content" (bytes->str).

Inputs: urls (required), fmt, max_chars. Returns: object

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

Loading tool schema changelog…

    TDQS

    A4.2/5.0

    Scored across 6 tools

    Disambiguation5/5

    Each tool targets a distinct content type or function: web, image, news, video, page extraction, and service diagnostics. There is no meaningful overlap in purpose, so an agent should rarely misselect among them.

    Naming Consistency4/5

    Names are uniformly lowercase snake_case and mostly follow a `<type>_search` pattern for the four search tools. `web_extract` and `search_status` are minor structural deviations, but they remain clear and predictable in style.

    Tool Count5/5

    Six tools is a well-scoped size for a search-focused server: four content-type searches, one extraction tool, and one diagnostics tool. Every tool has a clear role and none feel redundant or unnecessary.

    Completeness5/5

    The server covers the core search lifecycle: querying web, image, news, and video results, then extracting readable content from results, plus health diagnostics. There are no obvious missing operations for its stated purpose.

    Related MCP Connectors

    • Free web search for AI agents. No API key required. Hosted MCP in active development.

      https://api.ssearch.cc/mcp
    • Web search API and MCP server for developers building AI agents.

      https://searchpipe.tech/mcp/
    • Scrape, crawl and search the web for AI agents via MCP.

      https://mcp.messora.dev/mcp
    • Your agent needs the open web — searched by more than one engine, and read as clean markdown rather than raw HTML. **What you can ask for** • "Search this question with two providers and tell me where they disagree." • "Scrape these 40 URLs into markdown, in one batch." • "Crawl this documentation site and give me every page." • "Do deep research on this topic and cite the sources." • "Find the academic papers behind this claim." **How to use it** Point any MCP client at https://mcp.aisa.one/search/mcp and sign in with OAuth — there is no key to create or paste. 30 tools across several independent providers: Tavily and Exa search, answers, contents and agent runs; Firecrawl scrape, batch scrape, crawl, map and search; Perplexity Sonar, Sonar Pro, reasoning and deep research; Oxylabs AI search and LLM jobs; OpenAI and Anthropic web search; and scholarly search. **Why this rather than the source** Several independent indexes behind one account, because one engine's blind spot is not visible from inside it. **It is also a door to the rest** The same login reaches 26 sources and 580+ operations. Find the page here, then ask the same agent who links to it or how much traffic it gets — without adding a second server. **What it costs** Finding and inspecting an operation is free. Running one is billed per call at API prices, with no seat and no monthly minimum, and every call takes max_price_usd so an agent cannot overspend by accident. **Where else it reaches** https://mcp.aisa.one/seo-serp/mcp for the Google results page itself, https://mcp.aisa.one/seo-serp-other-engines/mcp for Bing, Baidu and Naver.

    Related MCP Servers

    • A
      license
      A
      quality
      C
      maintenance
      Free web search, web-page reading as Markdown, and llms.txt documentation retrieval for MCP clients. Runs locally with Node.js over stdio using @alkasima/alka-search-mcp. Searches DuckDuckGo, Mojeek, and Brave; default providers require no API key. Website and provider availability may vary.
      3
      51 npm
      MIT
    • A
      license
      A
      quality
      C
      maintenance
      Enables any MCP client to run keyless multi-engine web searches with RRF fusion, fetch pages and documents as Markdown, and full-text search a local SQLite index. It keeps queries and cached content on the user's machine, degrading gracefully across engine tiers when providers are blocked or rate-limited.
      8
      MIT
    • A
      license
      Not graded
      quality
      C
      maintenance
      Exposes metasearch across many engines and a page-to-Markdown fetcher as two MCP tools, web_search and web_fetch, so any MCP client can run searches and pull clean article content on demand. It also supports news-focused queries with category and time-range filters, plus optional inline page content.
      AGPL 3.0