Skip to main content
Glama
Sign In
DuckDuckGo Search MCP Server

DuckDuckGo Search MCP Server

by Muhammad-Sarfaraz
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

MCP DuckDuckGo Search

A Model Context Protocol (MCP) server querying DuckDuckGo Instant Answer API.

Installation

Installing via Smithery

To install DuckDuckGo Search for Claude Desktop automatically via Smithery:

npx -y @smithery/cli install @shaheen2013/duckduckgo-search-mcp-server --client claude

Manual Installation

# Clone the repository
git clone https://github.com/shaheen2013/duckduckgo-search-mcp-server.git
cd duckduckgo-search-mcp-server

# Install dependencies
npm install

# Build the project
npm run build

Docker

You can test this MCP server using Docker. To do this first run:

docker build -t duckduckgo-search-mcp-server .
docker run -p 8080:8080 duckduckgo-search-mcp-server

You can then test the server running within Docker via the inspector e.g.

pnpm run inspector http://localhost:8080

Related MCP server: DuckDuckGo Search MCP Server

Usage

Running the Server

You can use the MCP Inspector to test the server:

npm run inspector

Access the MCP Inspector and then test the tool e.g.

alt text

Development

Project Structure

  • src/index.ts - Main server implementation

Available Scripts

  • npm run build - Build the TypeScript code

  • npm run watch - Watch for changes and rebuild

  • npm run inspector - Run the MCP Inspector against the server

Contributing

Contributions are welcome! Please feel free to submit a Pull Request.

Acknowledgments

Available Tools

1 tool
duckduckgo_searchC

Search DuckDuckGo Instant Answer API for a query string

NameRequiredDescriptionDefault
queryYes

TDQS

C2.8/5.0
Behavior2/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

No annotations provided, and the description does not disclose behavioral traits beyond the obvious. For example, it doesn't mention if the search is read-only, rate limits, or result format, which is necessary for an API call.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is a single efficient sentence with no filler. However, it is overly brief and could include more detail without harming conciseness.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a simple one-parameter tool with no output schema and siblings, the description is minimally adequate. However, it lacks information about response structure or any caveats, which would complete the context.

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?

The single parameter 'query' has no description in the schema (0% coverage), and the description does not add any meaning, format instructions, or examples beyond the schema.

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?

Clearly states it searches the DuckDuckGo Instant Answer API for a query string, specifying the verb and resource. However, 'Instant Answer API' is a specific term that might not be universally understood, slightly reducing clarity.

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?

No guidance on when to use this tool, prerequisites, or alternatives. It simply states the function without context for decision-making.

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. 1 tool updatev0.1.0
    • First observedduckduckgo_search
Deploy Server
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

TDQS

B3.2/5.0

Scored across 1 tool

Disambiguation5/5

Only one tool exists, so there is no possibility of confusion between tools.

Naming Consistency5/5

The single tool name follows a clear verb_noun pattern (search_duckduckgo), which is consistent and descriptive.

Tool Count3/5

A single tool for a search server feels minimal but still functional for its stated purpose; it is at the lower end of acceptable scope.

Completeness2/5

The server only offers a single search operation (Instant Answer API), lacking common search features like web search, image search, or filtering, which are typical gaps.

Resources

Related MCP Connectors

Related MCP Servers

  • search-mcp

    deeprave
    F
    license
    Not graded
    quality
    D
    maintenance
    Enables web search capabilities using DuckDuckGo's free API without requiring authentication or API keys.
    -

  • MCP DuckDuckGo Search

    shaheen2013
    F
    license
    B
    quality
    D
    maintenance
    Enables querying the DuckDuckGo Instant Answer API through the Model Context Protocol, allowing users to perform searches and retrieve instant answers.
    1
    9
    -

  • web-search

    sh-arman
    A
    license
    Not graded
    quality
    D
    maintenance
    Enables web searching using Google search results with no API keys required.
    21 npm
    1
    MIT

Appeared in Searches