F
licenseNot graded
qualityD
maintenanceEnables web search across multiple search engines (DuckDuckGo, Bing, Startpage) with parallel execution and result deduplication. Also provides web page content extraction capabilities.
2
-
Serpex MCP
Serpex MCP
Serpex API를 통해 다중 엔진 웹 검색 기능을 제공하는 Model Context Protocol(MCP) 서버입니다. 자동 엔진 라우팅과 구조화된 JSON 결과로 Google, Bing, DuckDuckGo, Brave, Yahoo, Yandex에서 검색할 수 있습니다.
기능
✅ 다중 엔진 지원: 6개 검색 엔진(Google, Bing, DuckDuckGo, Brave, Yahoo, Yandex) 지원
✅ 자동 라우팅: 사용 가능한 최상의 검색 엔진을 자동 선택
✅ 시간 필터링: 일, 주, 월, 연도별로 결과 필터링
✅ 구조화된 결과: 깔끔하고 일관된 JSON 응답
✅ 빠르고 안정적: 내장된 캡차 처리 및 프록시 순환
✅ 간편한 통합: Claude Desktop, Jan AI 및 모든 MCP 호환 클라이언트에서 동작
Related MCP server: Serper Search and Scrape MCP Server
설치
빠른 시작 (npx - 권장)
설치가 필요 없습니다! npx로 직접 실행하세요:
npx serpex-mcp전역 설치
npm install -g serpex-mcp로컬 설치
npm install serpex-mcp사용 방법
Claude Desktop에서 사용
macOS의 경우 Claude Desktop 구성 파일(~/Library/Application Support/Claude/claude_desktop_config.json)에 추가하세요:
{
"mcpServers": {
"serpex": {
"command": "npx",
"args": ["-y", "serpex-mcp"],
"env": {
"SERPEX_API_KEY": "your-api-key-here"
}
}
}
}다른 MCP 클라이언트에서 사용
MCP 호환 클라이언트라면 모두 이 서버를 사용할 수 있습니다. 다음과 같이 구성하세요:
명령어:
npx인자:
-y serpex-mcp환경 변수:
SERPEX_API_KEY=your-key
독립 실행
export SERPEX_API_KEY="your-api-key-here"
serpex-mcp사용 가능한 도구
serpex_search
Serpex 다중 엔진 API를 사용하여 웹을 검색합니다. 선택적으로 상위 결과에 대해 전체 페이지 콘텐츠(markdown)를 검색 결과와 함께 가져옵니다. 최선 노력(best-effort) 방식이므로 각 결과에서 content와 content_error를 확인하세요.
매개변수:
q(필수): 검색 쿼리 문자열 (최대 500자)include_content(선택, boolean): 상위 결과에 대해 전체 페이지 콘텐츠(markdown)도 함께 가져옵니다. 최선 노력 방식으로, 결과 URL의 약 79%가 콘텐츠를 반환하며 차단되거나 robots가 금지한 페이지는 대신content_error를 반환합니다. 기본값:false.content_results(선택,5 | 10):include_content가true일 때 콘텐츠를 가져올 상위 결과 수입니다. 정확히5또는10이어야 합니다. 기본값:5.
예시:
{
"q": "artificial intelligence trends 2025",
"include_content": true,
"content_results": 5
}응답(JSON, 도구 출력 텍스트)에는 content_requested / content_delivered 개수가 포함되며, 각 결과에는 성공 시 content, 실패 시 content_error가 포함됩니다. 콘텐츠가 요청되지 않은 경우 두 키 모두 생략됩니다.
API 키 받기
serpex.dev를 방문하세요.
무료 계정에 가입하세요.
대시보드에서 API 키를 받으세요.
SERPEX_API_KEY환경 변수에 이 키를 사용하세요.
API 정보
기본 URL:
https://api.serpex.dev요금제: 무료 티어 이용 가능, 합리적인 유료 플랜
개발
소스에서 빌드
git clone https://github.com/divyeshradadiya/serpex-mcp.git
cd serpex-mcp
pnpm install
pnpm build테스트 실행
export SERPEX_API_KEY="your-key-here"
pnpm test라이선스
MIT
링크
Available Tools
1 toolserpex_searchB
Search the web using Serpex API. Returns structured search results from multiple engines (Google, Bing, DuckDuckGo, Brave, Yahoo, Yandex).
ParametersJSON Schema
| Name | Required | Description | Default |
|---|---|---|---|
| q | Yes | Search query (max 500 characters) | |
| engine | No | Search engine (default: auto) | |
| time_range | No | Filter by time range |
TDQS
B3.2/5.0
Behavior2/5
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are provided, so the description carries the full burden of behavioral disclosure. It mentions the API and return type (structured results from multiple engines), but fails to disclose critical traits such as rate limits, authentication needs, error handling, or pagination. For a search tool with no annotation coverage, this leaves significant gaps in understanding its behavior.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Conciseness5/5
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is a single, efficient sentence that front-loads the core purpose ('Search the web using Serpex API') and adds necessary detail ('Returns structured search results from multiple engines'). Every word earns its place with no redundancy or waste.
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 complexity of a search API tool with no annotations and no output schema, the description is incomplete. It lacks information on response format, error cases, rate limits, and authentication requirements. While the input schema is well-covered, the overall context for effective tool use is insufficient.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Parameters3/5
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
The schema description coverage is 100%, with all parameters well-documented in the input schema (e.g., query max length, engine options, time range enums). The description adds no additional parameter semantics beyond what the schema provides, so it meets the baseline of 3 for high schema coverage without compensating 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 clearly states the action ('Search the web') and resource ('using Serpex API'), specifying it returns structured results from multiple engines. It's specific about the verb and resource, but since there are no sibling tools, it doesn't need to distinguish from alternatives, making it clear but not requiring sibling differentiation.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Usage Guidelines3/5
Does the description explain when to use this tool, when not to, or what alternatives exist?
The description implies usage for web searching with structured results from multiple engines, but provides no explicit guidance on when to use this tool versus alternatives (e.g., other search methods or APIs). Since there are no sibling tools, it doesn't need to differentiate, but it lacks context on optimal use cases or exclusions.
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
- First observed
serpex_search
TDQS
B3.3/5.0
Scored across 1 tool
Disambiguation5/5
With only one tool, there is no possibility of ambiguity or overlap between tools. The single tool has a clear and distinct purpose: searching the web using the Serpex API.
Naming Consistency5/5
Since there is only one tool, naming consistency is inherently perfect. The tool name 'serpex_search' follows a clear and logical pattern, combining the server name with the action.
Tool Count2/5
A single tool is too few for a web search server, as it lacks essential operations like filtering results, handling pagination, or accessing specific search engines individually. This minimal set limits functionality and may cause agent failures in complex tasks.
Completeness2/5
The tool surface is severely incomplete for a web search domain. While the search tool exists, there are significant gaps such as no ability to refine searches, manage result formats, or perform advanced queries, which are common in search APIs.
Maintenance
ActivityMaintained
ResponsivenessNo issues
Related MCP Connectors
Web search, agentic search, news, page retrieval, sitemaps, and trending topics through Search1API.
Google, Bing, DuckDuckGo and Google Maps search results, free without an API key.
Provides AI assistants with access to Seltz's powerful Web Search capabilities.
LLM-ready web search + instant answers + URL-to-clean-text fetch for agents and RAG.
Related MCP Servers
- AlicenseBqualityDmaintenanceEnables web search via Serper API with advanced search operators and webpage scraping capabilities to extract content in plain text or markdown format.21,865 npmMIT
- AlicenseAqualityDmaintenanceEnables advanced web search across multiple search engines (Brave, DuckDuckGo, Google, Bing, Yandex) with intelligent backend selection, full content extraction, and advanced filtering by time, language, geography, and content type.3MIT
- FlicenseNot gradedqualityNot gradedmaintenanceEnables searching across multiple search engines (Google, Bing, YouTube, DuckDuckGo, etc.) and retrieving parsed search results via SerpApi integration.-