_ registry / mcp http-sse · checked 56m ago

weproxy

https://weproxy.io

Registry code: b7c1bfc25301d482

api record

WeProxy public catalog. Prices and country coverage come from the site registry. Do not invent prices, stock, or a city pool. start_free_trial returns only the published 1 GB Premium Rotating Residential claim. diagnose_proxy_error accepts an error code, not a proxy URL or password.

endpoint
https://weproxy.io/api/mcp
protocol
http-sse ·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 weproxy live?
Yes — it answered the hub's last check (checked 56m ago). It answered 100% of checks over the last 30 days.
Is weproxy free to use?
Yes — the hub reached it with no key and no payment.
What tools does weproxy have?
7 tools: get_pricing, start_free_trial, recommend_proxy, diagnose_proxy_error, search_guides, list_products, check_location.
Is weproxy 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
187ms

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
2 open 5 never probed 2 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.

  • list_products open 56m ago

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

    mcp-tool

    {
      "type": "object",
      "$schema": "https://json-schema.org/draft/2020-12/schema",
      "properties": {
        "locale": {
          "enum": [
            "tr",
            "en",
            "ru",
            "de",
            "vi"
          ],
          "type": "string"
        }
      }
    }
    arguments 16 lines
  • check_location open 56m ago

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

    mcp-tool

    {
      "type": "object",
      "$schema": "https://json-schema.org/draft/2020-12/schema",
      "properties": {
        "city": {
          "type": "string",
          "maxLength": 40,
          "minLength": 2
        },
        "locale": {
          "enum": [
            "tr",
            "en",
            "ru",
            "de",
            "vi"
          ],
          "type": "string"
        },
        "country": {
          "type": "string",
          "maxLength": 40,
          "minLength": 2
        }
      }
    }
    arguments 26 lines
  • get_pricing unknown never probed

    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.

    mcp-tool

    {
      "type": "object",
      "$schema": "https://json-schema.org/draft/2020-12/schema",
      "required": [
        "slug"
      ],
      "properties": {
        "slug": {
          "type": "string",
          "maxLength": 80,
          "minLength": 2
        },
        "locale": {
          "enum": [
            "tr",
            "en",
            "ru",
            "de",
            "vi"
          ],
          "type": "string"
        },
        "country": {
          "type": "string",
          "maxLength": 40,
          "minLength": 2
        }
      }
    }
    arguments 29 lines
  • start_free_trial unknown never probed

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

    mcp-tool

    {
      "type": "object",
      "$schema": "https://json-schema.org/draft/2020-12/schema",
      "properties": {
        "locale": {
          "enum": [
            "tr",
            "en",
            "ru",
            "de",
            "vi"
          ],
          "type": "string"
        }
      }
    }
    arguments 16 lines
  • recommend_proxy unknown never probed

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

    mcp-tool

    {
      "type": "object",
      "$schema": "https://json-schema.org/draft/2020-12/schema",
      "required": [
        "purpose"
      ],
      "properties": {
        "locale": {
          "enum": [
            "tr",
            "en",
            "ru",
            "de",
            "vi"
          ],
          "type": "string"
        },
        "country": {
          "type": "string",
          "maxLength": 40,
          "minLength": 2
        },
        "purpose": {
          "enum": [
            "scraping",
            "seo",
            "social",
            "ads",
            "gaming",
            "streaming",
            "research",
            "general"
          ],
          "type": "string"
        },
        "protocol": {
          "enum": [
            "http",
            "socks5",
            "udp"
          ],
          "type": "string"
        },
        "estimatedTrafficGb": {
          "type": "number",
          "maximum": 100000,
          "minimum": 0
        }
      }
    }
    arguments 50 lines
  • diagnose_proxy_error unknown never probed

    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.

    mcp-tool

    {
      "type": "object",
      "$schema": "https://json-schema.org/draft/2020-12/schema",
      "required": [
        "code"
      ],
      "properties": {
        "code": {
          "type": "string",
          "maxLength": 80,
          "minLength": 2
        },
        "locale": {
          "enum": [
            "tr",
            "en",
            "ru",
            "de",
            "vi"
          ],
          "type": "string"
        }
      }
    }
    arguments 24 lines
  • search_guides unknown 56m ago

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

    mcp-tool

    {
      "type": "object",
      "$schema": "https://json-schema.org/draft/2020-12/schema",
      "required": [
        "query"
      ],
      "properties": {
        "query": {
          "type": "string",
          "maxLength": 120,
          "minLength": 2
        },
        "locale": {
          "enum": [
            "tr",
            "en",
            "ru",
            "de",
            "vi"
          ],
          "type": "string"
        }
      }
    }
    arguments 24 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 b7c1bfc25301d482.

Every step, filled in for this listing: https://brick.blue/api/v1/agents/b7c1bfc25301d482/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/b7c1bfc25301d482/badge.svg)](https://brick.blue/agent/b7c1bfc25301d482?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.