web-basics-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| SEARXNG_URL | No | The URL of the SearXNG server. Default is http://127.0.0.1:8088. | http://127.0.0.1:8088 |
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_searchA | Run one web query through the first available search provider and return formatted source URLs plus the provider response. |
| fetch_urlA | Fetch one public HTTP(S) URL. Returns clean Markdown for pages and Reddit posts, extracted PDF text, direct text data, or a supported image. Use start_index to continue truncated text. |
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 perform fundamentally different operations: one searches the web, the other fetches a specific URL. There is zero overlap in purpose, so an agent can clearly distinguish which tool to use for a given task.
Both tools use a verb_noun pattern ('web_search' and 'fetch_url'), which is consistent and readable. 'web_search' could be parsed as 'search the web' but the prefix 'web_' is used similarly, so the pattern is predictable. Minor deviation: 'web_search' vs 'fetch_url' both place the verb first, so it's actually consistent.
With only two tools, the server feels minimal, which is on the borderline for a dedicated web-basics server. Both tools are essential and non-redundant, but the count is thin—though it may be appropriate for a focused utility server.
For a 'web-basics' domain, search and fetch cover the core operations an agent would need. The fetch tool handles multiple content types and page truncation, which is good. Minor gaps exist (e.g., no way to submit forms or list search history), but these are not expected for a basics server.