Web Research Assistant
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| MCP_USAGE_LOG | No | Location for usage analytics data | ~/.config/web-research-assistant/usage.json |
| PIXABAY_API_KEY | No | API key for Pixabay image search. Get free key at pixabay.com/api/docs | |
| SEARXNG_BASE_URL | No | Endpoint queried by web_search | http://localhost:2288/search |
| SEARXNG_MAX_RESULTS | No | Hard cap on hits per request | 10 |
| MCP_MAX_RESPONSE_CHARS | No | Overall response limit applied to every tool reply | 8000 |
| SEARXNG_MCP_USER_AGENT | No | User-Agent header for outward HTTP calls | web-research-assistant/0.1 |
| SEARXNG_CRAWL_MAX_CHARS | No | Default character budget for crawl_url | 8000 |
| SEARXNG_DEFAULT_RESULTS | No | Default number of search hits | 5 |
| SEARXNG_DEFAULT_CATEGORY | No | Category used when none is provided | general |
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_searchC | Use this first to gather fresh web search results via the local SearXNG instance. |
| crawl_urlC | Fetch a URL and return the page text as markdown for quoting or analysis. |
| stealth_scrapeA | Scrape a URL using a stealth browser that bypasses anti-bot protections. |
| package_infoA | |
| search_examplesA | |
| search_imagesA | |
| package_searchB | |
| github_repoA | |
| translate_errorA | |
| api_docsA | |
| extract_dataA | |
| compare_techA | |
| get_changelogC | Get changelog and release notes for a package. |
| check_service_statusC | Check if an API service or platform is experiencing issues. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
| research_package | Generate a prompt for comprehensive package research. Use this when you want to thoroughly evaluate a package before adding it to your project. |
| debug_error | Generate a prompt for debugging an error message. Use this when you encounter an error and want help understanding and fixing it. |
| compare_technologies | Generate a prompt for comparing two technologies. Use this when deciding between two frameworks, libraries, or tools. |
| evaluate_repository | Generate a prompt for evaluating a GitHub repository. Use this when deciding whether to use or contribute to an open source project. |
| check_service_health | Generate a prompt for checking multiple service statuses. Use this when you suspect infrastructure issues or before a deployment. Provide comma-separated service names. |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
| get_domain_health_resource | Per-domain fetch success/failure rates, block rates, and stealth escalation stats. |
TDQS
Scored across 14 tools
Each tool targets a distinct research task (e.g., web_search vs. api_docs vs. compare_tech), with clear descriptions that prevent overlap. Even similar tools like crawl_url and stealth_scrape are differentiated by use cases.
Names mostly follow a verb_noun or noun_noun pattern with underscores, but there are minor inconsistencies (e.g., 'github_repo' vs. 'check_service_status'). Overall readable and predictable.
14 tools are well-scoped for a web research assistant, covering searching, fetching, extracting, and analyzing without being overwhelming or too few.
Covers core research workflows (search, fetch, extract, compare, check status, find packages/images/errors). Minor gaps like direct social media scraping are acceptable for the stated purpose.