Quantumproxies Mcp

io.github.quantumproxiesPublished by GitHub account quantumproxiesv0.11.4Updated Oct 27, 2026

Web scraping, SERP search, crawl/map and 74 Collectors through residential proxies. 25 tools.

VerifiedStreamable HTTPWeb executableWeb Search & Scraping

Overview

AI-generated overview

QuantumProxies MCP gives an assistant web scraping, SERP search, crawl/map and 74 Collectors routed through residential proxies, via 25 tools.

What you can do
  • Run search engine results (SERP) queries through residential proxies
  • Scrape web pages and crawl or map sites
  • Use 74 Collectors to gather structured data from supported sources
  • Connect over a remote endpoint or a local npm package
When to use it
Useful when an assistant needs live web data at scale and the user already has or wants a QuantumProxies.io account, for example SERP lookups, page scraping, or site crawling and mapping.
Requirements
A QuantumProxies.io account and API key, supplied as QUANTUMPROXIES_API_KEY or as an Authorization bearer header; MCP OAuth sign-in is also supported. Runs as a remote endpoint at api.quantumproxies.io or as the local npm package quantumproxies-mcp over stdio. Network access required.
Before you install
The API key is a secret and grants access to the account's proxy usage; free monthly usage is mentioned, but usage beyond it may be billed, so check the plan. Scraping and crawling send target URLs to a third-party proxy service, and requests may be subject to the target sites' terms.

Installation

In SourceWeft

  1. Open Quantumproxies Mcp in the dashboard and add it to a workspace.
  2. Connect the required credentials. They are stored privately and never shown on public pages.
  3. Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/io.github.quantumproxies%2Fquantumproxies-mcp/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config. The client completes OAuth sign-in on first connect.

{
  "mcpServers": {
    "quantumproxies": {
      "type": "http",
      "url": "https://api.quantumproxies.io/mcp"
    }
  }
}

Tools

0
This server asks you to sign in, so SourceWeft could not read its tools without an account and has not indexed them. What a connected account sees can depend on that account and its permissions.

Version history

2
  1. v0.11.4LatestOct 2, 2026
  2. v0.8.1Sep 16, 2026

Score

60% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 daysRequired25 pts
  • Auth declaredRequired10 pts
  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts

    Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.

  • License10 pts

    Declare a license in the repository or the registry entry.