A
licenseA
qualityD
maintenanceA powerful MCP server for fetching and transforming web content into various formats (HTML, JSON, Markdown, Plain Text) with ease.
4
4,278 npm
42
MIT
MCP Node Fetch
by mcollina
Related Servers
Alternatives to MCP Node Fetch
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityDmaintenanceA web fetching MCP server with HTTP proxy support, allowing AI to retrieve web content in markdown, text, or HTML format while handling anti-crawler detection and redirects.1,526 npm1MIT
- AlicenseAqualityCmaintenanceAn MCP server for fetching and transforming web content into various formats.48MIT
- AlicenseAqualityBmaintenanceAn MCP server that enables AI assistants to fetch web content in multiple formats (HTML, JSON, text, Markdown) with intelligent content extraction, chunk management, and browser automation support.5213 npm15MIT
- AlicenseAqualityCmaintenanceMCP server that provides web content fetching, summarization, comparison, and extraction capabilities, handling up to 20 URLs per request.343 npm8MIT
- AlicenseAqualityDmaintenanceMCP server for fetching web pages without robots.txt restrictions, supporting all standard HTTP methods, custom headers, body, redirect control, and timeout settings.17 npmMIT
TDQS
B3.4/5.0
Scored across 3 tools
Disambiguation5/5
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.
Naming Consistency4/5
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.
Tool Count5/5
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.
Completeness4/5
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.
Maintenance
ActivityInactive
ResponsivenessNo issues