web-search-plus-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| EXA_API_KEY | No | API key for Exa (Neural), best for semantic discovery and finding similar content. | |
| YOU_API_KEY | No | API key for You.com, used for real-time RAG and LLM-ready snippets. | |
| QUERIT_API_KEY | No | API key for Querit, used for multi-lingual AI search with real-time info. | |
| SERPER_API_KEY | No | API key for Serper (Google), used for facts, news, shopping, and local businesses. | |
| TAVILY_API_KEY | No | API key for Tavily, optimized for deep research, analysis, and explanations. | |
| SEARXNG_BASE_URL | No | Base URL for a self-hosted SearXNG instance (e.g., https://your-searxng-instance.example.com). | |
| PERPLEXITY_API_KEY | No | API key for Perplexity, used for AI-synthesized answers with citations. |
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
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| web_searchB | Source-only web search through the Web Search Plus v3 runtime. Routes across configured source-result providers and returns additive v3 evidence, routing receipts, provider attempts, cache provenance, and typed errors. |
| web_extractB | Source-only URL extraction through 9 Web Search Plus v3 providers. Responses preserve bounded-context limits, truncation warnings, evidence, and page-on-demand stored-content references. |
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 2 tools
The two tools have distinct purposes: web_search finds web content, while web_extract retrieves content from a specific URL. There is no overlap in their core actions.
Both tool names follow the same web_verb pattern, with clear and predictable naming. The convention is consistent and readable.
With only two tools, the server sits at the borderline of being too thin. The two tools are individually useful, but the small count suggests a narrow scope.
The server covers the two core operations one would expect for a web search and extraction service. Minor gaps like search result pagination or provider selection details exist but are not critical.