MCP Smart Searcher
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| LOG_LEVEL | No | Logging level | INFO |
| PROXY_URL | No | Proxy URL | http://127.0.0.1:7890 |
| USE_PROXY | No | Enable proxy | true |
| GITHUB_TOKEN | No | GitHub API token | (none) |
| PROXY_ENGINES | No | Comma-separated engines using proxy | (all) |
| TAVILY_API_KEY | No | Tavily AI Search API key | (none) |
| DEFAULT_SEARCH_ENGINE | No | Default search engine | duckduckgo |
| MAX_CONCURRENT_SEARCH | No | Max concurrent search requests | 5 |
| ALLOWED_SEARCH_ENGINES | No | Comma-separated engine allowlist | (all allowed) |
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
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| web_searchA | Search the web using one or more search engines simultaneously. Args: query: Search query string (non-empty) engines: Search engines to use (duckduckgo, baidu, juejin, github, github_code, tavily) limit: Maximum number of results per engine (1-50, default 10) Returns: Formatted search results from all specified engines |
| fetch_web_contentA | Fetch and extract text content from any public URL. Args: url: Public HTTP/HTTPS URL to fetch prompt: Optional hint for what to extract. When provided, the content is filtered to prioritize paragraphs most relevant to the prompt keywords. Useful for AI agents to focus on specific content (e.g., "extract code examples only", "summarize the main argument"). max_chars: Maximum characters to return (default 30000) Returns: Extracted text content from the webpage, optionally filtered by prompt |
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 clearly distinct purposes: one fetches content from a specific URL, the other performs web searches. There is no overlap or ambiguity.
Both tool names follow a consistent verb_noun pattern (fetch_web_content, web_search) using snake_case, making them predictable and easy to understand.
With only 2 tools, the server is minimal but covers the basic search-and-fetch workflow. It feels slightly thin for a server named 'Smart Searcher' as it lacks additional features like content summarization or multi-URL fetch.
The surface covers the core operations of searching and fetching web content, but there are notable gaps such as no tool to fetch search results directly or to handle multiple URLs. Agents may need to combine calls manually.