A
licenseA
qualityA
maintenanceA privacy-friendly MCP server that enables web searches and URL content extraction using DuckDuckGo, allowing AI assistants to access real-time web information without API keys.
1
561
42
Apache 2.0
Duck Duck MCP
by qwang07
Provides web search functionality through the DuckDuckGo search engine, offering customizable search results with parameters for region settings, safe search levels, and number of results.
Click on "Deploy 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., "@Duck Duck MCPsearch for recent advancements in quantum computing"
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.
Duck Duck MCP
一个基于 DuckDuckGo 搜索引擎的 Model Context Protocol (MCP) 服务器实现。
功能特性
使用 DuckDuckGo 进行网络搜索
支持自定义搜索结果数量（默认 50 条）
支持区域设置（默认 zh-cn）
支持安全搜索级别设置（OFF/MODERATE/STRICT）
提供结构化的搜索结果，包含元数据
智能内容分类（文档/文章/社交媒体）
自动语言检测
主题标签识别
Related MCP server: duckduckgo-mcp
安装
安装通过 Smithery
通过 Smithery 将 DuckDuckGo 搜索自动安装到 Claude 桌面端：
npx -y @smithery/cli install duck-duck-mcp --client claude不需要安装，可以直接通过 npx 运行：
npx -y @smithery/cli install duck-duck-mcp --client claude使用方法
这是一个 MCP 服务器实现，主要用于与支持 MCP 协议的 AI 客户端（如 Claude）集成。
启动服务器：
# 使用 npx（推荐）
npx duck-duck-mcp
# 或者如果已经全局安装
mcp-server-search搜索参数示例：
{
"query": "搜索关键词",
"options": {
"region": "zh-cn",
"safeSearch": "MODERATE",
"numResults": 50
}
}返回结果格式：
{
"type": "search_results",
"data": [
{
"title": "标题",
"url": "网址",
"description": "描述",
"metadata": {
"type": "article|documentation|social|other",
"source": "域名"
}
}
],
"metadata": {
"query": "搜索关键词",
"timestamp": "时间戳",
"resultCount": 50,
"searchContext": {
"region": "zh-cn",
"safeSearch": "MODERATE"
},
"queryAnalysis": {
"language": "zh-cn|en",
"topics": ["technology", "documentation"]
}
}
}License
MIT
Available Tools
1 toolsearchC
Search the web using DuckDuckGo
ParametersJSON Schema
| Name | Required | Description | Default |
|---|---|---|---|
| query | Yes | ||
| options | No |
TDQS
C2.8/5.0
Behavior2/5
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations provided, the description carries the full burden of behavioral disclosure. It mentions the search engine (DuckDuckGo) but doesn't describe rate limits, authentication needs, result format, pagination, or potential side effects. For a web search tool with zero annotation coverage, this leaves significant behavioral gaps.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Conciseness5/5
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is extremely concise at just 5 words, front-loading the essential information with zero wasted words. Every word earns its place in conveying the core functionality.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Completeness2/5
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
Given the tool has no annotations, no output schema, and 0% schema description coverage for its 2 parameters (including a nested object), the description is inadequate. It doesn't explain what the search returns, how results are structured, or provide any parameter guidance, leaving the agent with insufficient information for effective use.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Parameters2/5
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema description coverage is 0%, meaning none of the parameters have descriptions in the schema. The tool description mentions no parameters at all, failing to compensate for this gap. While 'query' is obvious for search, the 'options' object with region, safeSearch, and numResults remains completely undocumented in both schema and description.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Purpose4/5
Does the description clearly state what the tool does and how it differs from similar tools?
The description clearly states the action ('Search') and the resource ('the web using DuckDuckGo'), providing a specific verb+resource combination. However, with no sibling tools mentioned, there's no opportunity to differentiate from alternatives, preventing a perfect score.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Usage Guidelines2/5
Does the description explain when to use this tool, when not to, or what alternatives exist?
The description provides no guidance on when to use this tool versus alternatives, nor does it mention any prerequisites or contextual constraints. It simply states what the tool does without offering usage context.
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.
1 tool update
- First observed
search
TDQS
B3/5.0
Scored across 1 tool
Disambiguation5/5
With only one tool, there is no possibility of confusion or overlap between tools, making disambiguation perfect.
Naming Consistency5/5
A single tool named 'search' follows a clear and consistent verb-based naming pattern, with no inconsistencies to evaluate.
Tool Count2/5
One tool is too few for a web search server, as it lacks complementary functions like filtering results, getting details, or handling different search types, making the scope feel incomplete.
Completeness2/5
The tool surface is severely incomplete for a web search domain; it only provides basic search without options for advanced queries, result pagination, or accessing specific content types, leading to significant gaps in functionality.
Maintenance
ActivityInactive
ResponsivenessNo issues
Related MCP Connectors
Live AI-native web search with citations. One tool for every MCP client. Flat per-request pricing.
Fast, intelligent web search and web crawling. New mcp tool: Exa-code is a context tool for coding
The Dappier MCP server connects LLMs and AI agents to real-time, rights-cleared, proprietary data from trusted sources across various domains. It provides specialized knowledge through real-time web search, financial stock market and crypto data access, AI-powered content recommendations from premium publishers, and structured outputs with sub-300ms response times, enabling AI systems to respond to current events and trends.
Related MCP Servers
- AlicenseNot gradedqualityCmaintenanceA MCP server for DuckDuckGo HTML search. Unlike other DuckDuckGo MCP servers, this one isn't just AI slop.ISC
- FlicenseNot gradedqualityDmaintenanceThis MCP server provides tools for AI agents to search the web, fetch page content, and query specific elements from pages using DuckDuckGo.7-
- 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