Serpex MCP
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| SERPEX_API_KEY | Yes | Your API key from serpex.dev |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Server capabilities have not been inspected yet.
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| serpex_searchB | Search the web using Serpex API. Returns structured search results from multiple engines (Google, Bing, DuckDuckGo, Brave, Yahoo, Yandex). |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 1 tool
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.
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.
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.
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.