DuckDuckGo MCP Server

Created By
rsimda year ago
DuckDuckGo MCP Server for Claude Desktop and Cursor
Overview

What is DuckDuckGo MCP Server?

DuckDuckGo MCP Server is a Model Context Protocol (MCP) server that provides search functionality using DuckDuckGo for applications like Claude Desktop and Cursor IDE.

How to use DuckDuckGo MCP Server?

To use the DuckDuckGo MCP Server, install the required dependencies and run the server using either the uv package manager or pip. You can then execute searches using the provided command.

Key features of DuckDuckGo MCP Server?

  • Web page search functionality via DuckDuckGo
  • Retrieval of search results with summaries and detailed information
  • Asynchronous processing for fast search results
  • Fallback functionality for enhanced stability

Use cases of DuckDuckGo MCP Server?

  1. Integrating DuckDuckGo search capabilities into desktop applications.
  2. Enhancing coding environments with AI-assisted search features.
  3. Providing a reliable search service for various MCP-compatible applications.

FAQ from DuckDuckGo MCP Server?

  • Is the DuckDuckGo MCP Server free to use?

Yes! The DuckDuckGo API is free to use.

  • What are the prerequisites for running the server?

You need Python 3.11 or later and the uv package manager or pip for installation.

  • Can I run the server in a Docker environment?

Yes! The server can be run in a Docker environment supporting both Python 3.13 and the required package managers.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
rsimd
Star
0
Language
Python
License
-

Recommend Servers

View All
AI Work Market — USDC settlement rails for AI labor on Base Mainnet)
@Dario (DME)

AI Work Market is a USDC escrow protocol on Base Mainnet, designed for autonomous AI agents to find work, post jobs, and settle payments without humans in the loop. This MCP server exposes 10 tools: **Escrow lifecycle** - `create_intent_quote` — get calldata + gas estimate for funding a new escrow intent - `submit_proof_quote` — get calldata for the seller to submit a proof URI - `release_funds_quote` — get calldata for the buyer to release payment (or claim/refund) **x402 single-call binding** - `x402_consume` — replaces the 5-step x402 flow with one HMAC-signed POST that returns a delivery URL **Onboarding & discovery** - `agent_onboard` — generate a signed agent card with marketplace attestation - `agent_search` — tf-idf search over the live agent catalog - `agent_reputation` — server-side reputation from on-chain Released/Refunded/Disputed events **Live state** - `system_status` — live on-chain state (nextIntentId, accumulatedFees, contract balance, owner) - `escrow_rules` — contract semantics, lifecycle, call guides, failure modes - `events_subscribe` — SSE stream of new on-chain intent events All endpoints are serverless (Vercel) and return their schema on GET. No browser, no wallet UI required for an agent to integrate. The protocol takes a 1% commission on every settlement; the rest goes to the seller. The full AgentCard is at `/.well-known/agent-card.json` (A2A-compatible). The OpenAPI 3.0.3 spec is at `/.well-known/openapi.json` with `components.securitySchemes` (none, hmacX402). `robots.txt` allows GPTBot, ClaudeBot, anthropic-ai, PerplexityBot, Google-Extended, Applebot-Extended, CCBot, Amazonbot.

8 hours ago
Tavily Mcp
@tavily-ai

JavaScript
a year ago