ProxyRange
REMOTE · MCP.PROXYRANGE.COM
Residential proxy checkout prices, terms and sourcing checks, every fact dated and sourced.
Available components
Last scanned (8 hours ago)
Scores higher than 60% of remote servers
Reachable. Last reached 5 Nov 2026.
Category Security
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. How we score → Why this is hard to score →
Endpoint Security74
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one. See how to fix → View diagnostics → Partial
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability63
- AI-judged instruction clarity (good).Pass
- 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. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management27
- Stability observed for 8 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
- Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 7 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 8 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a current MCP spec version (2026-07-28).Pass
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 5 Nov 26 +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.
- 3 Nov 26 +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.
- 1 Nov 26 +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.
- 30 Oct 26 +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.
- 29 Oct 26 0
- Stability: unverified → 0.03 ▲ functional
- 28 Oct 26 69
First indexed and scored.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 5 Nov 2026 · Probed https://mcp.proxyrange.com/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=proxyrange.com | CN=WE1,O=Google Trust Services,C=US | 28 Oct 2026 | 26 Jan 2027 | ECDSA 256 | ECDSA-SHA256 | 8bda75950a7354370e3208a5f201d165 |
| SANs: proxyrange.com, mcp.proxyrange.com, *.mcp.proxyrange.com | ||||||
| CN=WE1,O=Google Trust Services,C=US (CA) | CN=GTS Root R4,O=Google Trust Services LLC,C=US | 13 Dec 2023 | 20 Feb 2029 | ECDSA 256 | ECDSA-SHA384 | 7ff31977972c224a76155d13b6d685e3 |
| CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) | CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE | 15 Nov 2023 | 28 Jan 2028 | ECDSA 384 | SHA256-RSA | 7fe530bf331343bedd821610493d8a1b |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of mcp.proxyrange.com. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| com. | present | 19718 | 13 | Verified |
| proxyrange.com. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
| Header | Value |
|---|---|
| x-content-type-options | nosniff |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://mcp.proxyrange.com/mcp | Verified | 200 | |
| http (plaintext) | http://mcp.proxyrange.com/mcp | HTTPS enforced | 301 | https://mcp.proxyrange.com/mcp |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
cheapest Cheapest residential proxies ~182
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.
| Name | Type | Req | Description |
|---|---|---|---|
| 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) |
| Name | Type | Req | Description |
|---|---|---|---|
| attribution | string | yes | How to credit the data when you show it |
| basketGb | number | yes | – |
| leftOut | object | yes | – |
| licence | string | yes | – |
| medianUsd | number|null | yes | – |
| ranking | array | yes | – |
| rule | string | yes | – |
| updated | string | yes | The newest date any fact in the data was checked (YYYY-MM-DD) |
No examples provided.
compare_providers Compare residential proxy providers ~101
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.
| Name | Type | Req | Description |
|---|---|---|---|
| providers | array | yes | Two to four provider ids, names or websites |
| Name | Type | Req | Description |
|---|---|---|---|
| attribution | string | yes | How to credit the data when you show it |
| cheaperAt | array | yes | – |
| licence | string | yes | – |
| notStated | string | yes | – |
| providers | array | yes | – |
| sharedInfrastructure | array | yes | – |
| sharedNote | string | yes | – |
| updated | string | yes | The newest date any fact in the data was checked (YYYY-MM-DD) |
No examples provided.
find_providers Find residential proxy providers ~314
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.
| Name | Type | Req | Description |
|---|---|---|---|
| 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) |
| Name | Type | Req | Description |
|---|---|---|---|
| attribution | string | yes | How to credit the data when you show it |
| basketGb | number | yes | – |
| licence | string | yes | – |
| matched | integer | yes | How many providers meet every requirement |
| medianUsd | number|null | yes | The market median of regular checkout prices for this basket |
| order | string | yes | – |
| providers | array | yes | – |
| shown | integer | yes | – |
| updated | string | yes | The newest date any fact in the data was checked (YYYY-MM-DD) |
No examples provided.
get_provider Residential proxy provider facts and review ~156
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.
| Name | Type | Req | Description |
|---|---|---|---|
| provider | string | yes | Provider id, name or website, e.g. "iproyal", "Bright Data", "decodo.com" or a former name such as "Smartproxy" |
| Name | Type | Req | Description |
|---|---|---|---|
| attribution | string | yes | How to credit the data when you show it |
| formerly | string|null | yes | – |
| id | string | yes | – |
| idCheck | object | yes | – |
| licence | string | yes | – |
| marketMedianUsd | array | yes | – |
| minimumPurchaseUsd | object | yes | – |
| name | string | yes | – |
| needsMet | array | yes | – |
| notStated | string | yes | – |
| page | string | yes | Its page on proxyrange.com: cite this |
| payments | object | yes | – |
| poolClaimed | object | yes | – |
| prices | object | yes | – |
| protocols | object | yes | – |
| refunds | object | yes | – |
| review | – | yes | – |
| sharesInfrastructureWith | array | yes | – |
| sourcingCheck | – | yes | null: not yet reviewed |
| stickySessionMaxMinutes | object | yes | – |
| targeting | object | yes | – |
| testing | object | yes | – |
| trafficExpires | object | yes | – |
| trial | object | yes | – |
| updated | string | yes | The newest date any fact in the data was checked (YYYY-MM-DD) |
| website | string | yes | – |
No examples provided.
monthly_picks This month’s residential proxy picks ~85
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.
Input schema present but exposes no named parameters.
| Name | Type | Req | Description |
|---|---|---|---|
| attribution | string | yes | How to credit the data when you show it |
| licence | string | yes | – |
| medians | array | yes | – |
| month | string | yes | – |
| page | string | yes | – |
| picks | array | yes | – |
| rule | string | yes | – |
| updated | string | yes | The newest date any fact in the data was checked (YYYY-MM-DD) |
No examples provided.
shared_infrastructure Residential proxy brands that share infrastructure ~99
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.
| Name | Type | Req | Description |
|---|---|---|---|
| provider | string | – | One provider id, name or website; leave out to list every brand that shares infrastructure |
| Name | Type | Req | Description |
|---|---|---|---|
| attribution | string | yes | How to credit the data when you show it |
| brands | array | yes | – |
| corrections | string | yes | – |
| howToRead | string | yes | – |
| licence | string | yes | – |
| note | string | yes | – |
| rightOfReply | string | yes | – |
| updated | string | yes | The newest date any fact in the data was checked (YYYY-MM-DD) |
No examples provided.
sourcing_check Where a provider’s IPs come from ~154
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.
| Name | Type | Req | Description |
|---|---|---|---|
| evidenceLimit | integer | – | At most this many evidence items (default 20, up to 60) |
| provider | string | yes | Provider id, name or website, e.g. "iproyal", "Bright Data", "decodo.com" or a former name such as "Smartproxy" |
| Name | Type | Req | Description |
|---|---|---|---|
| attribution | string | yes | How to credit the data when you show it |
| checked | – | yes | – |
| confidence | string|null | yes | – |
| corrections | string | yes | – |
| evidence | array | yes | – |
| evidenceTotal | integer | yes | – |
| howToRead | string | yes | – |
| id | string | yes | – |
| level | – | yes | null: not yet reviewed |
| licence | string | yes | – |
| meaning | string | yes | – |
| method | string | yes | – |
| name | string | yes | – |
| page | string | yes | – |
| reasons | array | yes | – |
| reply | – | yes | – |
| rightOfReply | string | yes | – |
| updated | string | yes | The newest date any fact in the data was checked (YYYY-MM-DD) |
No examples provided.
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.
remote · mcp.proxyrange.com
claude mcp add --transport http com-proxyrange-proxyrange 'https://mcp.proxyrange.com/mcp'
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.