fusionproxy-mcp
OfficialRelated Servers
Alternatives to fusionproxy-mcp
No user-submitted related servers found.
Related Servers
- AlicenseBqualityBmaintenanceEnables 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.3140 PyPIMIT
- AlicenseNot gradedqualityCmaintenanceEnables MCP clients such as Claude, Cursor, and VS Code to fetch public web pages through residential IPs in a selected country, with optional sticky sessions, and to check the exit IP. Supports Markdown, plain text, or HTML output.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

JsonLink MCP Serverofficial
AlicenseAqualityCmaintenanceEnables AI agents to read any web page as clean Markdown, pull title/description/preview metadata, capture desktop, mobile, or full-page screenshots, and list every link or image on a URL. JavaScript-heavy pages are rendered in a real browser and blocked requests retried through a proxy, so agents can reach content they'd otherwise miss.561 npmMIT- AlicenseNot gradedqualityDmaintenanceEnables AI agents to fetch and extract clean, readable content from web pages, and search within pages for specific queries, without needing a full browser.1MIT
- AlicenseAqualityBmaintenanceEnables AI assistants to fetch public web pages as readable text or HTML, with caching, live refresh, and parallel job handling.317 npmMIT
TDQS
Scored across 2 tools
fetch_page retrieves page content while check_exit_ip is a pure diagnostic that reports the exit IP/geo; their purposes are unmistakably distinct despite sharing the optional country/session parameters. An agent would never confuse the two.
Both tools follow the same snake_case verb_noun convention (fetch_page, check_exit_ip), with verbs that accurately describe the action. No mixing of styles or vague names.
Two tools is on the thin side; fetch plus a single diagnostic leaves little room for related operations. The scope is coherent, but the surface is closer to a minimal wrapper than a well-rounded toolset.
The core operation (proxied page fetch) and the key verification step (exit IP check) are both present, covering the main workflow. Minor gaps exist: no non-GET requests, no session management (list/clear/expire), and the sticky-IP duration is fixed.