Skip to main content
Glama
quantumproxies

quantumproxies-mcp

Official
by quantumproxies
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Related Servers

Alternatives to quantumproxies-mcp

No user-submitted related servers found.

    Related Servers

    • Proxy4Agent

      Goldentrii
      A
      license
      Not graded
      quality
      C
      maintenance
      Routes 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.
      17 npm
      1
      MIT

    • Apollo Proxy MCP Server

      bnmbnmai
      A
      license
      A
      quality
      D
      maintenance
      Provides 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.
      3
      65 npm
      2
      MIT

    • Firecrawl-Compatible Stealth

      Ansarii
      A
      license
      Not graded
      quality
      C
      maintenance
      Provides a drop-in replacement for Firecrawl's core tools, enabling AI agents to scrape, crawl, and map websites with resilient TLS fingerprinting and pay-per-success billing, while avoiding edge bot filters and blocked-request charges.
      MIT

    • klawfetch

      novalis78
      A
      license
      Not graded
      quality
      D
      maintenance
      A geo-distributed HTTP proxy for AI agents, enabling web fetching from multiple global regions (Frankfurt, Sydney, New York, San Francisco) with support for screenshots, scraping, and JS rendering.
      MIT
    Deploy Server
    One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

    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

    Resources