Skip to content
WeProxy logo

WeProxy MCP server

Which MCP servers are WeProxy's own, from the official registry and from asking its own domain, whether they answer, and what they offer. A program checked each of these, nobody copied them from a product page.

read 2026-10-31

← Back to WeProxy

Whose server it is
  • Registry nameio.weproxy/mcpverified in the MCP registry

The registry name sits under weproxy.io. The registry only lets a publisher use that namespace after proving control of the domain through DNS or HTTP.

When we asked itchecked 2026-10-31
  • Stateanswerschecked 2026-10-31
  • Tools7
  • Server calls itselfweproxy
  • Server version1.0.0
  • Protocol version2025-06-18

On 2026-10-31 the server answered initialize and tools/list without a sign-in. First answer in 254 ms.

Should an agent connect itSkip it
  • Its tools do none of the product's use cases we checked: collect search engine results for SEO rank tracking; verify how ads appear from different locations.
  • Checked on 3 of the 7 days it takes to judge reliability.

Once connected

  • Parameters are untyped or undescribed in 7 of 7 tools: check arguments before calling.

Said by rules from the measurements above. The likely first call is a model's pick from the tool list; read its description before relying on it.

Measured dailydaily checks: 3, the first on 2026-10-31
  • INITE MCP scoreafter a weeka score needs 7 daily checks: 3 so far
  • What an agent can do with it0 of 2 use cases
  • Answeredmeasuring3 of the 7 daily checks it takes to print a share
  • Median first answer638 ms
  • Space in an agent's context≈ 768 tokensthe definitions of all its tools (7), which an agent carries on every turn
  • Tool definitionsC · 67 of 100
  • Typed results0 of 7 toolsdeclared outputSchema: results come typed, read once
  • Parameters without a description: in 7 of 7
  • Not saying whether it only reads or can destroy: 7 of 7

What an agent can do with it

  • cannot · collect search engine results for SEO rank tracking
  • cannot · verify how ads appear from different locations
  • not sure · scrape public web data without getting blocked

Each of the product's use cases, put to Jev against this server's tool list: can an agent do it with these tools?

Worth a look

None of the five warning signs in these definitions.

A program checks the server once a day: initialize and tools/list, no model. Tokens are the definitions' length at about four characters a token. The grade averages six checks of every tool's name, description, schema and annotations; it says how well the tools are described, not whether they work. The score weighs what was measured and nothing else: answering (25%), doing the product's job (25%), definitions (20%), context (10%), use (10%) and how readily a client connects (10%). A part that was not measured is left out, and a hidden instruction caps the score at 40. The state of vendors' MCP servers: method and numbers →

Tools it offers7 tools · read 2026-10-31
  • recommend_proxy

    Pick a published WeProxy product for a job. Uses use-case product lists and the country registry. Does not invent prices or city pools.

  • list_products

    List published products that appear in the site catalog, with the same starting price the pricing page shows.

  • get_pricing

    Return package rows for one published product. Prices are formatted the same way as the site. Pass a country code to keep only that location.

  • check_location

    Say which published products cover a country. City inventory is not in the registry; a city name does not prove a pool.

  • diagnose_proxy_error

    Look up 407, 502, curl exit codes, browser tunnel errors, or SOCKS reply 0x01-0x08 in the published error guide. Send the code only, never a proxy URL, username, or password.

  • search_guides

    Search published blog posts and SEO landing titles in tr, en, ru, de, or vi.

  • start_free_trial

    Return the published 1 GB Premium Rotating Residential claim page and its order link. This tool does not describe any other signup credit.

How to connect

Add the server to your MCP client config. Claude Desktop, Cursor and most other clients read this shape:

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

Add it

Claude Code, in a terminal

claude mcp add --transport http weproxy https://weproxy.io/api/mcp

Add to CursorAdd to VS Code

claude.ai, ChatGPT and other clients: add https://weproxy.io/api/mcp as a custom connector in the settings.

Each line is something a program found when it went looking: the registry entry, the server's own answer, a spec that parses. A missing line means we did not find it, not that it does not exist.