Novada Proxyofficial
A
licenseNot graded
qualityC
maintenanceEnables AI agents to route HTTP requests through millions of real residential IPs, bypassing anti-bot systems and geo-targeting by country or city.
4
MIT
quantumproxies-mcp
OfficialRelated Servers
Alternatives to quantumproxies-mcp
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityCmaintenanceRoutes AI agent HTTP requests through residential proxies to bypass anti-bot systems, geo-target by country/city, and maintain sticky sessions across multi-step workflows.6 npm1MIT
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- AlicenseAqualityDmaintenanceRoutes web requests through 175M+ residential IPs across 195+ countries, enabling AI to bypass geo-restrictions and anti-bot systems.431 npm1MIT
- AlicenseAqualityCmaintenanceProvides AI agents with access to a global residential proxy network covering over 190 countries for web fetching and scraping. It enables pay-per-request transactions using USDC on the Base network via the x402 protocol.366 npm2MIT
- AlicenseNot gradedqualityAmaintenanceEnables AI agents to navigate, interact with, search, extract from, download from, and reuse sessions across the web using anti-detection browser automation.971 npmMIT
TDQS
A3.9/5.0
Scored across 25 tools
Disambiguation3/5
Several tools share overlapping search/fetch behavior: search, search_bulk, search_and_read, run_collector, and create_dataset all involve searching the web, while scrape, batch, crawl, and search_and_read all fetch page content. Descriptions do differentiate them, but an agent could easily misselect between search, search_bulk, and search_and_read for a given task.
Naming Consistency4/5
Most tools follow a clear snake_case verb_noun pattern with predictable async pairs such as create_dataset/dataset_status, run_collector/collector_run_status, and crawl/crawl_status. Minor deviations like map, batch, seo_audit, and search_bulk break the pattern slightly but do not create serious confusion.
Tool Count3/5
At 25 tools, this sits right at the heavy end of the range; the size is justified by the broad domain covering proxies, search, scraping, collectors, datasets, and parser presets. Still, the five async status pollers and five parser-related tools make the surface feel larger and more burdensome than strictly necessary.
Completeness4/5
Core workflows are well covered: proxy listing/generation/locations/whitelisting, single and bulk scraping, search variants, collector execution, dataset creation, parser preset lifecycle, and SEO audit. Notable gaps include no way to delete parser presets, cancel async jobs, or list past datasets/jobs, but agents can work around these limitations in most scenarios.
Maintenance
ActivityMaintained
ResponsivenessNo issues