Skip to main content
Glama
kouui

DuckDuckGo Web Search MCP Server

by kouui
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault

No arguments

Instructions

Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.

This server publishes no instructions, or was last inspected before Glama recorded them.

Capabilities

Server capabilities have not been inspected yet.

Tools

Functions exposed to the LLM to take actions

NameDescription
search_and_fetchA
Search the web using DuckDuckGo and return results.

Args:
    query: The search query string
    limit: Maximum number of results to return (default: 3, maximum 10)

Returns:
    List of dictionaries containing 
    - title
    - url
    - snippet 
    - summary markdown (empty if not available)
fetchC
scrape the html content and return the markdown format using jina api.

Args:
    url: The search query string

Returns:
    text : html in markdown format

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

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.3/5.0

Scored across 2 tools

Disambiguation4/5

The two tools have distinct primary purposes: 'search_and_fetch' performs web searches and returns results, while 'fetch' scrapes HTML content from a given URL. However, there is some potential for confusion because 'fetch' accepts a 'url' argument but its description mentions 'search query string' (likely a documentation error), which could blur the boundary between searching and fetching.

Naming Consistency4/5

The tool names follow a consistent verb-based pattern ('fetch' and 'search_and_fetch'), with clear action-oriented naming. The minor deviation is that 'search_and_fetch' uses an 'and' conjunction, but overall the naming is readable and predictable.

Tool Count3/5

With only 2 tools, the server feels thin for a web search and scraping domain. While it covers basic search and fetch operations, more tools (e.g., for advanced search filtering, caching, or handling different content types) would provide better scope. It's borderline but not severely lacking.

Completeness3/5

The server covers core web search and content fetching workflows, but there are notable gaps. For example, it lacks tools for managing search history, refining queries, handling pagination, or supporting different output formats beyond markdown. Agents can work around these, but the surface is not fully comprehensive.

Maintenance

ActivityInactive
ResponsivenessNo issues

Resources