fetchrouter-mcp
Related Servers
Alternatives to fetchrouter-mcp
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityDmaintenanceProvides AI agents with reliable web fetching capabilities, handling retries, caching, and anti-bot bypass automatically.MIT
- AlicenseAqualityAmaintenanceEnables AI agents to open, read, and act on live web pages through verified browser actions, including filling forms, extracting data, debugging pages, and handling bot walls.112MIT
- FlicenseNot gradedqualityBmaintenanceEnables AI agents to reliably fetch public web URLs and extract clean, agent-ready text, Markdown, links, and metadata, with automatic browser fallback and optional x402 payment support.-
- AlicenseAqualityAmaintenanceEnables AI agents to perform web searches, fetch and extract page content, and crawl sites with caching, rate limiting, and robots.txt compliance, all without needing API keys.15325 PyPI1MIT
- AlicenseBqualityAmaintenanceEnables AI agents to fetch web pages, convert them into token-efficient semantic Markdown, and extract hyperlinks and page metadata while rotating realistic browser fingerprints to reduce anti-bot blocks.3MIT
- AlicenseNot gradedqualityBmaintenanceEnables AI agents to search the web, read and extract content from webpages, fetch JSON from REST APIs, and collect links while bypassing anti-bot protections.22 npmISC
TDQS
Scored across 2 tools
The two tools have completely non-overlapping purposes: one performs a fetch, the other reports historical pass-rate statistics for routing decisions. An agent cannot reasonably confuse them, and the descriptions reinforce the distinction (fetch is billed, stats are free).
Both names use clean snake_case, which is consistent at the style level. However, 'fetch_page' is verb_noun while 'domain_reliability' is a noun phrase, so the action-oriented pattern isn't uniform across the set.
Two tools is on the thin side relative to the typical 3-15 range, but each earns its place: a core fetch operation plus a supporting diagnostic for choosing fetch settings. The surface is deliberately minimal rather than padded.
The stated purpose—reliably fetching a URL and choosing the right route—is well covered, including error reasons and a route-reliability lookup to guide retries. Minor gaps remain, such as batch fetching or a way to enumerate available routes/providers directly.