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
Ein Model Context Protocol (MCP)-Server, der Multi-Engine-Websuche über die Serpex API bereitstellt. Durchsuchen Sie Google, Bing, DuckDuckGo, Brave, Yahoo und Yandex mit automatischem Engine-Routing und strukturierten JSON-Ergebnissen.
Funktionen
✅ Multi-Engine-Unterstützung: Zugriff auf 6 Suchmaschinen (Google, Bing, DuckDuckGo, Brave, Yahoo, Yandex)
✅ Automatisches Routing: Wählt automatisch die beste verfügbare Suchmaschine aus
✅ Zeitfilterung: Ergebnisse nach Tag, Woche, Monat oder Jahr filtern
✅ Strukturierte Ergebnisse: Saubere, konsistente JSON-Antworten
✅ Schnell & zuverlässig: Integrierte Captcha-Verarbeitung und Proxy-Rotation
✅ Einfache Integration: Funktioniert mit Claude Desktop, Jan AI und jedem MCP-kompatiblen Client
Related MCP server: Serper Search and Scrape MCP Server
Installation
Schnellstart (npx - empfohlen)
Keine Installation erforderlich! Verwenden Sie npx, um direkt zu starten:
npx serpex-mcpGlobale Installation
npm install -g serpex-mcpLokale Installation
npm install serpex-mcpVerwendung
Mit Claude Desktop
Fügen Sie Folgendes zu Ihrer Claude Desktop-Konfiguration hinzu (~/Library/Application Support/Claude/claude_desktop_config.json unter macOS):
{
"mcpServers": {
"serpex": {
"command": "npx",
"args": ["-y", "serpex-mcp"],
"env": {
"SERPEX_API_KEY": "your-api-key-here"
}
}
}
}Mit anderen MCP-Clients
Jeder MCP-kompatible Client kann diesen Server verwenden. Konfigurieren Sie ihn mit:
Befehl:
npxArgumente:
-y serpex-mcpUmgebungsvariable:
SERPEX_API_KEY=your-key
Eigenständiger Betrieb
export SERPEX_API_KEY="your-api-key-here"
serpex-mcpVerfügbare Tools
serpex_search
Durchsuchen Sie das Web mit der Serpex-Multi-Engine-API. Optional wird der vollständige Seiteninhalt
(Markdown) der Top-Ergebnisse direkt mit der Suche abgerufen – nach bestem Bemühen. Prüfen Sie daher jedes
Ergebnis auf content bzw. content_error.
Parameter:
q(erforderlich): Suchanfrage (maximal 500 Zeichen)include_content(optional, boolesch): Ruft auch den vollständigen Seiteninhalt (Markdown) für die Top-Ergebnisse ab. Nach bestem Bemühen – etwa 79 % der Ergebnis-URLs liefern Inhalte; blockierte oder von Robots ausgeschlossene Seiten liefern stattdessencontent_error. Standard:false.content_results(optional,5 | 10): Anzahl der Top-Ergebnisse, für die Inhalte abgerufen werden sollen, wenninclude_contentauftruegesetzt ist. Muss genau5oder10sein. Standard:5.
Beispiel:
{
"q": "artificial intelligence trends 2025",
"include_content": true,
"content_results": 5
}Antwort (JSON, als Tool-Ausgabetext) enthält content_requested /
content_delivered-Zähler und, pro Ergebnis, content bei Erfolg oder content_error
bei Fehler – beide Schlüssel werden weggelassen, wenn keine Inhalte angefordert wurden.
So erhalten Sie Ihren API-Schlüssel
Besuchen Sie serpex.dev
Registrieren Sie sich für ein kostenloses Konto.
Holen Sie Ihren API-Schlüssel aus dem Dashboard.
Verwenden Sie ihn in der Umgebungsvariable
SERPEX_API_KEY.
API-Informationen
Basis-URL:
https://api.serpex.devDokumentation: https://serpex.dev/docs
Preise: Kostenloser Tarif verfügbar, erschwingliche kostenpflichtige Pläne.
Entwicklung
Aus dem Quellcode erstellen
git clone https://github.com/divyeshradadiya/serpex-mcp.git
cd serpex-mcp
pnpm install
pnpm buildTests ausführen
export SERPEX_API_KEY="your-key-here"
pnpm testLizenz
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.
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.-