Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

WeProxy

REMOTE · WEPROXY.IO

Turkey-focused proxy catalog: product picker, pricing, country coverage, error diagnosis. No key.

Available components

62 Trust /100

Last scanned (5 hours ago)

Scores higher than 44% of remote servers

Reachable. Last reached 5 Nov 2026.

Category Cloud Infrastructure

Trust breakdown (7 categories)

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 Security57
Transport & Reachability100
Schema Quality & AI Usability62
  • AI-judged instruction clarity (fair).Partial
  • Tool/resource definitions use about 439 tokens (~62/item across 7 items; 7 tools + 0 resources), lean.Pass
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management17
  • Stability observed for 5 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage67
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 0% of tool parameters carry a description.Fail
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
Changelog

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 13 to 17. That category is still filling its 30-day observation window: 4 days of observed history at the previous scan, 5 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 7 to 10. That category is still filling its 30-day observation window: 2 days of observed history at the previous scan, 3 at this one. The score rises as the window fills, whether or not the server changes.

  • 1 Nov 26 +1
    • Stability: unverified → 0.03 ▲ functional
  • 31 Oct 26 59

    First indexed and scored.

Diagnostics

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://weproxy.io/api/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=weproxy.io CN=WE1,O=Google Trust Services,C=US 26 Oct 2026 24 Jan 2027 ECDSA 256 ECDSA-SHA256 6273f4006d125fa20e60d31a337b94e9
SANs: weproxy.io, *.weproxy.io
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 weproxy.io. — Not signed

Zone DS Keys Algorithms Outcome
. trust_anchor 20326, 38696 8, 8 Verified
io. present 38690 8 Verified
weproxy.io. 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
x-frame-options SAMEORIGIN
referrer-policy same-origin

Background: How OAuth 2.1 works in the 2026 MCP spec →

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://weproxy.io/api/mcp Verified 200
http (plaintext) http://weproxy.io/api/mcp HTTPS enforced 301 https://weproxy.io/api/mcp
MCP tools · 7 exposed · ~378 tokens

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 →

Tool Tokens
check_location ~54

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

NameTypeReqDescription
citystring––
countrystring––
localestring––

No output schema declared.

No examples provided.

diagnose_proxy_error ~72

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.

NameTypeReqDescription
codestringyes–
localestring––

No output schema declared.

No examples provided.

get_pricing ~58

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.

NameTypeReqDescription
countrystring––
localestring––
slugstringyes–

No output schema declared.

No examples provided.

list_products ~35

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

NameTypeReqDescription
localestring––

No output schema declared.

No examples provided.

recommend_proxy ~73

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

NameTypeReqDescription
countrystring––
estimatedTrafficGbnumber––
localestring––
protocolstring––
purposestringyes–

No output schema declared.

No examples provided.

search_guides ~43

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

NameTypeReqDescription
localestring––
querystringyes–

No output schema declared.

No examples provided.

start_free_trial ~43

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

NameTypeReqDescription
localestring––

No output schema declared.

No examples provided.

Install

How do I install the WeProxy MCP server?

WeProxy is a hosted endpoint at https://weproxy.io/api/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 · weproxy.io

# add to Claude Code
claude mcp add --transport http io-weproxy-mcp 'https://weproxy.io/api/mcp'
Common questions

What is the WeProxy MCP server?

WeProxy is an MCP server listed in the public MCP registry as io.weproxy/mcp. Turkey-focused proxy catalog: product picker, pricing, country coverage, error diagnosis. No key. This page covers its hosted endpoint (https://weproxy.io/api/mcp).

Is the WeProxy MCP server safe to use?

WeProxy scores 62 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 WeProxy MCP server expose?

WeProxy exposes 7 tools: recommend_proxy, list_products, get_pricing, check_location, diagnose_proxy_error, and 2 more. Their descriptions and schemas cost roughly 378 tokens of context every time the server is loaded.

Does the WeProxy MCP server require authentication?

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

Is the WeProxy MCP server still maintained?

WeProxy 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.