DuckDuckGo Search MCP
The DuckDuckGo Search MCP server provides a privacy-friendly, AI-enhanced web search and content extraction tool with the following capabilities:
Web Search: Perform searches using DuckDuckGo, with options to specify page number and number of results
Felo AI Search: Access Felo AI for technical information and advanced search capabilities, with streaming response options
Fetch URL Content: Extract and filter content from URLs, with controls for maximum length, tag exclusion, and inclusion of links/images/main content
URL Metadata Extraction: Retrieve metadata such as title and description from web pages
The server performs direct web scraping rather than relying on limited APIs and does not require API keys.
Enables web search functionality by scraping DuckDuckGo HTML results, providing more comprehensive search capabilities than limited APIs.
Allows the MCP server to be installed and run through the npm package registry, making it easily accessible for AI assistants.
Links to the OEvortex YouTube channel for updates and tutorials related to the MCP server.
Click on "Install Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@DuckDuckGo Search MCPsearch for latest AI developments in healthcare"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
Quick Start
# Search from the command line
npx -y @oevortex/ddg_search@latest "your search query"
# Or install globally
npm install -g @oevortex/ddg_search
ddg "your search query"Related MCP server: webmcp
Usage
CLI
# Basic web search (DuckDuckGo)
ddg "quantum computing"
# Get more results
ddg "latest news" -n 10
# AI-generated answer (IAsk)
ddg "explain recursion" -m ai
# AI-generated answer (Monica)
ddg "hello world" -m ai -b monica
# IAsk with options
ddg "gravity" -m ai --iask-mode academic --detail-level comprehensiveFlags
Flag | Description | Default |
|
|
|
|
|
|
| Number of results (1-20, web mode) |
|
|
|
|
|
| — |
| Show help | |
| Show version |
MCP Server
Start the MCP server for use with Claude Desktop, OpenCode, or other MCP clients:
ddg --serverClaude Desktop config:
{
"mcpServers": {
"ddg-search": {
"command": "npx",
"args": ["-y", "@oevortex/ddg_search@latest"]
}
}
}Global install config:
{
"mcpServers": {
"ddg-search": {
"command": "ddg"
}
}
}Programmatic API
import { searchDuckDuckGo } from '@oevortex/ddg_search/src/utils/search.js';
import { searchIAsk } from '@oevortex/ddg_search/src/utils/search_iask.js';
import { searchMonica } from '@oevortex/ddg_search/src/utils/search_monica.js';
// DuckDuckGo
const results = await searchDuckDuckGo("query", 5);
// IAsk AI
const answer = await searchIAsk("query", "thinking", null);
// Monica AI
const answer = await searchMonica("query");MCP Tool Schema
Single unified tool web-search:
Parameter | Type | Default | Description |
| string | required | Search query |
|
|
| DuckDuckGo results or AI answer |
|
|
| AI backend (mode=ai only) |
| integer |
| Results count (web mode, 1-20) |
| string |
| IAsk mode (backend=iask only) |
| string | — | IAsk detail level (backend=iask only) |
Agent Prompt
Add this to your agent's system prompt to enable web search:
When you need to search the web or find current information, use the DDG Search CLI:
npx -y @oevortex/ddg_search@latest "<query>" -m ai
This runs an AI-powered web search via IAsk. For standard DuckDuckGo results (titles + URLs + snippets), use mode "web" instead:
npx -y @oevortex/ddg_search@latest "<query>" -m web -n 5
For a different AI backend (Monica), add -b monica. Use this for any research, fact-checking, or current events task.Proxy Support
Respects HTTP_PROXY, HTTPS_PROXY, and NO_PROXY environment variables automatically.
HTTPS_PROXY=http://proxy:8080 ddg "search query"Install
npm install -g @oevortex/ddg_searchOr use npx without installing.
Project Structure
bin/cli.js CLI entry point
src/
index.ts MCP server
tools/
searchTool.js Unified search tool
utils/
search.js DuckDuckGo scraper
search_iask.js IAsk AI client
search_monica.js Monica AI client
user_agents.js User agent rotation
skills/
ddg-search/ Agent skill for marketplaceContributing
Pull requests welcome. Open an issue for bugs or feature requests.
License
Apache 2.0
Available Tools
1 toolweb-searchWeb SearchARead-only
Search the web. Use mode="web" for standard DuckDuckGo results (titles, URLs, snippets). Use mode="ai" for AI-generated answers — pick backend="iask" (default) or backend="monica".
| Name | Required | Description | Default |
|---|---|---|---|
| mode | No | Search mode. "web" returns DuckDuckGo search results. "ai" returns an AI-generated answer. | web |
| query | Yes | The search query or question. | |
| backend | No | AI backend when mode="ai": "iask" or "monica". Ignored in web mode. | iask |
| iaskMode | No | IAsk mode when backend="iask": "question", "academic", "forums", "wiki", or "thinking". Default: "thinking". | thinking |
| numResults | No | Number of web results (1-20). Web mode only. Default: 3. | |
| detailLevel | No | IAsk detail level when backend="iask": "concise", "detailed", or "comprehensive". |
TDQS
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already declare readOnlyHint=true, so the tool is inherently read-only. The description adds behavioral context: what each mode returns (titles/URLs/snippets vs. AI answer), default backends, and that mode can be chosen. No contradictions; description supplements annotations well.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is extremely concise—two short sentences. It is front-loaded with the primary action and uses line breaks for readability. Every phrase adds value; no wasted words.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
Given no output schema, the description adequately covers return types per mode. It mentions key parameters (mode, backend) but omits mentioning 'numResults' for web mode or 'iaskMode'/'detailLevel' for AI mode. However, since the schema provides full descriptions and the tool is simple, completeness is high but not perfect.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema coverage is 100%, so baseline is 3. The description adds minimal parameter semantics beyond the schema, only noting the default value for 'backend'. It does not elaborate on 'numResults', 'iaskMode', or 'detailLevel', but the schema descriptions are already sufficient. Hence score 3.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description clearly states the tool's purpose: 'Search the web.' It distinguishes two modes with specific outputs: 'mode="web" for standard DuckDuckGo results (titles, URLs, snippets)' and 'mode="ai" for AI-generated answers'. This provides a specific verb (search) and resource (web), and differentiates the major modes effectively.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
The description explicitly tells when to use each mode: 'Use mode="web" for standard DuckDuckGo results' and 'Use mode="ai" for AI-generated answers'. It also provides guidance on backend selection for AI mode. With no sibling tools, no explicit when-not is necessary, but the guidance is clear and actionable.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections. Dates show when Glama detected each change.
3 tool updates
v1.4.0- Removed
iask-search - Removed
monica-search - Changed
web-search8 fields changed- added
Input schema / properties / backendAdded value: +{ + "default": "iask", + "description": "AI backend when mode=\"ai\": \"iask\" or \"monica\". Ignored in web mode.", + "enum": [ + "iask", + "monica" + ], + "type": "string" +} - added
Input schema / properties / detailLevelAdded value: +{ + "description": "IAsk detail level when backend=\"iask\": \"concise\", \"detailed\", or \"comprehensive\".", + "enum": [ + "concise", + "detailed", + "comprehensive" + ], + "type": "string" +} - added
Input schema / properties / iaskModeAdded value: +{ + "default": "thinking", + "description": "IAsk mode when backend=\"iask\": \"question\", \"academic\", \"forums\", \"wiki\", or \"thinking\". Default: \"thinking\".", + "enum": [ + "question", + "academic", + "forums", + "wiki", + "thinking" + ], + "type": "string" +} - changed
Input schema / properties / mode / defaultPrevious value: -"short"New value: +"web" - changed
Input schema / properties / mode / descriptionPrevious value: -"Choose 'short' for basic results (no Description) or 'detailed' for full results (includes Description)."New value: +"Search mode. \"web\" returns DuckDuckGo search results. \"ai\" returns an AI-generated answer." - changed
Input schema / properties / mode / enumPrevious value: -[ - "short", - "detailed" -]New value: +[ + "web", + "ai" +] - changed
Input schema / properties / numResults / descriptionPrevious value: -"Specify how many results to display (default: 3, maximum: 20)."New value: +"Number of web results (1-20). Web mode only. Default: 3." - changed
Input schema / properties / query / descriptionPrevious value: -"Enter your search query to find the most relevant web pages."New value: +"The search query or question."
6 tool updates
v1.0.0- Removed
felo-search - Removed
fetch-url - Added
iask-search - Added
monica-search - Removed
url-metadata - Changed
web-search5 fields changed- added
Input schema / properties / modeAdded value: +{ + "default": "short", + "description": "Choose 'short' for basic results (no Description) or 'detailed' for full results (includes Description).", + "enum": [ + "short", + "detailed" + ], + "type": "string" +} - changed
Input schema / properties / numResults / defaultPrevious value: -10New value: +3 - changed
Input schema / properties / numResults / descriptionPrevious value: -"Number of results to return (default: 10)"New value: +"Specify how many results to display (default: 3, maximum: 20)." - removed
Input schema / properties / pageRemoved value: -{ - "default": 1, - "description": "Page number (default: 1)", - "minimum": 1, - "type": "integer" -} - changed
Input schema / properties / query / descriptionPrevious value: -"The search query"New value: +"Enter your search query to find the most relevant web pages."
4 tool updates
- First observed
felo-search - First observed
fetch-url - First observed
url-metadata - First observed
web-search
TDQS
Only one tool exists, so there is no possibility of confusion between tools. The two modes are clearly described within the single tool.
With a single tool named 'web-search', the naming is self-consistent and follows a clear verb-noun pattern.
A search server with only one tool feels too thin for the domain. Typically, separate tools for different search types (web, images, news, etc.) would be expected.
The single tool covers web and AI search but misses common search categories like images, news, and video, leaving notable gaps for typical search use cases.
Maintenance
Resources
Unclaimed servers have limited discoverability.
Looking for Admin?
If you are the server author, to access and configure the admin panel.
Related MCP Connectors
Driflyte MCP server which lets AI assistants query topic-specific knowledge from web and GitHub.
Docs: https://docs.keenable.ai/mcp-server Keenable is a free, remote MCP server that gives agents access to the web index. Search the web with ranked results and date/site filters, then fetch any indexed page as clean markdown. Works out of the box with no account or API key.
An MCP server that gives your AI access to the source code and docs of all public github repos
Related MCP Servers
- FlicenseNot gradedqualityDmaintenanceThis MCP server provides tools for AI agents to search the web, fetch page content, and query specific elements from pages using DuckDuckGo.20-
- AlicenseNot gradedqualityCmaintenanceMCP server for web search and content extraction using DuckDuckGo or SearXNG, with Playwright-based fetching and LLM-powered data extraction.139MIT
- AlicenseNot gradedqualityDmaintenanceMCP server for internet search via direct Google and DuckDuckGo HTML scraping with AI-powered result normalization and optional summarization, requiring no API keys for search.MIT
- FlicenseNot gradedqualityDmaintenanceMCP server that provides web search scraping from DuckDuckGo (with Mojeek fallback) and URL content fetching as markdown/text or raw HTML.1-
Latest Blog Posts
- Who's Calling? MCP Hosts Are an Identity Blind Spot (And the Spec Knows It)By Om-Shree-0709 on .mcpAgent IdentityOAuth 2.1
- Your AI Chatbot Just Exposed Your CEO's Salary to an InternBy Om-Shree-0709 on .Agent IdentityMCP SecurityOAuth Delegation
- Why MCP Servers Need Execution Sandboxing (And Why Your Current Stack Isn't Enough)By Om-Shree-0709 on .Agentic AiPrompt InjectionWebAssembly
MCP directory API
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/OEvortex/ddg_search'
If you have feedback or need assistance with the MCP directory API, please join our Discord server