deepseek-search-mcp
Related Servers
Alternatives to deepseek-search-mcp
No user-submitted related servers found.
Related Servers
- AlicenseAqualityCmaintenanceEnables any MCP client to run keyless multi-engine web searches with RRF fusion, fetch pages and documents as Markdown, and full-text search a local SQLite index. It keeps queries and cached content on the user's machine, degrading gracefully across engine tiers when providers are blocked or rate-limited.8MIT
- AlicenseAqualityCmaintenanceGives MCP-capable agents live web access: search the web, scrape pages into Markdown (including JavaScript-heavy and bot-protected sites), and extract named fields as JSON, with job polling, token-aware content offloading, and built-in research guidance. Ships as a self-hostable stdio or HTTP service with spend caps and per-request key support.7MIT
- AlicenseBqualityBmaintenanceEnables AI coding assistants to perform real-time web searches for technical documentation and deep-fetch web pages, returning clean structured results. It supports integration with MCP clients such as Cursor, Claude, and CodeBuddy.3437 npm1MIT
- AlicenseAqualityBmaintenanceA local-first MCP server that lets AI agents read any webpage as clean Markdown, crawl whole sites within configured limits, search without API keys, and solve supported captchas locally — all without cloud services or third-party keys.3020AGPL 3.0
- AlicenseNot gradedqualityFmaintenanceMCP server enabling local-first web search, fetch, extract, and caching with citeable excerpts, no API key required. Supports research workflows for agents and apps.72 npm1MIT
- AlicenseAqualityCmaintenanceEnables any MCP-compatible AI agent to search the live web and fetch pages as clean Markdown, including batch fetching with rate limiting, retries, and context-safe truncation.3MIT
TDQS
Scored across 3 tools
The three tools cover clearly distinct purposes: cost/quota inspection (deepseek_usage), web search (deepseek_search), and single-page retrieval (deepseek_fetch). An agent can unambiguously select the right tool for each task.
All tools share the deepseek_ prefix, giving a predictable namespace. The suffixes mix verbs (search, fetch) with a noun (usage), a minor deviation, but overall it reads consistently.
Three tools is well-scoped for a search/retrieval server, and each earns its place: one to search, one to fetch, one to monitor billing. No redundant or filler tools.
The surface fully covers the search lifecycle: discovery via search, content retrieval via fetch with pagination hints, and cost control via usage. No obvious gaps for the stated purpose.