multi-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
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| echoA | Echo back the input text |
| timestampA | Get the current date and time |
| mathA | Evaluate a math expression (add, subtract, multiply, divide, parentheses) |
| hashC | Generate a hash of the input text using various algorithms |
| base64B | Encode or decode base64 strings |
| uuidB | Generate one or more UUIDs |
| list-toolsA | List all available tools with descriptions and usage examples |
| scrapeA | Fetch a URL with Cloudflare bypass, retries, and optional metadata. Returns raw HTML. |
| domB | Parse HTML with jsdom and execute DOM operations (query, attr, text, html, links, images, tables, forms, etc.). |
| scrape-domA | Scrape a URL, parse with jsdom, and extract data via structured DSL or low-level operations. Supports pagination. |
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 10 tools
The utility tools are clearly distinct, but scrape, scrape-dom, and dom overlap in fetching URLs and working with HTML/DOMs, so an agent could select the wrong one. Descriptions clarify raw HTML vs structured extraction vs in-memory DOM operations, but the boundaries are not immediately obvious from names alone.
All names are lowercase, but the set mixes single-word nouns (timestamp, math, uuid), single-word verbs (echo, scrape), and hyphenated verb-noun names (list-tools, scrape-dom). The naming is readable and predictable in tone, but not structurally consistent.
Ten tools is within a reasonable scope for a multi-purpose server, and each tool has a defined function. The utility side adds some trivial tools, but the overall count is not excessive or too thin.
The utility side covers common helper operations, and the scraping side provides raw fetch, structured extraction, and DOM manipulation with pagination support. There are minor gaps like limited HTTP request customization, but no critical dead ends for the apparent purpose.