fast-web-search-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| FWSMCP_LOG_LEVEL | No | Log verbosity: debug, info, warn, error | warn |
| FWSMCP_PROVIDERS | No | Comma-separated provider list | duckduckgo,bing,wikipedia |
| FWSMCP_LOG_FORMAT | No | Log format: text or json | text |
| FWSMCP_CONFIG_FILE | No | Path to optional JSON config file | |
| FWSMCP_SAFE_SEARCH | No | Safe search level: off, moderate, strict | moderate |
| FWSMCP_SEARXNG_URL | No | Optional SearXNG instance URL | |
| FWSMCP_CACHE_ENABLED | No | Enable in-memory result cache | true |
| FWSMCP_DEFAULT_REGION | No | Default region for searches | us-en |
| FWSMCP_REDACT_QUERIES | No | Redact search queries in logs | true |
| FWSMCP_DEFAULT_LANGUAGE | No | Default language for searches | en |
| FWSMCP_FETCH_TIMEOUT_MS | No | Page fetch timeout (ms) | 15000 |
| FWSMCP_CACHE_MAX_ENTRIES | No | Maximum cache entries | 250 |
| FWSMCP_NEWS_CACHE_TTL_MS | No | News cache TTL (5 min) | 300000 |
| FWSMCP_PAGE_CACHE_TTL_MS | No | Page cache TTL (30 min) | 1800000 |
| FWSMCP_PROVIDER_STRATEGY | No | Strategy: fallback or merge | fallback |
| FWSMCP_SEARCH_TIMEOUT_MS | No | Search operation timeout (ms) | 20000 |
| FWSMCP_MAX_SEARCH_RESULTS | No | Maximum results per search | 25 |
| FWSMCP_DIAGNOSTICS_ENABLED | No | Enable diagnostics tool | false |
| FWSMCP_PROVIDER_TIMEOUT_MS | No | Per-provider timeout (ms) | 10000 |
| FWSMCP_RESEARCH_TIMEOUT_MS | No | search_and_fetch total timeout (ms) | 45000 |
| FWSMCP_SEARCH_CACHE_TTL_MS | No | Search cache TTL (15 min) | 900000 |
| FWSMCP_MAX_FETCH_CHARACTERS | No | Maximum characters per fetch | 100000 |
| FWSMCP_GLOBAL_EXCLUDE_DOMAINS | No | Comma-separated domains to always exclude |
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": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| web_searchC | Search the general web and return normalized results. |
| fetch_urlA | Fetch a public HTTP(S) URL and return extracted content as clean Markdown or plain text. |
| search_and_fetchB | Search the web and fetch the best results. One call for research: search, rank, and fetch the best few pages. |
| news_searchA | Search for recent news articles. Returns date-sensitive results with publisher and publication time. |
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 4 tools
Each tool has a clear primary purpose: fetch a specific URL, general search, combined search-and-fetch, and news-specific search. There is minor overlap between web_search and search_and_fetch, but the descriptions clarify that one returns results and the other also fetches the top pages.
The names mix verb-first (fetch_url), noun-first (web_search, news_search), and a combined form (search_and_fetch). The use of 'and' in search_and_fetch breaks the otherwise consistent underscore-separated pattern, making the naming slightly unpredictable.
Four tools is an appropriate scope for a search-and-fetch server. Each tool serves a distinct workflow step, and the count is neither too thin nor overburdened.
The tool set covers the full search-and-fetch lifecycle: searching, fetching a specific URL, combining both for efficiency, and filtering to news. No obvious missing operations for the stated domain.