A
licenseNot graded
qualityD
maintenanceWeb search, clean page reading & one-call research dossiers for AI agents. No API key — your agent does the synthesis.
58 npm
MIT
contextfetch-mcp
by lachy3433
Related Servers
Alternatives to contextfetch-mcp
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityAmaintenanceEnables AI agents to perform live web searches with ranked results and extracted page passages, plus clean markdown extraction of any URL.MIT
- FlicenseNot gradedqualityAmaintenanceEnables AI agents to search multiple web providers in parallel and crawl single pages or entire sites into clean, deduplicated Markdown or JSON, including authenticated crawls.-
- FlicenseNot gradedqualityAmaintenanceEnables AI agents to search the web across configured providers and crawl individual pages or entire sites into clean, deduplicated Markdown or JSON.-
EnConvert MCP Serverofficial
AlicenseAqualityAmaintenanceEnables AI agents to convert files, render web pages to markdown/PDF/screenshots, search the live web, extract structured data, ingest RAG-ready chunks, and monitor pages for changes through a single API key.24106 npm7MIT- FlicenseNot gradedqualityAmaintenanceEnables AI agents to search the web through configured providers and crawl pages or entire sites into clean, deduplicated Markdown or JSON, including authenticated crawls.-
TDQS
A4.1/5.0
Scored across 11 tools
Disambiguation4/5
Most tools target clearly distinct operations (search, extract_url, crawl, map, find_similar, balance). The main overlap is contextfetch_research vs contextfetch_deep_research, which the description openly admits is essentially the same tool kept for backwards compatibility, plus some conceptual overlap among search/answer/research.
Naming Consistency4/5
All names use a consistent contextfetch_ prefix and snake_case, making the set predictable. The only deviation is that some are verb_noun (extract_url, find_similar, get_free_key) while others are bare verbs or nouns (search, answer, crawl, map, balance), but this is minor and readable.
Tool Count5/5
11 tools is well within the ideal 3-15 range for a web-context service. Each tool covers a distinct capability (fetch, crawl, search, research, discovery, billing), with only the redundant deep_research arguably not earning a slot.
Completeness5/5
The surface covers the full lifecycle for a web-context service: onboarding (get_free_key), discovery (map, find_similar), retrieval (extract_url, crawl, search), synthesis (research, answer) and account management (balance, auto_reload). No obvious dead ends for the stated purpose.