mcp-www
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| MCP_DNS_SERVER | No | Override the default system DNS resolver (e.g., 192.168.68.133:5335) |
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 | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| discoverA | DNS-only lookup. Returns all _mcp.{domain} TXT records — there can be multiple, each advertising a different MCP server. Fast, cheap, no HTTP calls. Supports single domain or batch lookup across multiple domains. |
| discover_browseA | DNS lookup + server card in one call. Looks up all _mcp.{domain} TXT records, then fetches .well-known/mcp.json for server metadata. Only falls back to MCP initialize if no server card is found. Lighter than browse — no MCP session unless needed. |
| browseA | Inspect a domain or server URL. Tries .well-known/mcp.json (server card) first, only falls back to MCP initialize handshake if no server card is found. For domains: also performs DNS lookup for _mcp TXT records. |
| call_remote_toolA | Call a tool on a remote MCP server. Use browse first to discover available tools, then use this to execute them. |
| read_remote_resourceA | Read a resource from a remote MCP server. Use browse first to see available resources, then use this to read one by its URI. |
| get_remote_promptA | Get a prompt from a remote MCP server. Use browse first to see available prompts, then use this to retrieve one with optional arguments. |
| installA | Generate client configuration to permanently register a discovered MCP server. Returns config file paths and JSON entries for Claude Desktop, VS Code, Cursor, and Windsurf. The agent should then read the target config file, merge the entry, and write it back. Accepts a server URL directly or a domain (runs discovery first). |
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 7 tools
The overlap between `browse` and `discover_browse` is significant—both perform DNS lookup and fetch server card data, with only a subtle distinction in that `browse` can also take a server URL directly. `discover` nests within `browse` as a subset, further blurring boundaries. This ambiguity makes it difficult for an agent to reliably select the correct discovery tool.
The naming mixes bare verbs (`discover`, `browse`, `install`) with compound verb-adjective-noun patterns (`call_remote_tool`, `read_remote_resource`, `get_remote_prompt`), and `discover_browse` is an unusual verb-verb compound. While all names are readable and mostly intuitive, the lack of a uniform verb_noun pattern prevents full consistency.
Seven tools is a well-scoped size for a server that handles discovery, inspection, remote interaction, and installation. The count covers all necessary phases without excessive bloat, and each tool has a clear role in the workflow, even if some overlap exists.
The tool set covers the complete lifecycle: DNS-based discovery, metadata inspection via server cards, remote tool/resource/prompt access, and installation configuration. There are no obvious missing operations for the stated purpose, and the browse function adequately lists available capabilities.