A
licenseA
qualityD
maintenanceProvides functionality to fetch web content in various formats, including HTML, JSON, plain text, and Markdown.
4
73,147 npm
2
MIT
Fetch MCP Server
by goswamig
Related Servers
Alternatives to Fetch MCP Server
No user-submitted related servers found.
Related Servers
- AlicenseAqualityDmaintenanceProvides functionality to fetch web content in various formats, including HTML, JSON, plain text, and Markdown.46,053 npm827MIT
- AlicenseNot gradedqualityDmaintenanceFetches web content and returns it in HTML, JSON, plain text, or Markdown format.6,053 npmMIT
- AlicenseNot gradedqualityDmaintenanceEnables fetching and converting web content into various formats including HTML, JSON, plain text, and Markdown. It supports custom request headers and provides specialized tools for on-demand web data retrieval and transformation.73,147 npmMIT
- AlicenseNot gradedqualityCmaintenanceProvides functionality to fetch and transform web content in various formats (HTML, JSON, plain text, and Markdown) through simple API calls.73,147 npm1MIT
- AlicenseAqualityDmaintenanceProvides tools to fetch web content in HTML, JSON, text, or Markdown formats via MCP. Supports custom headers, length limits, and start index.4MIT
TDQS
B3.3/5.0
Scored across 4 tools
Disambiguation4/5
The tools are mostly distinct, with each handling a different content type (HTML, JSON, Markdown, plain text). However, fetch_html and fetch_txt could be slightly confusing as both fetch websites, but their output formats (HTML vs. plain text) clarify the distinction. There is no significant overlap in purpose.
Naming Consistency5/5
All tool names follow a consistent verb_noun pattern with 'fetch_' prefix and descriptive suffixes (html, json, markdown, txt). The naming is predictable and uniform, making it easy to understand the tool set at a glance.
Tool Count4/5
With 4 tools, the count is reasonable for a fetch server focused on retrieving different content types. It is slightly lean but covers core use cases well. A few additional tools (e.g., for handling errors or metadata) might enhance it, but it's not incomplete.
Completeness3/5
The server covers fetching various content types, which aligns with its purpose. However, there are notable gaps: no tools for handling HTTP methods beyond GET (e.g., POST), error handling, or configuration (e.g., headers, timeouts). This limits advanced use cases but suffices for basic retrieval.
Maintenance
ActivityInactive
ResponsivenessNo issues