MCP NPX Fetch
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
Server capabilities have not been inspected yet.
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| fetch_htmlC | Fetch a website and return the content as HTML |
| fetch_markdownC | Fetch a website and return the content as Markdown |
| fetch_txtA | Fetch a website, return the content as plain text (no HTML) |
| fetch_jsonC | Fetch a JSON file from a URL |
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 4 tools
Each tool has a clearly distinct purpose based on the output format (HTML, JSON, Markdown, plain text), with no overlap in functionality. The descriptions explicitly differentiate them by content type, making tool selection straightforward for an agent.
All tools follow a consistent verb_noun pattern with 'fetch_' prefix and suffix indicating the output format (e.g., fetch_html, fetch_json). The naming is perfectly uniform and predictable across all four tools.
With 4 tools, this server is well-scoped for fetching content in different formats. Each tool earns its place by covering a distinct output type, and the count is neither too thin nor excessive for the domain of URL-based content retrieval.
The toolset covers the core fetching operations for common content types (HTML, JSON, Markdown, plain text), with no dead ends. A minor gap exists in not handling other formats like XML or binary data, but agents can work around this for most use cases.