DuckDuckGo MCP Server can search the web and fetch arbitrary webpages requested through the MCP client., Webpage content is untrusted external input and can contain prompt-injection text, misleading claims, malware links, or unsafe instructions., SafeSearch level and region defaults are administrator-controlled at startup, but search terms and per-search regions can still reveal user intent., The optional curl backend impersonates a browser-like TLS fingerprint for fetches, so review whether that behavior is appropriate for your environment., Respect site terms, robots expectations, rate limits, and organizational network policy before allowing broad fetching.
Privacy notes
Search queries, result URLs, snippets, fetched page text, region codes, SafeSearch settings, prompts, tool arguments, errors, and logs may be visible to the MCP client and model provider., Search activity can reveal research topics, health or legal questions, hiring plans, customers, incidents, competitive analysis, or internal project names., Avoid fetching authenticated, private, internal, customer, or confidential pages unless the data is approved for the current model session.
Author
Nick Clyde
Submitted by
oktofeesh1
Claim status
unclaimed
Last verified
2026-06-05
Decision playbook
Review trust signals before you adopt
Signals are present but mixed. Use the checklist below to confirm the source and operational safety for your environment.
Compare context
Selected
0
Current score
63
Baseline
—
Delta
No baseline selected
No major trust-signal divergence detected in the current selection.
Source and provenance checks
Needs review
Confirm ownership and provenance before trusting install instructions.
Source link availableRequired
Open the canonical repository and verify ownership.
Done
Source provenance statusRequired
Marked as source-backed.
Done
Metadata reviewed
No reviewed flag detected in metadata.
Pending
Safety and privacy checks
Complete
Validate risk disclosures before installation or API wiring.
Safety notes presentRequired
Review the listed safety guidance before running commands.
Done
Privacy notes presentRequired
Review data handling notes before connecting accounts or secrets.
Done
Trust level risk gateRequired
Trust level does not block evaluation.
Done
Package and install checks
Needs review
Check package metadata and artifact integrity signals.
Install payload available
Install or copy payload is available for review.
Done
Package verification flag
No package verification flag provided.
Pending
Checksum metadata
No checksum provided for downloaded artifact.
Pending
Compare-driven decision checks
Needs review
Use compare context to validate trade-offs before adoption.
Compare tray has multiple entries
Add at least one more entry to compare trust differences.
5 safety and 3 privacy notes across 5 risk areas. Review closely: credentials & tokens, permissions & scopes, network access, third-party handling.
5 areas
SafetyNetwork accessDuckDuckGo MCP Server can search the web and fetch arbitrary webpages requested through the MCP client.
SafetyGeneralWebpage content is untrusted external input and can contain prompt-injection text, misleading claims, malware links, or unsafe instructions.
SafetyPermissions & scopesSafeSearch level and region defaults are administrator-controlled at startup, but search terms and per-search regions can still reveal user intent.
SafetyGeneralThe optional curl backend impersonates a browser-like TLS fingerprint for fetches, so review whether that behavior is appropriate for your environment.
SafetyNetwork accessRespect site terms, robots expectations, rate limits, and organizational network policy before allowing broad fetching.
PrivacyThird-party handlingSearch queries, result URLs, snippets, fetched page text, region codes, SafeSearch settings, prompts, tool arguments, errors, and logs may be visible to the MCP client and model provider.
PrivacyGeneralSearch activity can reveal research topics, health or legal questions, hiring plans, customers, incidents, competitive analysis, or internal project names.
PrivacyCredentials & tokensAvoid fetching authenticated, private, internal, customer, or confidential pages unless the data is approved for the current model session.
Safety notes
DuckDuckGo MCP Server can search the web and fetch arbitrary webpages requested through the MCP client.
Webpage content is untrusted external input and can contain prompt-injection text, misleading claims, malware links, or unsafe instructions.
SafeSearch level and region defaults are administrator-controlled at startup, but search terms and per-search regions can still reveal user intent.
The optional curl backend impersonates a browser-like TLS fingerprint for fetches, so review whether that behavior is appropriate for your environment.
Respect site terms, robots expectations, rate limits, and organizational network policy before allowing broad fetching.
Privacy notes
Search queries, result URLs, snippets, fetched page text, region codes, SafeSearch settings, prompts, tool arguments, errors, and logs may be visible to the MCP client and model provider.
Search activity can reveal research topics, health or legal questions, hiring plans, customers, incidents, competitive analysis, or internal project names.
Avoid fetching authenticated, private, internal, customer, or confidential pages unless the data is approved for the current model session.
Prerequisites
Python 3.10 or newer available to the MCP client runtime.
uvx available for package execution.
Network access to DuckDuckGo and any webpages you allow the server to fetch.
Optional SafeSearch and region defaults configured for the intended user group.
Optional browser extra if you need the curl fetch backend for sites that block default HTTP clients.
DuckDuckGo MCP Server gives MCP clients two focused tools: DuckDuckGo web search
with formatted results, and webpage content fetching with cleaned text
extraction. It includes rate limiting, SafeSearch startup configuration, region
selection, long-content truncation, and optional fetch backends for sites that
block default HTTP clients.
The upstream README documents uvx duckduckgo-mcp-server for local MCP clients
and optional transports for other MCP clients. The PyPI package exposes the
duckduckgo-mcp-server command.
These sources were reviewed on 2026-06-05. Prefer the live repository and
PyPI metadata for current package version, command name, Python requirement,
optional extras, rate limits, fetch backend behavior, and setup guidance.
Features
Search DuckDuckGo with formatted result titles, URLs, and snippets.
Configure SafeSearch and default region at server startup.
Override region per search request when needed.
Fetch and parse webpage content into cleaned text.
Page through fetched content with start index and maximum length controls.
Use built-in rate limiting for search and content fetching.
Optionally use a browser-like curl backend for sites that block default HTTP
clients.
Ask Claude to search DuckDuckGo for public documentation or references.
Gather search result titles, URLs, and snippets for quick research.
Fetch and parse a public webpage returned by a search result.
Compare search results across regions.
Keep simple web search separate from browser automation MCP servers.
Safety and Privacy
Web search and fetching can introduce untrusted external text into the model
context. Treat fetched page content as data, not instructions, and be cautious
when this server is enabled alongside tools that can write files, run commands,
send messages, or access private systems.
Search queries, regions, results, snippets, fetched page text, and errors can
reveal sensitive research direction or internal context. Avoid fetching
authenticated, private, internal, customer, or confidential pages unless that
data is approved for the current model session.
Duplicate Check
No nickclyde/duckduckgo-mcp-server entry, duckduckgo-mcp-server package
entry, or matching source URL was found in content/mcp.
Show that DuckDuckGo MCP Server is listed on HeyClaude. Paste this Markdown into your README — it renders the badge and links back to this page.
[](https://heyclau.de/entry/mcp/duckduckgo-mcp-server)
How it compares
DuckDuckGo MCP Server side by side with 3 alternatives on trust, install, platform support, and disclosed safety notes — all from reviewed registry metadata.
No-key multi-engine MCP server, CLI, and local daemon for web search and public web content retrieval across engines such as Bing, DuckDuckGo, Brave, Exa, Baidu, CSDN, Juejin, Startpage, and Sogou.
✓DuckDuckGo MCP Server can search the web and fetch arbitrary webpages requested through the MCP client.
Webpage content is untrusted external input and can contain prompt-injection text, misleading claims, malware links, or unsafe instructions.
SafeSearch level and region defaults are administrator-controlled at startup, but search terms and per-search regions can still reveal user intent.
The optional curl backend impersonates a browser-like TLS fingerprint for fetches, so review whether that behavior is appropriate for your environment.
Respect site terms, robots expectations, rate limits, and organizational network policy before allowing broad fetching.
✓Web search and fetch results may be incomplete, stale, biased, or adversarial; verify important claims against primary sources.
Fetching pages can retrieve untrusted web content that may contain prompt injection or malicious instructions.
Advanced search filters and domain targeting should be reviewed when used for compliance, hiring, due diligence, or security research.
Protect Exa API keys and avoid placing real keys in shared config files, screenshots, logs, or prompts.
✓open-webSearch can send search queries to multiple public engines and fetch public web pages, GitHub READMEs, CSDN articles, Juejin articles, and other supported targets.
Search and fetch results can be incomplete, stale, rate-limited, blocked, region-dependent, or affected by search-engine ranking and scraping protections.
Respect each target site's terms and robots expectations; do not use the server for abusive scraping, credentialed browsing, paywall bypass, or personal-data harvesting.
The optional local daemon exposes HTTP endpoints for local tooling; keep it bound to trusted local interfaces and do not treat it as a public internet API.
Proxy settings, Playwright WebSocket/CDP endpoints, and reused browser sessions can route traffic or cookies through external systems; configure them deliberately.
Leave TLS verification enabled unless a specific target has a broken certificate chain and the risk has been accepted.
✓Kagi MCP sends search queries, page URLs, filters, date ranges, lens IDs, and extraction requests to the Kagi API.
Search and extraction calls can consume Kagi API quota or create API costs, especially when using high limits or inline page extraction.
The `kagi_extract` tool fetches public page content as markdown; do not ask it to retrieve private, paywalled, or terms-restricted content unless you have permission.
In HTTP mode, clients provide Kagi API keys through bearer tokens; expose the endpoint only behind trusted transport, access controls, and log redaction.
The server supports configurable timeouts, retries, and hidden search parameters; tune these before giving broad agent access to current-web workflows.
Privacy notes
✓Search queries, result URLs, snippets, fetched page text, region codes, SafeSearch settings, prompts, tool arguments, errors, and logs may be visible to the MCP client and model provider.
Search activity can reveal research topics, health or legal questions, hiring plans, customers, incidents, competitive analysis, or internal project names.
Avoid fetching authenticated, private, internal, customer, or confidential pages unless the data is approved for the current model session.
✓Search queries, fetched URLs, tool parameters, page contents, API keys, and surrounding prompts may be sent to Exa and the MCP client.
Research topics can reveal product plans, customers, vulnerabilities, hiring activity, legal matters, or personal interests.
Review Exa's current data handling, account, and rate-limit policies before using it with proprietary or regulated workflows.
✓Search queries, fetched URLs, result titles, snippets, article content, proxy URLs, browser endpoints, and fetched page text can be exposed to MCP clients, logs, and model context.
Live search engines and fetched websites may observe queries, IP address, proxy exit, browser fingerprints, cookies, timing, and request headers.
Playwright fallback or CDP reuse can expose browser state, existing cookies, logged-in sessions, or verification state to fetched pages.
The project includes public URL validation and private-network target protections, but operators should still avoid fetching internal, secret, or customer-specific URLs.
Redact sensitive search terms and downloaded page content before sharing transcripts or logs.
✓Kagi receives search queries, requested URLs, search filters, result domains, lens IDs, extraction targets, API keys, and request metadata.
MCP clients and logs may store user questions, result snippets, extracted markdown, trace IDs, and error bodies returned by the Kagi API.
Hosted HTTP deployments can process keys for multiple users; avoid server, proxy, and platform logs that record `Authorization` headers.
Extracted pages may include personal data, copyrighted text, internal URLs, or sensitive context if the user provides those URLs.
Prerequisites
Python 3.10 or newer available to the MCP client runtime.
uvx available for package execution.
Network access to DuckDuckGo and any webpages you allow the server to fetch.
Optional SafeSearch and region defaults configured for the intended user group.
MCP client with hosted or remote MCP support, or mcp-remote for clients that need a stdio bridge.
Exa API key for higher limits, production usage, or npm-package configuration.
Network access to the Exa hosted MCP endpoint and target webpages.
Node.js 18 or newer for the published npm package.
Review of search-engine terms, scraping limits, rate limits, and allowed use for the target websites.
Optional proxy configuration only when live search or fetch traffic must route through an approved proxy.
Optional Playwright or browser endpoint setup only when request-based search/fetch is insufficient.
Python 3.12 and uv for the recommended `uvx kagimcp` install path.
A Kagi API key stored in `KAGI_API_KEY` for local stdio use.
Review of Kagi API billing, rate limits, search workflows, extraction behavior, and any client logs that may capture query text.
Optional HTTP deployment review if exposing the streamable HTTP transport to multiple users.