MCP Node DuckDuckGo Server

Created By
yapweijun1996a year ago
The MCP Node DuckDuckGo Server is a modular Node.js application that allows developers to integrate and test DuckDuckGo search and web content fetching capabilities through a simple HTTP API. It uses Express to establish endpoints, axios to make outbound HTTP requests, and Cheerio for parsing HTML.
Overview

what is MCP Node DuckDuckGo Server?

The MCP Node DuckDuckGo Server is a modular Node.js application that allows developers to integrate and test DuckDuckGo search and web content fetching capabilities through a simple HTTP API.

how to use MCP Node DuckDuckGo Server?

To use the server, clone the repository, install the dependencies, and run the server. You can then access various endpoints to perform searches or fetch content.

key features of MCP Node DuckDuckGo Server?

  • DuckDuckGo Search: Execute search queries and return formatted results.
  • Web Content Fetching: Retrieve and parse text content from any webpage URL.
  • Rate Limiting: Manage request frequency to prevent overload.
  • Extensible MCP Server: Easily add or modify functionality through modules.

use cases of MCP Node DuckDuckGo Server?

  1. Integrating DuckDuckGo search functionality into applications.
  2. Fetching and parsing content from web pages for data analysis.
  3. Building tools that require web scraping capabilities.

FAQ from MCP Node DuckDuckGo Server?

  • What technologies does the server use?

The server uses Node.js, Express, Axios, and Cheerio.

  • How do I start the server?

Run node mcp-node-duckduckgo-server.js after installing the dependencies.

  • Can I contribute to the project?

Yes! Contributions are welcome, and you can fork the repository to add features.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
yapweijun1996
Star
0
Language
JavaScript
License
-

Recommend Servers

View All
Tavily Mcp
@tavily-ai

JavaScript
a year ago
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.

an hour ago