F
licenseNot graded
qualityC
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
Web Search: Perform web searches using
serpex_searchwith up to 500-character queries.Multi-Engine Support: Choose from auto (default), google, bing, duckduckgo, brave, yahoo, yandex; auto routes to the best available engine.
Time Filtering: Filter by all, day, week, month, or year.
Structured Results: Get clean, consistent JSON responses.
Content Retrieval: Optionally fetch full page content in markdown for top 5 or 10 results using
include_contentandcontent_results(best-effort, ~79% success; failures returncontent_error).Reliability: Includes built-in captcha handling and proxy rotation.
Integration: Works with MCP-compatible clients like Claude Desktop and Jan AI.
Provides web search capabilities through Brave's search engine, accessible via the Serpex API with support for time-based filtering and structured JSON results
Enables web search functionality through DuckDuckGo's search engine, accessible via the Serpex API with support for time-based filtering and structured JSON results
Provides web search capabilities through Google's search engine, accessible via the Serpex API with support for time-based filtering and structured JSON results
Click on "Install Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@Serpex MCPfind recent articles about quantum computing breakthroughs"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
Serpex MCP
A Model Context Protocol (MCP) server that provides multi-engine web search capabilities through the Serpex API. Search across Google, Bing, DuckDuckGo, Brave, Yahoo, and Yandex with automatic engine routing and structured JSON results.
Features
✅ Multi-Engine Support: Access 6 search engines (Google, Bing, DuckDuckGo, Brave, Yahoo, Yandex)
✅ Auto Routing: Automatically selects the best available search engine
✅ Time Filtering: Filter results by day, week, month, or year
✅ Structured Results: Clean, consistent JSON responses
✅ Fast & Reliable: Built-in captcha handling and proxy rotation
✅ Easy Integration: Works with Claude Desktop, Jan AI, and any MCP-compatible client
Related MCP server: Serper Search and Scrape MCP Server
Installation
Quick Start (npx - Recommended)
No installation needed! Use npx to run directly:
npx serpex-mcpGlobal Installation
npm install -g serpex-mcpLocal Installation
npm install serpex-mcpUsage
With Claude Desktop
Add to your Claude Desktop config (~/Library/Application Support/Claude/claude_desktop_config.json on macOS):
{
"mcpServers": {
"serpex": {
"command": "npx",
"args": ["-y", "serpex-mcp"],
"env": {
"SERPEX_API_KEY": "your-api-key-here"
}
}
}
}With Other MCP Clients
Any MCP-compatible client can use this server. Configure it with:
Command:
npxArguments:
-y serpex-mcpEnvironment:
SERPEX_API_KEY=your-key
Standalone
export SERPEX_API_KEY="your-api-key-here"
serpex-mcpAvailable Tools
serpex_search
Search the web using Serpex multi-engine API. Optionally fetches full page content
(markdown) for the top results inline with the search — best-effort, so check each
result for content vs content_error.
Parameters:
q(required): Search query string (max 500 characters)include_content(optional, boolean): Also fetch full page content (markdown) for the top results. Best-effort — roughly 79% of result URLs return content; blocked or robots-disallowed pages returncontent_errorinstead. Default:false.content_results(optional,5 | 10): Number of top results to fetch content for, wheninclude_contentistrue. Must be exactly5or10. Default:5.
Example:
{
"q": "artificial intelligence trends 2025",
"include_content": true,
"content_results": 5
}Response (JSON, as tool output text) includes content_requested /
content_delivered counts and, per result, content on success or content_error
on failure — both keys are omitted when content wasn't requested.
Getting Your API Key
Visit serpex.dev
Sign up for a free account
Get your API key from the dashboard
Use it in the
SERPEX_API_KEYenvironment variable
API Information
Base URL:
https://api.serpex.devDocumentation: https://serpex.dev/docs
Pricing: Free tier available, affordable paid plans
Development
Build from Source
git clone https://github.com/divyeshradadiya/serpex-mcp.git
cd serpex-mcp
pnpm install
pnpm buildRun Tests
export SERPEX_API_KEY="your-key-here"
pnpm testLicense
MIT
Links
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.
TDQS
B3.3/5.0
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
Resources
Unclaimed servers have limited discoverability.
Looking for Admin?
If you are the server author, to access and configure the admin panel.
Related MCP Connectors
Web search, news, page retrieval, sitemaps, and trending topics through Search1API.
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.
Search Google straight from your AI agent. Web results, images, videos, news, products, scholarly ar
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.23,022MIT
- 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.
Latest Blog Posts
- Who's Calling? MCP Hosts Are an Identity Blind Spot (And the Spec Knows It)By Om-Shree-0709 on .mcpAgent IdentityOAuth 2.1
- Your AI Chatbot Just Exposed Your CEO's Salary to an InternBy Om-Shree-0709 on .Agent IdentityMCP SecurityOAuth Delegation
- Why MCP Servers Need Execution Sandboxing (And Why Your Current Stack Isn't Enough)By Om-Shree-0709 on .Agentic AiPrompt InjectionWebAssembly
MCP directory API
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/divyeshradadiya/serpex-mcp'
If you have feedback or need assistance with the MCP directory API, please join our Discord server