Web Explorer MCP
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
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
} |
| logging | {} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| extensions | {
"io.modelcontextprotocol/ui": {}
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| web_search_toolA | Perform web search using SearxNG instance. This tool searches the web using a local SearxNG instance and returns structured search results. It provides title, description, and URL for each result with support for pagination. The tool handles errors gracefully and returns them in the response rather than raising exceptions. |
| webpage_content_toolA | Extract and clean webpage content for a provided URL. This tool extracts full content from webpages using Playwright with JavaScript rendering. Content is automatically paginated for display if it exceeds max_chars. |
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 completely distinct purposes: one performs web searches and the other extracts content from a given URL. There is no overlap or ambiguity between them.
Both tool names follow a consistent pattern: a descriptive noun phrase followed by '_tool' (web_search_tool, webpage_content_tool). This makes the naming predictable and clear.
With only 2 tools, the server feels minimal for a 'Web Explorer' purpose. While the two tools cover search and content retrieval, the count is borderline and could benefit from additional tools like link extraction or history management.
The tool set covers the core web exploration workflow: searching and fetching content. It lacks some advanced operations like extracting specific elements or managing browsing sessions, but the primary needs are met without major gaps.