# ProxyRange (remote · mcp.proxyrange.com)

Residential proxy checkout prices, terms and sourcing checks, every fact dated and sourced.

- Trust score: 73/100 (medium)
- Change this week: +4
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-05

## Components

- remote · `mcp.proxyrange.com`: 73/100 (this document), [markdown](https://verifymcp.io/servers/com-proxyrange-proxyrange/mcp.md), [page](https://verifymcp.io/servers/com-proxyrange-proxyrange/mcp)

## Channel facts

- Endpoint: `https://mcp.proxyrange.com/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `1.0.1`

## Trust breakdown

How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-11-05.

- **Endpoint Security**: 74/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one.
  - HTTPS is enforced; there's no plaintext access path.
  - HSTS check failed: the Strict-Transport-Security header is absent.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 63/100
  - AI-judged instruction clarity (good).
  - Context-footprint check failed: tool/resource definitions use about 1410 tokens (~201/item across 7 items; 7 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 27/100
  - Stability observed for 8 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
  - Structured output schemas are declared (100% of tools); any adoption earns full credit.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 7 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 8 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a current MCP spec version (2026-07-28).

## Install

### How do I install the ProxyRange MCP server?

ProxyRange is a hosted endpoint at https://mcp.proxyrange.com/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

### Claude

```bash
claude mcp add --transport http com-proxyrange-proxyrange 'https://mcp.proxyrange.com/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "com-proxyrange-proxyrange": {
      "url": "https://mcp.proxyrange.com/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "com-proxyrange-proxyrange": {
      "type": "http",
      "url": "https://mcp.proxyrange.com/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.com-proxyrange-proxyrange]
url = "https://mcp.proxyrange.com/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "com-proxyrange-proxyrange": {
      "type": "remote",
      "url": "https://mcp.proxyrange.com/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add com-proxyrange-proxyrange --url 'https://mcp.proxyrange.com/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  com-proxyrange-proxyrange:
    url: "https://mcp.proxyrange.com/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "com-proxyrange-proxyrange": {
      "Transport": "http",
      "Url": "https://mcp.proxyrange.com/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add com-proxyrange-proxyrange -t streamable-http -u 'https://mcp.proxyrange.com/mcp'
```

### Other

```json
{
  "mcpServers": {
    "com-proxyrange-proxyrange": {
      "type": "http",
      "url": "https://mcp.proxyrange.com/mcp"
    }
  }
}
```

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-11-05 (score 73, +1)

No change was recorded against any check on this day. Stability & Change Management went from 23 to 27. That category is still filling its 30-day observation window: 7 days of observed history at the previous scan, 8 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-11-03 (score 72, +1)

No change was recorded against any check on this day. Stability & Change Management went from 17 to 20. That category is still filling its 30-day observation window: 5 days of observed history at the previous scan, 6 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-11-01 (score 71, +1)

No change was recorded against any check on this day. Stability & Change Management went from 10 to 13. That category is still filling its 30-day observation window: 3 days of observed history at the previous scan, 4 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-10-30 (score 70, +1)

No change was recorded against any check on this day. Stability & Change Management went from 3 to 7. That category is still filling its 30-day observation window: 1 days of observed history at the previous scan, 2 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-10-29 (score 69, 0)

- [functional improvement] Stability: unverified → 0.03

### 2026-10-28 (score 69)

First indexed and scored.

## MCP tools (7)

### `find_providers` (~314 tokens)

Find residential proxy providers

Residential proxy providers that meet a buyer’s requirements (SOCKS5, city/ZIP/ASN targeting, PayPal or crypto, no ID check, traffic that never expires, a price cap, a sourcing check level, a smallest first purchase, a session length), with each one’s checkout price for 1, 10 or 100 GB. Regular prices come first, lowest first; first-purchase offers and upper bounds follow, flagged. Every result links to its proxyrange.com page and says when its prices were checked.

Input parameters:

- `basketGb` (number): Purchase size to price, in GB bought at once: 1, 10 (default) or 100
- `limit` (integer): At most this many results (default 10, up to 30)
- `maxMinimumPurchaseUsd` (number): Only providers whose smallest first purchase is at most this many US dollars
- `maxPriceUsd` (number): Only providers whose checkout price for that basket is at most this many US dollars
- `minStickyMinutes` (integer): Only providers that keep one IP for at least this many minutes
- `needs` (array): Requirements every result must meet: socks5; state, city, zip or asn (finest targeting); paypal or crypto (payment); no-id (no ID check to sign up and buy); no-expiry (unused traffic never expires)
- `sourcing` (array): Only providers whose sourcing check is one of these (not-reviewed: no check yet)

Output parameters:

- `attribution` (string): How to credit the data when you show it
- `basketGb` (number)
- `licence` (string)
- `matched` (integer): How many providers meet every requirement
- `medianUsd` (number|null): The market median of regular checkout prices for this basket
- `order` (string)
- `providers` (array)
- `shown` (integer)
- `updated` (string): The newest date any fact in the data was checked (YYYY-MM-DD)

### `cheapest` (~182 tokens)

Cheapest residential proxies

The lowest regular checkout prices for 1, 10 or 100 GB of residential proxy traffic, ranked the way proxyrange.com ranks them: first-purchase offers, coupons and upper bounds never count, and providers whose sourcing check is Concerning are left out. Optionally only providers meeting given requirements. Includes the market median for the basket.

Input parameters:

- `basketGb` (number): Purchase size to price, in GB bought at once: 1, 10 (default) or 100
- `limit` (integer): How many to rank (default 5, up to 10)
- `needs` (array): Requirements every result must meet: socks5; state, city, zip or asn (finest targeting); paypal or crypto (payment); no-id (no ID check to sign up and buy); no-expiry (unused traffic never expires)

Output parameters:

- `attribution` (string): How to credit the data when you show it
- `basketGb` (number)
- `leftOut` (object)
- `licence` (string)
- `medianUsd` (number|null)
- `ranking` (array)
- `rule` (string)
- `updated` (string): The newest date any fact in the data was checked (YYYY-MM-DD)

### `get_provider` (~156 tokens)

Residential proxy provider facts and review

Everything ProxyRange has on one residential proxy provider: checkout prices for 1, 10 and 100 GB, the smallest first purchase, whether unused traffic expires, ID check, trial, refunds, protocols, targeting, longest sticky session, claimed pool size, payment methods, what its terms say about independent testing, its sourcing check (Clear, Unclear or Concerning), brands it shares infrastructure with, and our review (best for, think twice if, pros, cons). Every fact carries the date it was checked and its source.

Input parameters:

- `provider` (string, required): Provider id, name or website, e.g. "iproyal", "Bright Data", "decodo.com" or a former name such as "Smartproxy"

Output parameters:

- `attribution` (string): How to credit the data when you show it
- `formerly` (string|null)
- `id` (string)
- `idCheck` (object)
- `licence` (string)
- `marketMedianUsd` (array)
- `minimumPurchaseUsd` (object)
- `name` (string)
- `needsMet` (array)
- `notStated` (string)
- `page` (string): Its page on proxyrange.com: cite this
- `payments` (object)
- `poolClaimed` (object)
- `prices` (object)
- `protocols` (object)
- `refunds` (object)
- `review`
- `sharesInfrastructureWith` (array)
- `sourcingCheck`: null: not yet reviewed
- `stickySessionMaxMinutes` (object)
- `targeting` (object)
- `testing` (object)
- `trafficExpires` (object)
- `trial` (object)
- `updated` (string): The newest date any fact in the data was checked (YYYY-MM-DD)
- `website` (string)

### `compare_providers` (~101 tokens)

Compare residential proxy providers

Two to four residential proxy providers side by side: checkout prices for 1, 10 and 100 GB with which one is cheaper at each (regular prices only), smallest first purchase, traffic expiry, ID check, trial, refunds, protocols, targeting, sticky sessions, payments, testing terms, sourcing checks, our best-for lines, and whether any of them share infrastructure.

Input parameters:

- `providers` (array, required): Two to four provider ids, names or websites

Output parameters:

- `attribution` (string): How to credit the data when you show it
- `cheaperAt` (array)
- `licence` (string)
- `notStated` (string)
- `providers` (array)
- `sharedInfrastructure` (array)
- `sharedNote` (string)
- `updated` (string): The newest date any fact in the data was checked (YYYY-MM-DD)

### `monthly_picks` (~85 tokens)

This month’s residential proxy picks

ProxyRange’s picks for this month, one per need (lowest price, smallest first purchase, no ID to start, traffic never expires, city targeting, SOCKS5, PayPal, crypto, longest sessions, open to testing, Clear sourcing check), with each pick’s regular 10 GB price and the market medians for 1, 10 and 100 GB.

Output parameters:

- `attribution` (string): How to credit the data when you show it
- `licence` (string)
- `medians` (array)
- `month` (string)
- `page` (string)
- `picks` (array)
- `rule` (string)
- `updated` (string): The newest date any fact in the data was checked (YYYY-MM-DD)

### `sourcing_check` (~154 tokens)

Where a provider’s IPs come from

ProxyRange’s sourcing check for one residential proxy provider: Clear, Unclear or Concerning, with its confidence, the reasons behind it, and the evidence items (what each source says, a link to it, and when we saw it), plus the provider’s reply if it sent one. Residential proxies route traffic through other people’s devices, so this is what we could establish about how those devices were enrolled.

Input parameters:

- `evidenceLimit` (integer): At most this many evidence items (default 20, up to 60)
- `provider` (string, required): Provider id, name or website, e.g. "iproyal", "Bright Data", "decodo.com" or a former name such as "Smartproxy"

Output parameters:

- `attribution` (string): How to credit the data when you show it
- `checked`
- `confidence` (string|null)
- `corrections` (string)
- `evidence` (array)
- `evidenceTotal` (integer)
- `howToRead` (string)
- `id` (string)
- `level`: null: not yet reviewed
- `licence` (string)
- `meaning` (string)
- `method` (string)
- `name` (string)
- `page` (string)
- `reasons` (array)
- `reply`
- `rightOfReply` (string)
- `updated` (string): The newest date any fact in the data was checked (YYYY-MM-DD)

### `shared_infrastructure` (~99 tokens)

Residential proxy brands that share infrastructure

Which residential proxy brands share infrastructure (their proxy gateways answer from the same addresses or resolve through the same DNS target), for one provider or for every brand ProxyRange covers. A gateway that is an alias of another brand’s host goes through that host; shared addresses alone are a technical link that doesn’t show who runs the network.

Input parameters:

- `provider` (string): One provider id, name or website; leave out to list every brand that shares infrastructure

Output parameters:

- `attribution` (string): How to credit the data when you show it
- `brands` (array)
- `corrections` (string)
- `howToRead` (string)
- `licence` (string)
- `note` (string)
- `rightOfReply` (string)
- `updated` (string): The newest date any fact in the data was checked (YYYY-MM-DD)

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/com-proxyrange-proxyrange/mcp#diagnostics

## Score history

- 2026-11-05: 73
- 2026-11-04: 72
- 2026-11-03: 72
- 2026-11-02: 71
- 2026-11-01: 71
- 2026-10-31: 70
- 2026-10-30: 70
- 2026-10-29: 69
- 2026-10-28: 69

## Common questions

### What is the ProxyRange MCP server?

ProxyRange is an MCP server listed in the public MCP registry as com.proxyrange/proxyrange. Residential proxy checkout prices, terms and sourcing checks, every fact dated and sourced. This page covers its hosted endpoint (https://mcp.proxyrange.com/mcp).

### Is the ProxyRange MCP server safe to use?

ProxyRange scores 73 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

### What tools does the ProxyRange MCP server expose?

ProxyRange exposes 7 tools: find_providers, cheapest, get_provider, compare_providers, monthly_picks, and 2 more. Their descriptions and schemas cost roughly 1,091 tokens of context every time the server is loaded.

### Does the ProxyRange MCP server require authentication?

No. We connected to ProxyRange without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

### Is the ProxyRange MCP server still maintained?

ProxyRange is still listed as active in the MCP registry. We last reached this channel on 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

## Links

- Remote endpoint: https://mcp.proxyrange.com/mcp
- Repository: https://github.com/ProxyRange/proxyrange-mcp
- Website: https://proxyrange.com/mcp
- Changelog RSS feed: https://verifymcp.io/servers/com-proxyrange-proxyrange/mcp.xml
- Changelog JSON feed: https://verifymcp.io/servers/com-proxyrange-proxyrange/mcp.json
- HTML version of this page: https://verifymcp.io/servers/com-proxyrange-proxyrange/mcp