smart-web-search-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| SERPER_API_KEY | No | Optional Serper API key (L3, Google; 2500 one-time free, then paid). Without it, serper is skipped (opt-in). | |
| TAVILY_API_KEY | No | Optional Tavily API key (L2, 1000/mo free). Without it, tavily is skipped (opt-in). | |
| KEENABLE_API_KEY | No | Optional Keenable API key for the free tier (100K/mo). Without it, the shared public tier is used (1K req/hour, auto-backoff on 429). | |
| TINYFISH_API_KEY | No | Optional Tinyfish API key (L2, pay-as-you-go). Without it, tinyfish is skipped. |
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
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| smart_web_searchA | 5-provider web search with cascade routing. L1 wigolo (free, 18 engines) + keenable (100K/mo free, independent index) in parallel → L2 tinyfish → tavily (serial; AI-optimized, 1000/mo free) → L3 serper (Google, 2500 free then paid). Returns search results as readable blocks (Title/URL/Snippet) with a one-line routing footer; output_format=json gives a structured envelope. Use this as the DEFAULT web search tool. |
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
There is only one tool, so there is no possibility of misselection or overlapping purpose. Its stated role as the default web search entry point is unambiguous.
A single snake_case name (smart_web_search) is clean and readable, and with only one tool there is nothing to be inconsistent with. No mixed conventions or vague verbs appear.
Web search is fundamentally a single operation, so one tool is a defensible scope rather than a mismatch. It is slightly thin in that provider targeting, filtering, or page fetching are not exposed as separate capabilities.
The search capability itself is unusually thorough, with multi-provider cascade routing, parallel/serial fallbacks, and both block and JSON output formats. The only notable gap is the absence of any companion operation such as fetching/extracting the content behind a result URL.