bingcn
Related Servers
Alternatives to bingcn
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityDmaintenanceAn MCP server optimized for Chinese users that enables AI models to perform Bing searches and fetch webpage content without requiring an API key. It provides specialized tools for searching and scraping web data directly through supported AI environments like Claude or Cursor.41 npm6MIT
- AlicenseAqualityCmaintenanceProvides Bing Chinese search and webpage crawling tools, enabling AI assistants to fetch real-time web information without API keys.2318 npm70MIT
- AlicenseAqualityFmaintenanceA Model Context Protocol server that integrates with Microsoft Bing Search API, allowing AI assistants to perform web, news, and image searches.379MIT
- FlicenseNot gradedqualityDmaintenanceWraps the Kimi Coding Search and Fetch APIs into MCP tools for web searching and content retrieval. It enables LLMs to perform targeted searches and crawl web pages using standardized interfaces.1-
- AlicenseAqualityAmaintenanceMCP server that enables AI agents to search Chinese web platforms (Taobao, JD, Xiaohongshu, Zhihu, ZSXQ) without being blocked.4039MIT
- AlicenseNot gradedqualityDmaintenanceA plug-and-play MCP toolkit providing AI agents with web search (Chinese sources prioritized), file operations, and shell command execution capabilities.2MIT
TDQS
Scored across 2 tools
The two tools have clearly distinct purposes: bing_search performs keyword searches and returns a list of results with metadata, while fetch_webpage retrieves the full content of a specific webpage based on an ID. There is no overlap in functionality, making it easy for an agent to select the correct tool for each task.
Both tools follow a consistent verb_noun naming pattern: bing_search and fetch_webpage. The names are descriptive, use snake_case uniformly, and clearly indicate the action (search/fetch) and target (bing/webpage), providing predictability across the tool set.
With only 2 tools, the set feels thin for a search and content retrieval server, as it lacks operations like filtering, pagination, or advanced search options. While the tools cover basic workflows, the count is borderline low for the apparent scope, potentially limiting agent capabilities.
The tools provide core search and content retrieval functions, but there are notable gaps: no ability to update, delete, or manage search results, and no support for operations like caching or result refinement. The surface is functional but incomplete for robust web search and content handling.