MCProxy
Related Servers
Alternatives to MCProxy
No user-submitted related servers found.
Related Servers
AlicenseAqualityDmaintenanceAn MCP server enabling AI agents to drive a real browser through residential proxies with per-task geo (country/city) and sticky identity, all chosen at call time.1066 npm4MIT- AlicenseAqualityDmaintenanceMCP server that lets AI agents route web requests through NodeMaven residential and mobile proxies, with tools for geo-targeted fetching, proxy checking, and location/usage queries.5MIT
- AlicenseNot gradedqualityDmaintenanceMCP server giving AI agents controlled residential-proxy web access with optional browser rendering and structured extraction from 60+ sites.1MIT
- AlicenseNot gradedqualityCmaintenanceA unified MCP server providing AI agents with 40+ developer APIs including geolocation, crypto prices, DNS lookup, and web scraping. Enables natural language access to various tools through a single gateway.1MIT
- AlicenseNot gradedqualityDmaintenanceA proxy server that unifies multiple MCP servers, enabling seamless tool, prompt, and resource management via the MetaMCP App.124 npm154Apache 2.0
- FlicenseAqualityDmaintenanceMCP server that wraps the Proxyline proxy provider API, exposing all methods as MCP tools for AI assistants. Enables managing proxies, orders, countries, IPs, balance, and tags through natural language.11-
TDQS
Scored across 11 tools
Most tools target distinct actions (list, generate, buy, extend), but `acquire_proxy` overlaps somewhat with `get_proxies` and `generate_proxy_list`, and `check_balance` vs `get_usage` could be confusing without careful reading. Descriptions mostly clarify the intended use cases.
All tool names follow a consistent verb_noun pattern (list_providers, get_proxies, generate_proxy_list, buy_proxies, etc.) with snake_case throughout. Even `scrape` and `acquire_proxy` fit the verb-first style.
11 tools is well-scoped for a proxy management server. Each tool addresses a distinct need: provider discovery, proxy listing/generation, account checks, purchasing, and usage. No redundancy or bloat.
The surface covers the core proxy lifecycle: view providers, generate/list proxies, buy/extend them, and monitor balance/usage. Missing are configuration tools (e.g., to set up providers) and a deletion option, but these are minor gaps that agents can work around.