yuanbao-search-mcp
Related Servers
Alternatives to yuanbao-search-mcp
No user-submitted related servers found.
Related Servers
- AlicenseBqualityCmaintenanceEnables MCP clients to run web searches via DeepSeek's open platform API, with optional web page fetching that returns Markdown content, and supports query syntax for source, language, and time filters.174 npm1MIT
- AlicenseNot gradedqualityBmaintenanceEnables MCP clients to search the web and fetch public web pages via DeepSeek's Search and Fetch APIs, returning ranked results and Markdown page content for agent use.37 npm1MIT
- AlicenseNot gradedqualityCmaintenanceEnables AI clients to run web searches through Tencent Cloud's Yuanbao Search using either a service API key or TC3 signing. Supports domain, industry, freshness, result count, deeplink, and optional full-text content filters to tailor results.441 npm1Apache 2.0
- AlicenseBqualityDmaintenanceAggregated search API service that provides real-time web search capabilities for AI assistants via MCP.232 npm43GPL 3.0
- AlicenseNot gradedqualityCmaintenanceEnables MCP clients to run web searches and receive ranked results with titles, URLs, snippets, and optional dates, with caching and quota-aware error handling.MIT
- AlicenseAqualityBmaintenanceEnables MCP-capable AI clients to run web searches through DeepSeek's search engine and fetch individual webpages as Markdown. Search results include relevance scores, authority, and publication times, and support advanced query syntax such as site:, lang:, and date filters.251 npmApache 2.0
TDQS
Scored across 1 tool
With only one tool in the set, there is no possibility of tool selection confusion; its purpose (web search via Tencent Yuanbao WSA) is unmistakable. The description also clearly delineates what it does and does not do (snippets, not full page text).
The single name yuanbao_search follows a clean snake_case verb_noun-ish convention that matches the server name. There is no second tool to compare against, so full pattern consistency cannot be demonstrated, but nothing is inconsistent.
A single search tool is a defensible minimal surface for a focused search server, but it is thin: all query variations (site restriction, time range, vertical) must be expressed through one tool's parameters with no companion operations. The explicit note that full-text retrieval must happen elsewhere makes the one-tool surface feel incomplete rather than elegantly scoped.
Search coverage with filters and rich result metadata is reasonable, but the tool deliberately stops at snippets and tells the caller to fetch page content from the result URLs — a capability this server does not provide, creating a dead end for content-retrieval workflows. There is also no pagination or follow-up/refinement operation.