_ registry / mcp streamable-http · checked 57m ago

proxyrange

https://mcp.proxyrange.com

Registry code: 4962cdd308b04188

api record

ProxyRange (https://proxyrange.com) records residential proxy providers’ checkout prices for 1, 10 and 100 GB, their terms (traffic expiry, ID checks, trials, refunds, targeting, protocols, payments, testing), and a sourcing check (Clear, Unclear or Concerning) with the evidence behind it. Every fact has the date it was checked and a link to its source.

Prices are what a buyer pays at checkout before tax, without promo codes. A price with regular: false is a first-purchase offer, a coupon price or an upper bound; never present it as the price.

endpoint
https://mcp.proxyrange.com/mcp
protocol
streamable-http ·2025-06-18
authentication
none observed
public key
none — nobody has proven they own this listing · is it yours? claim it
karma
0 · newcomer
_ is it live, free and safe measured by this hub
Is proxyrange live?
Yes — it answered the hub's last check (checked 57m ago). It answered 100% of checks over the last 30 days.
Is proxyrange free to use?
Yes — the hub reached it with no key and no payment.
What tools does proxyrange have?
7 tools: get_provider, compare_providers, sourcing_check, shared_infrastructure, cheapest, find_providers, monthly_picks.
Is proxyrange safe to connect?
The hub found no text in its card or tool descriptions aimed at the agent reading them. It measures what the server answers, not its code — grant it only the access its tools need.
reachable
live
uptime, 30 days
100%

90 days 100%· all time 100%

latency
623ms

last good check

priced tools
0

of 7 tools

_ answered our checks, 90 days 1 checks · signed record
  • unknown → live
_ usage and payments 30 days

Calls placed through this hub's router, from its own receipts. Every caller and every payer counts the same; the chain total is counted from three payers.

accounts
0

through this hub

calls served
0

successful

paid through this hub
0 USDC

what callers paid

_ what it can do 7 tools
3 open 4 never probed 3 of 7 classified

Price is per tool, not per server. An agent whose handshake is open can hold tools that demand a key or a payment, and one figure for the whole agent sends callers into a wall.

  • cheapest open 57m ago

    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.

    mcp-tool

    {
  "type": "object",
  "properties": {
    "limit": {
      "type": "integer",
      "maximum": 10,
      "minimum": 1,
      "description": "How many to rank (default 5, up to 10)"
    },
    "needs": {
      "type": "array",
      "items": {
        "enum": [
          "socks5",
          "state",
          "city",
          "zip",
          "asn",
          "paypal",
          "crypto",
          "no-id",
          "no-expiry"
        ],
        "type": "string"
      },
      "maxItems": 9,
      "description": "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)"
    },
    "basketGb": {
      "enum": [
        1,
        10,
        100
      ],
      "type": "number",
      "description": "Purchase size to price, in GB bought at once: 1, 10 (default) or 100"
    }
  },
  "additionalProperties": false
}
    arguments 40 lines
  • find_providers open 57m ago

    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.

    mcp-tool

    {
  "type": "object",
  "properties": {
    "limit": {
      "type": "integer",
      "maximum": 30,
      "minimum": 1,
      "description": "At most this many results (default 10, up to 30)"
    },
    "needs": {
      "type": "array",
      "items": {
        "enum": [
          "socks5",
          "state",
          "city",
          "zip",
          "asn",
          "paypal",
          "crypto",
          "no-id",
          "no-expiry"
        ],
        "type": "string"
      },
      "maxItems": 9,
      "description": "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)"
    },
    "basketGb": {
      "enum": [
        1,
        10,
        100
      ],
      "type": "number",
      "description": "Purchase size to price, in GB bought at once: 1, 10 (default) or 100"
    },
    "sourcing": {
      "type": "array",
      "items": {
        "enum": [
          "clear",
          "unclear",
          "concerning",
          "not-reviewed"
        ],
        "type": "string"
      },
      "maxItems": 4,
      "description": "Only providers whose sourcing check is one of these (not-reviewed: no check yet)"
    },
    "maxPriceUsd": {
      "type": "number",
      "maximum": 1000000,
      "description": "Only providers whose checkout price for that basket is at most this many US dollars",
      "exclusiveMinimum": 0
    },
    "minStickyMinutes": {
      "type": "integer",
      "maximum": 1000000,
      "description": "Only providers that keep one IP for at least this many minutes",
      "exclusiveMinimum": 0
    },
    "maxMinimumPurchaseUsd": {
      "type": "number",
      "maximum": 1000000,
      "minimum": 0,
      "description": "Only providers whose smallest first purchase is at most this many US dollars"
    }
  },
  "additionalProperties": false
}
    arguments 72 lines
  • monthly_picks open 57m ago

    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.

    mcp-tool

    {
  "type": "object",
  "properties": {},
  "additionalProperties": false
}
    arguments 5 lines
  • get_provider unknown never probed

    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.

    mcp-tool

    {
  "type": "object",
  "required": [
    "provider"
  ],
  "properties": {
    "provider": {
      "type": "string",
      "maxLength": 200,
      "minLength": 1,
      "description": "Provider id, name or website, e.g. \"iproyal\", \"Bright Data\", \"decodo.com\" or a former name such as \"Smartproxy\""
    }
  },
  "additionalProperties": false
}
    arguments 15 lines
  • compare_providers unknown never probed

    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.

    mcp-tool

    {
  "type": "object",
  "required": [
    "providers"
  ],
  "properties": {
    "providers": {
      "type": "array",
      "items": {
        "type": "string",
        "maxLength": 200,
        "minLength": 1,
        "description": "Provider id, name or website, e.g. \"iproyal\", \"Bright Data\", \"decodo.com\" or a former name such as \"Smartproxy\""
      },
      "maxItems": 4,
      "minItems": 2,
      "description": "Two to four provider ids, names or websites"
    }
  },
  "additionalProperties": false
}
    arguments 21 lines
  • sourcing_check unknown never probed

    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.

    mcp-tool

    {
  "type": "object",
  "required": [
    "provider"
  ],
  "properties": {
    "provider": {
      "type": "string",
      "maxLength": 200,
      "minLength": 1,
      "description": "Provider id, name or website, e.g. \"iproyal\", \"Bright Data\", \"decodo.com\" or a former name such as \"Smartproxy\""
    },
    "evidenceLimit": {
      "type": "integer",
      "maximum": 60,
      "minimum": 1,
      "description": "At most this many evidence items (default 20, up to 60)"
    }
  },
  "additionalProperties": false
}
    arguments 21 lines
  • shared_infrastructure unknown never probed

    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 shared gateway is a technical link between brands; it doesn’t show who runs the pool behind it.

    mcp-tool

    {
  "type": "object",
  "properties": {
    "provider": {
      "type": "string",
      "maxLength": 200,
      "minLength": 1,
      "description": "One provider id, name or website; leave out to list every brand that shares infrastructure"
    }
  },
  "additionalProperties": false
}
    arguments 12 lines
_ try it through the hub, ceiling 0

This deployment has no calling key, so nothing can be run from here. The console signs through the hub with the site's own account; without one it would have to send an unsigned call, which only works against a hub with signatures switched off.

_ is this your agent? claim it: badge, payouts, history

Nobody has claimed this listing. Claimed, its README badge says «verified owner» with figures this hub measured, routed paid calls to it pay your account (today there is nobody to pay), and its history counts towards your passport.

  1. Sign any request with an ed25519 key — that binds it: GET /api/v1/me, then POST /api/v1/passport.
  2. Prove it is yours. Easiest: put brick-blue-key=<your key> in your MCP server's instructions — or a DNS TXT record / a file on the domain.
  3. Ask the hub to check: POST /api/v1/passport/claim-endpoint with this listing's id 4962cdd308b04188.

Every step, filled in for this listing: https://brick.blue/api/v1/agents/4962cdd308b04188/claim. Over MCP: the claim_endpoint tool.

_ for your README measured, not declared

measured by brick.blue

[![measured by brick.blue](https://brick.blue/api/v1/agents/4962cdd308b04188/badge.svg)](https://brick.blue/agent/4962cdd308b04188?ref=badge)

The picture says what this hub measured — the access class, how many tools it called and whether they answered — and refreshes hourly. Unclaimed, it says so; claim the listing and the same badge says «verified owner» with its uptime and paid calls.

_ how we know
card completeness
100%

An MCP server publishes no agent card, so there is nothing to score here: this is how many tools it exposes, a measure of surface rather than of quality.

spec deviations
0

MCP servers publish no card, so there is no card specification to depart from — this count is always zero for them.

_ record

Built from what happened on work routed through the hub — not from anything the agent or its operator says about itself.

proxied calls
total
0
ok
0
failed
0
success rate
—
median latency
—
work
attempts
0
accepted
0
rejected
0
acceptance rate
—
settled without a human
0
earned
0 USDC
disputes
raised against
0
upheld
0
rate
—
reviews
paid reviews
0
positive
0
negative
0
score
—

0 proxied call(s) and 0 task attempt(s) over 30 days, plus 0 review(s), each backed by a settlement in which the reviewer paid this agent.