coronium-proxy-mcp
OfficialRelated Servers
Alternatives to coronium-proxy-mcp
No user-submitted related servers found.
Related Servers
- AlicenseAqualityCmaintenanceEnables AI agents to autonomously buy and operate mobile proxies via MCP, supporting both API key and on-chain USDC payments for tasks like port creation, IP rotation, and traffic management.44210 npmMIT

2extract MCP Serverofficial
AlicenseNot gradedqualityBmaintenanceEnables AI agents to create and manage residential and mobile proxies with granular geo-targeting, traffic and spend limits, access restrictions, and usage/cost reporting.1MIT- AlicenseAqualityAmaintenanceMCP server that gives Claude and other agents direct control over mobile proxies, enabling proxy management and rotation tasks.2838 npmMIT
- 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.115 npm-
- AlicenseNot gradedqualityAmaintenanceConnects MCP-compatible AI agents to an anti-detection browser server so they can navigate, interact with, and extract content from web pages without getting blocked. Provides 47 tools spanning tabs, navigation, interaction, observation, search, sessions, profiles, downloads, extraction, presets, and batch workflows.201 npmMIT
- AlicenseNot gradedqualityAmaintenanceConnects MCP-compatible AI agents to an anti-detection browser backend, enabling web navigation, interaction, search, extraction, downloads, and session reuse across multi-tab workflows.201 npmMIT
TDQS
Scored across 48 tools
Most tools have clearly distinct purposes, but a few pairs like restart_modem vs rotate_modem and list_pool_sessions vs list_pool_keys could be confused without reading descriptions. The consistent resource-oriented naming helps overall, but the large number of overlapping lifecycle actions creates minor ambiguity.
All tools follow a strict coronium_<verb>_<noun> pattern, with predictable verbs like list, get, set, create, cancel, and buy. This consistency makes it easy to guess tool behavior and reduces cognitive load despite the large count.
At 48 tools, this server is far beyond the typical well-scoped count of 3-15, and even exceeds the 25+ threshold for 'too many.' While the API serves a broad domain, the sheer number of tools imposes a heavy selection burden on agents and suggests the surface could be consolidated or split into separate servers.
The tool set covers the full lifecycle for modems, proxies, pool keys, account management, payments, webhooks, and support tickets. Operations like buy, renew, cancel, rotate, test, replace, and health checks are all present, with no obvious missing features or dead ends.