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 提供多引擎 Web 搜索功能的 Model Context Protocol (MCP) 服务器。支持在 Google、Bing、DuckDuckGo、Brave、Yahoo 和 Yandex 之间搜索，并具备自动引擎路由和结构化 JSON 结果。
功能
✅ 多引擎支持：可访问 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 一起使用
将以下内容添加到你的 Claude Desktop 配置（macOS 上的 ~/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）——尽力而为，因此请检查每个结果是包含 content 还是 content_error。
参数：
q（必填）：搜索查询字符串（最多 500 个字符）include_content（可选，布尔值）：同时获取排名靠前结果的完整页面内容（markdown）。尽力而为——约 79% 的结果 URL 会返回内容；被屏蔽或不允许爬虫抓取的页面则返回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.-