MCP Node 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 |
|---|---|
| extract-html-fragmentC | Extract a specific HTML fragment from a webpage using CSS selectors |
| fetch-urlC | Fetch content from a URL |
| check-statusB | Check if a URL is accessible (HEAD request) |
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 3 tools
Each tool has a clearly distinct purpose: check-status performs a HEAD request to verify accessibility, extract-html-fragment parses HTML content with CSS selectors, and fetch-url retrieves full content. There is no overlap in functionality, making tool selection straightforward for an agent.
The tools follow a consistent verb-noun pattern (check-status, extract-html-fragment, fetch-url), with all names using kebab-case. The minor deviation is that 'fetch-url' uses a verb-noun structure while the others are verb-adjective-noun, but the pattern remains readable and predictable.
With 3 tools, this server is well-scoped for its purpose of URL fetching and HTML processing. Each tool earns its place by covering distinct aspects: status checking, content fetching, and HTML extraction, without being overly sparse or bloated.
The tool set covers core workflows for URL interaction: checking accessibility, fetching content, and extracting specific data. A minor gap is the lack of tools for more advanced operations like POST requests or handling different content types, but agents can work around this for basic use cases.