A
licenseNot graded
qualityD
maintenanceEnables AI assistants to perform intelligent web searches using the Baidu Wenxin API, supporting multiple models, search modes, and providing search results with reference sources.
21 npm
6
MIT
Baidu Search MCP Server
by Evilran
바이두 검색 MCP 서버
Baidu를 통해 웹 검색 기능을 제공하고, 콘텐츠 페칭 및 구문 분석을 위한 추가 기능을 제공하는 MCP(Model Context Protocol) 서버입니다.
특징
웹 검색 : 고급 속도 제한 및 결과 형식을 사용하여 Baidu 검색
콘텐츠 가져오기 : 지능형 텍스트 추출을 통해 웹 페이지 콘텐츠를 검색하고 구문 분석합니다.
속도 제한 : 검색 및 콘텐츠 페칭 모두에 대한 속도 제한에 대한 내장형 보호 기능
오류 처리 : 포괄적인 오류 처리 및 로깅
LLM 친화적 출력 : 대규모 언어 모델 소비를 위해 특별히 포맷된 결과
Related MCP server: DuckDuckGo MCP Server
설치
Smithery를 통해 설치
Smithery 를 통해 Claude Desktop에 Baidu 검색 서버를 자동으로 설치하는 방법:
지엑스피1
uv 를 통해 설치
uv 사용하여 PyPI에서 직접 설치:
uv pip install baidu-mcp-server용법
Claude Desktop으로 실행
Claude Desktop 다운로드
Claude Desktop 구성을 생성하거나 편집하세요.
macOS의 경우:
~/Library/Application Support/Claude/claude_desktop_config.jsonWindows의 경우:
%APPDATA%\Claude\claude_desktop_config.json
다음 구성을 추가합니다.
{
"mcpServers": {
"baidu-search": {
"command": "uvx",
"args": ["baidu-mcp-server"]
}
}
}Claude Desktop을 다시 시작하세요
개발
로컬 개발을 위해 MCP CLI를 사용할 수 있습니다.
# Run with the MCP Inspector
mcp dev server.py
# Install locally for testing with Claude Desktop
mcp install server.py사용 가능한 도구
1. 검색 도구
async def search(query: str, max_results: int = 10) -> strBaidu에서 웹 검색을 수행하여 서식이 지정된 결과를 반환합니다.
매개변수:
query: 검색 쿼리 문자열max_results: 반환할 최대 결과 수(기본값: 10)
반환값: 제목, URL, 스니펫이 포함된 검색 결과가 포함된 형식화된 문자열입니다.
2. 콘텐츠 가져오기 도구
async def fetch_content(url: str) -> str웹페이지에서 콘텐츠를 가져와서 구문 분석합니다.
매개변수:
url: 콘텐츠를 가져올 웹 페이지 URL
반환: 웹페이지의 텍스트 콘텐츠를 정리하고 형식을 지정했습니다.
자세한 기능
속도 제한
검색: 분당 30개 요청으로 제한됨
콘텐츠 가져오기: 분당 20개 요청으로 제한됨
자동 대기 관리 및 대기 시간
결과 처리
광고 및 관련 없는 콘텐츠를 제거합니다.
Baidu 리디렉션 URL을 정리합니다.
최적의 LLM 소비를 위한 결과 형식
긴 내용을 적절하게 잘라냅니다.
오류 처리
포괄적인 오류 포착 및 보고
MCP 컨텍스트를 통한 자세한 로깅
속도 제한 또는 시간 초과에 대한 우아한 저하
기여하다
이슈 및 풀 리퀘스트는 환영합니다! 개선이 필요한 부분은 다음과 같습니다.
추가 검색 매개변수(지역, 언어 등)
향상된 콘텐츠 구문 분석 옵션
자주 액세스되는 콘텐츠에 대한 캐싱 계층
추가 속도 제한 전략
특허
이 프로젝트는 MIT 라이선스에 따라 라이선스가 부여되었습니다.
감사의 말
이 프로젝트의 코드는 다음 저장소를 참조합니다.
오픈 소스 커뮤니티에 기여하고 노력해 주신 이 저장소의 작성자와 기여자 여러분께 감사드립니다.
Available Tools
1 toolsearchC
Search Baidu and return formatted results.
Args:
query: The search query string
max_results: Maximum number of results to return (default: 6)
deep_mode: Deep search the web content (default: False)
ctx: MCP context for logging
ParametersJSON Schema
| Name | Required | Description | Default |
|---|---|---|---|
| query | Yes | ||
| max_results | No | ||
| deep_mode | No |
TDQS
C2.5/5.0
Behavior2/5
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
The description does not disclose behavioral traits such as authentication requirements, rate limits, pagination behavior, or the nature of 'deep_mode.' With no annotations, the description carries full burden but fails to provide sufficient context beyond the basic function.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Conciseness2/5
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is short but poorly structured. It includes unnecessary notation like 'Args:' and references a 'ctx' parameter not in the schema, which is misleading. It mixes parameter docs with the main description, reducing clarity.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Completeness2/5
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
Given the tool has three parameters, no output schema, and no annotations, the description is incomplete. It fails to explain output format, error handling, or advanced usage. A search tool typically requires more documentation to be used correctly.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Parameters2/5
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
The parameter descriptions in 'Args' merely restate the schema field names and defaults (e.g., 'query: The search query string') without adding meaningful semantics. 'Deep search the web content' is vague. Schema coverage is 0%, and the description adds only trivial value.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Purpose4/5
Does the description clearly state what the tool does and how it differs from similar tools?
The description states 'Search Baidu and return formatted results,' which clearly identifies the tool's action (search) and resource (Baidu), and implies output formatting. No sibling tools exist, so differentiation is not needed. However, it could be more specific about the result format (e.g., titles, URLs, snippets).
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Usage Guidelines2/5
Does the description explain when to use this tool, when not to, or what alternatives exist?
No guidance is provided on when to use this tool or its limitations. For a search tool, one would expect notes on query syntax, rate limits, or alternatives, but none are given.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
1 tool update
v1.0.0- First observed
search
TDQS
B3/5.0
Scored across 1 tool
Disambiguation5/5
With only one tool, there is no possibility of confusion between different operations. The tool's purpose is clear and distinct.
Naming Consistency5/5
The single tool is consistently named 'search', following a verb-only pattern that matches its action. There is no inconsistency.
Tool Count3/5
A single tool for a search server is functional but minimal. It falls into the borderline category where the tool count feels thin for a typical API surface.
Completeness4/5
The search tool includes essential parameters like query, max_results, and deep_mode. However, it lacks other common search features like image or news search, leaving minor gaps.
Maintenance
ActivityInactive
ResponsivenessUnresponsive
Related MCP Connectors
Web search, page extraction, visual tools and developer utilities through Baizhi Cloud.
Provides AI assistants with access to Seltz's powerful Web Search capabilities.
Web search, fetch, extract, and research for AI agents. Markdown output + AI-synthesized answers.
Web search, browser automation, scraping, crawling and CAPTCHA solving for AI agents.
Related MCP Servers
- AlicenseBqualityCmaintenanceEnables web search through DuckDuckGo and webpage content fetching with intelligent text extraction. Features built-in rate limiting and LLM-optimized result formatting for seamless integration with language models.2MIT
- FlicenseAqualityDmaintenanceProvides web search capabilities across multiple engines and webpage content fetching to simplified Markdown. It enables AI assistants to access real-time internet information and extract text from specific URLs.213-
- 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-