WebSurfer MCP
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| MCP_USER_AGENT | No | User-Agent string for outgoing requests. | MCP-URL-Search-Server/1.0.0 |
| MCP_MAX_TIMEOUT | No | Maximum allowed timeout in seconds. | 60 |
| MCP_DEFAULT_TIMEOUT | No | Default request timeout in seconds. | 10 |
| MCP_MAX_CONTENT_LENGTH | No | Maximum content size in bytes (default 10MB). | 10485760 |
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
Server capabilities have not been inspected yet.
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| search_urlC | Fetch and return plain-text content from a web page URL. Handles various content types and provides comprehensive error handling. |
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 1 tool
With only one tool, there is no possibility of ambiguity or overlap between tools, making disambiguation perfect.
The single tool name 'search_url' follows a clear verb_noun pattern, and with no other tools, consistency is inherently perfect.
One tool is too few for a server named 'WebSurfer MCP', which suggests broader web navigation or interaction capabilities beyond just fetching content from a URL.
The tool surface is severely incomplete for a web surfing domain; it lacks basic operations like navigating links, interacting with forms, or handling dynamic content, leaving significant gaps for agent workflows.