agentfetch-mcp
Related Servers
Alternatives to agentfetch-mcp
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityBmaintenanceEnables LLM agents to fetch web pages and receive clean, readable markdown with token budgeting and link extraction.1MIT
- AlicenseNot gradedqualityAmaintenanceEnables AI agents to fetch web pages, strip noise, and convert content into clean Markdown with link preservation, caching, and configurable crawling for token-efficient scraping.MIT
- FlicenseNot gradedqualityAmaintenanceEnables AI agents to quickly fetch webpages, strip noise, and convert content into clean, link-preserving Markdown with caching and optional multi-page crawling for token-efficient web scraping.-
- AlicenseAqualityDmaintenanceEnables AI agents to fetch any web page as clean markdown or screenshot it, turning URLs into LLM-ready context.24 npmMIT
- AlicenseNot gradedqualityAmaintenanceEnables AI agents and LLM pipelines to fetch webpages, strip noise, preserve links, and convert content to clean Markdown with caching and configurable crawling for token-efficient scraping.MIT
- AlicenseAqualityCmaintenanceEnables AI agents to fetch any web page and receive clean, token-efficient Markdown, escalating only as needed from direct HTTP with browser TLS fingerprints to headless-browser rendering and residential proxies when a site blocks access. Supports question-focused passage retrieval with BM25 ranking, pagination, caching, JS rendering control, and safe-by-default restrictions on local and private-network URLs.1AGPL 3.0
TDQS
Scored across 4 tools
Each tool has a clearly distinct purpose: estimate_tokens is for token estimation without body fetch, fetch_url for single URL fetch, fetch_multiple for batch fetch, search_and_fetch for combined search and fetch. No overlap in functionality.
All tool names use consistent snake_case with a verb_noun pattern. The verbs are clear (estimate, fetch, fetch, search_and_fetch) and the nouns differentiate the actions (tokens, url, multiple, and_fetch).
With 4 tools, the set is concise and well-scoped for a web fetching and searching service. Each tool addresses a core need: estimating, single fetch, batch fetch, and combined search+fetch.
The tool set covers the primary workflows of fetching URLs and searching. A possible gap is the lack of a search-only tool that returns just snippets without fetching, but given the server's focus on fetching, the current set is largely complete.