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, Reddit posts, X posts, and YouTube video transcripts, 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
fetch_url and web_search target clearly separate actions—retrieving a single known URL vs. discovering URLs via a query. There is no realistic way to confuse one for the other.
Both names follow the same verb_noun snake_case pattern (fetch_url, web_search) and the verbs accurately signal their actions. Fully consistent.
Two tools is very thin, but it covers the minimal retrieve-and-discover pair that defines a 'web basics' server. It borders on underspecified, since there is no way to select a provider, batch fetches, or crawl links, but the scope is intentionally minimal.
Fetch and search together cover the core read-only web workflow, with fold-out detail like start_index pagination, PDF/image handling, and YouTube/Reddit/X support baked into the descriptions. Gaps remain for multi-URL fetching, link extraction, or provider choice, which agents must work around by issuing repeated calls.