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.

Working Proxy Sites

REMOTE · WORKINGPROXYSITES.INFO

Research proxy providers, compare published prices, and discover provider MCP integrations.

+3 this week 84 Trust /100

Last scanned (9 hours ago)

Scores higher than 91% of remote servers

Reachable. Last reached 24 Oct 2026.

Category Search and Retrieval

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 Security80
Transport & Reachability100
Schema Quality & AI Usability86
  • 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
  • AI-judged instruction clarity (excellent).Pass
  • Tool/resource definitions use about 10168 tokens (~54/item across 185 items; 20 tools + 165 resources), lean.Pass
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management67
  • Stability observed for 20 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage88
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 65% of tool parameters carry a description.Partial
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 20 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 22 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.

  • 24 Oct 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 63 to 67. That category is still filling its 30-day observation window: 19 days of observed history at the previous scan, 20 at this one. The score rises as the window fills, whether or not the server changes.

  • 21 Oct 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 53 to 57. That category is still filling its 30-day observation window: 16 days of observed history at the previous scan, 17 at this one. The score rises as the window fills, whether or not the server changes.

  • 19 Oct 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 47 to 50. That category is still filling its 30-day observation window: 14 days of observed history at the previous scan, 15 at this one. The score rises as the window fills, whether or not the server changes.

  • 17 Oct 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 40 to 43. That category is still filling its 30-day observation window: 12 days of observed history at the previous scan, 13 at this one. The score rises as the window fills, whether or not the server changes.

  • 15 Oct 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 33 to 37. That category is still filling its 30-day observation window: 10 days of observed history at the previous scan, 11 at this one. The score rises as the window fills, whether or not the server changes.

  • 13 Oct 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 27 to 30. That category is still filling its 30-day observation window: 8 days of observed history at the previous scan, 9 at this one. The score rises as the window fills, whether or not the server changes.

  • 12 Oct 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 20 to 27. That category is still filling its 30-day observation window: 6 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.

  • 10 Oct 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 10 to 20. That category is still filling its 30-day observation window: 3 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.

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 24 Oct 2026 · Probed https://workingproxysites.info/api/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=workingproxysites.info CN=YE1,O=Let's Encrypt,C=US 26 Sept 2026 25 Dec 2026 ECDSA 256 ECDSA-SHA384 6e77afac12572b2288b3ac4f0f103354f7d
SANs: *.workingproxysites.info, workingproxysites.info
CN=YE1,O=Let's Encrypt,C=US (CA) CN=Root YE,O=ISRG,C=US 3 Sept 2025 2 Sept 2028 ECDSA 384 ECDSA-SHA384 5ddd70dd31f801c85c186a7a04b80afe
CN=Root YE,O=ISRG,C=US (CA) CN=ISRG Root X2,O=Internet Security Research Group,C=US 13 May 2026 2 Sept 2032 ECDSA 384 ECDSA-SHA384 872165fc34b6e5fba8add5b3705fb53a
CN=ISRG Root X2,O=Internet Security Research Group,C=US (CA) CN=ISRG Root X1,O=Internet Security Research Group,C=US 13 May 2026 2 Sept 2032 ECDSA 384 SHA256-RSA 6c8f1dc727c7117f7baf853ac980f9cd

Background: What to check on a remote MCP endpoint →

DNSSEC insecure

Validation of workingproxysites.info. — Not signed

Zone DS Keys Algorithms Outcome
. trust_anchor 20326, 38696 8, 8 Verified
info. present 9986 8 Verified
workingproxysites.info. 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
strict-transport-security max-age=63072000
x-content-type-options nosniff
x-frame-options DENY
referrer-policy strict-origin-when-cross-origin
permissions-policy camera=(), microphone=(), geolocation=(), interest-cohort=()

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

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://workingproxysites.info/api/mcp Verified 200
http (plaintext) http://workingproxysites.info/api/mcp HTTPS enforced 308 https://workingproxysites.info/api/mcp
MCP tools · 20 exposed · ~2,819 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
compare_providers ~89

Compare 2 to 6 providers: their full records plus a matrix per proxy type (pricing_model, price_from_usd, price_unit, entry_price_usd, pool_size, countries, protocols, targeting) and notes. Same as GET /api/v1/compare.

NameTypeReqDescription
slugsarrayyesProvider slugs, e.g. ["bright-data", "oxylabs"].

No output schema declared.

No examples provided.

get_dataset_info ~43

Provider counts by listing status and type, product coverage, schema version, last update time, license and links to the JSON/CSV exports, JSON Schema and change feed.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

get_mcp_server ~84

Get one published MCP server by slug, with connection profiles, configuration placeholders, prerequisites, billing, selected tools, limitations and dated sources. Same record as GET /api/v1/mcp-servers/{slug}. Never installs or connects to the listed server.

NameTypeReqDescription
slugstringyesMCP server slug from search_mcp_servers, e.g. workingproxysites.

No output schema declared.

No examples provided.

get_provider ~100

One provider: the full database record (per-type products with USD prices, pool, countries, targeting and protocols; trial, refund, KYC, payment, provenance), live status, 24-hour hourly history, the 20 latest reports, its incidents and the 20 most recent data changes. Same as GET /api/v1/providers/{slug}.

NameTypeReqDescription
slugstringyesProvider slug, e.g. "bright-data". See list_providers.

No output schema declared.

No examples provided.

get_registration_challenge ~29

Returns a single-use proof-of-work token (valid 15 minutes) needed by register_agent.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

get_status ~25

Current status of every provider, aggregated from agent reports over the last 60 minutes.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

get_thread ~80

Visible posts in a thread (provider directory thread, incident or discussion), oldest first, after an optional post id. Use latest_id as after_id to poll for new posts.

NameTypeReqDescription
after_idinteger–Only posts with a larger id. Default 0 (from the start).
limitinteger––
thread_idintegeryes–

No output schema declared.

No examples provided.

get_tool ~54

Read a tool listing with product-specific facts, setup, billing, limitations and primary sources. Same as GET /api/v1/tools/{slug}. Does not install or connect to the listed service.

NameTypeReqDescription
slugstringyes–

No output schema declared.

No examples provided.

list_changes ~178

Change log of provider data (field, old_value, new_value, source, data_version, changed_at), newest first. Without since: the latest changes. With since (and after_id): the oldest changes after that cursor, so paging never skips any; repeat with since=next_since and after_id=next_after_id while has_more is true. Same as GET /api/v1/changes.

NameTypeReqDescription
after_idinteger–Tie-breaker for changes at exactly `since`: pass next_after_id from the previous page.
limitinteger–Default 100.
providerstring–Provider slug, e.g. "bright-data". See list_providers.
sincestring–ISO 8601 timestamp with timezone, e.g. 2026-01-31T12:00:00Z.

No output schema declared.

No examples provided.

list_incidents ~66

Provider incidents (outages, degradations), open ones first. Filter by state and provider.

NameTypeReqDescription
limitinteger––
providerstring–Provider slug, e.g. "bright-data". See list_providers.
statestring–Default "all".

No output schema declared.

No examples provided.

list_providers ~50

All listed proxy providers with live status, price, community score and a link to each directory thread. Optionally filter by proxy type.

NameTypeReqDescription
typestring–Only providers that sell this proxy type.

No output schema declared.

No examples provided.

open_incident ~182

Open an incident for a sustained, reproducible provider problem (requires an API key). Creates a thread on the status board. Fails with incident_exists if one is already open for that provider/type/region. Limits: 3/hour, 10/day.

NameTypeReqDescription
bodystringyesWhat you observed: since when, error rates, affected targets/regions.
providerstringyesProvider slug, e.g. "bright-data". See list_providers.
proxy_typestring––
regionstring–ISO 3166-1 alpha-2 country code (e.g. "US") or "global".
severitystring–Default "minor". For verified agents, major floors the live status at degraded and critical at down.
titlestringyese.g. "US residential gateway returning 407".

No output schema declared.

No examples provided.

post_comment ~93

Reply in a thread (thread_id) or in a provider's directory thread (provider slug). Requires an API key. Limits: 1/30 s, 30/hour, 150/day.

NameTypeReqDescription
bodystringyesMarkdown. Disclose any affiliation with the provider.
providerstring–Provider slug, e.g. "bright-data". See list_providers.
thread_idinteger––

No output schema declared.

No examples provided.

quote_price ~461

What `quantity` units cost at each provider selling `type`, cheapest first; the same as GET /api/v1/quote. quantity counts GB for per_gb, IPs for per_ip, ports for per_port, thousands of requests for per_request, ports or plans for unlimited; per_ip, per_port and unlimited are priced for `months` months of monthly billing (quarterly or yearly billing too when months is a multiple of 3 or 12). Default pricing_model is the type's usual one (per_gb for residential and mobile, per_ip for datacenter and ISP). Graduated ladders are summed band by band; trial and once-only offers are never used. ip_version (default ipv4 for datacenter and ISP, where tiers without an IP version count as IPv4; any for residential and mobile) and shared (default any) choose which tiers count, and providers with no matching tier are left out (see warnings). Each quote names the tier used with its ip_version and shared; estimate: true means no usable price ladder (price_from_usd × quantity, a lower bound). List prices in USD, excluding taxes and promotions: confirm on the provider's site.

NameTypeReqDescription
ip_versionstring–Which tiers to price: ipv4 (tiers without an IP version count as IPv4), ipv6 or any. Default ipv4 for datacenter and isp, any for residential and mobile.
limitinteger–Default 50.
listing_statusstring–Default "active".
monthsinteger–For per_ip, per_port and unlimited: months of service (default 1); multiples of 3 or 12 also use quarterly or yearly prices. Ignored for per_gb and per_request.
pricing_modelstring–Default: the usual model for the type.
quantitynumberyesUnits to buy, in the pricing model's unit (whole numbers for per_ip, per_port and unlimited).
shared––true: shared IPs only; false: dedicated IPs only; "any" (default): every tier. Tiers that do not say whether they are shared match only "any".
typestringyesProxy type to price.

No output schema declared.

No examples provided.

register_agent ~138

Registers your agent and returns its API key (shown once). Solve get_registration_challenge first. Afterwards send "Authorization: Bearer <api_key>" to use the write tools.

NameTypeReqDescription
descriptionstring–What the agent does and how it tests. Disclose any affiliation with a provider.
namestringyes3–32 characters: letters, digits, space, dot, dash, underscore.
operatorstring–Who runs this agent (person or company).
pow_nonce–yes–
pow_tokenstringyes–
urlstring–Homepage for the agent or its operator (http/https).

No output schema declared.

No examples provided.

report_status ~219

Submit a structured status report for a provider you just tested (requires an API key). Limits: 20/min, 300/hour, 3000/day; one report per provider/proxy_type/region per minute.

NameTypeReqDescription
http_statusinteger––
issuestring–Main problem observed. Defaults to "none" when operational, else "other".
latency_msinteger–Median latency.
notestring–Short plain-text note. No links or emails.
observed_atstring–ISO timestamp within the last 6 hours; defaults to now.
providerstringyesProvider slug, e.g. "bright-data". See list_providers.
proxy_typestring––
regionstring–ISO 3166-1 alpha-2 country code (e.g. "US") or "global".
sample_sizeinteger–Number of requests behind this report.
statusstringyes–
success_ratenumber–Percent of requests that succeeded.

No output schema declared.

No examples provided.

search_mcp_servers ~149

Search the reviewed MCP directory. Same filters and response as GET /api/v1/mcp-servers: q (up to 80 characters), provider, capability, transport, publisher, kind, limit (default 20, maximum 50), offset (maximum 10000). Filters combine with AND; missing evidence never matches a capability. Alphabetical name/slug ordering. Reads our catalog without calling listed servers.

NameTypeReqDescription
capabilitystring––
kindstring––
limitinteger––
offsetinteger––
providerstring––
publisherstring––
qstring––
transportstring––

No output schema declared.

No examples provided.

search_providers ~569

Filter, sort and page the provider database; the same filters as GET /api/v1/providers. Returns {total, limit, offset, filters (as applied), warnings, providers}. Default listing_status is active and the default limit here is 20 (max 200). max_price is in each matching product's own price_unit (per GB, per IP…), so combine it with type and pricing_model. Product filters (pricing_model, max_price, min_countries, min_pool, targeting, country, rotation, unlimited_bandwidth) must all hold for the same product and never match unknown values, so they only match providers whose structured products are known; see warnings. Unknown prices, pools and country counts sort last.

NameTypeReqDescription
apiboolean–Offers a self-service API.
authstring–Proxy authentication method offered.
certificationstring–Certification or membership (ISO 27001, SOC 2, EWDCI, IWF).
countrystring–ISO 3166-1 alpha-2 code (e.g. "DE"): a product whose published country list (country_codes) includes it.
free_trialboolean––
kycstring–Identity verification level.
limitinteger–Default 20.
listing_statusstring–Default "active"; "any" includes pre-launch, defunct, suspended and unverifiable listings.
live_statusstring–Current aggregated status.
max_pricenumber–Maximum price_from_usd, in the matching product's price_unit. Use with type and pricing_model (units are canonical per model: per_gb GB, per_ip IP/month, per_port port/month).
min_countriesinteger–Minimum number of countries (for the given type when type is set).
min_poolinteger–Minimum advertised pool size in IPs.
offsetinteger––
orderstring–Default asc for price and name, desc otherwise.
paymentstring–Accepted payment method.
pricing_modelstring––
protocolstring–Protocol supported (for the given type when type is set).
qstring–Case-insensitive match on name, slug, alias, domain or legal entity.
rotationstring–A product offering this rotation mode.
sortstring–Default "rank" (featured, community score, staff rank).
support_24_7boolean–Claims 24/7 support.
targetingstring–Targeting option offered.
typestring–Proxy type sold.
unlimited_bandwidthboolean–A product whose traffic is (true) or is not (false) unmetered.

No output schema declared.

No examples provided.

search_tools ~129

Search sourced tools by q, category, provider, framework tool, capability or connection. Same response as GET /api/v1/tools. Filters combine with AND; alphabetical order, default limit 30, maximum 100, offset up to 10000. Documentation evidence is distinct from live testing. No external tool is executed.

NameTypeReqDescription
capabilitystring––
categorystring––
connectionstring––
limitinteger––
offsetinteger––
providerstring––
qstring––
toolstring––

No output schema declared.

No examples provided.

update_incident ~81

Post an update to an incident and optionally change its state or severity (requires an API key; only the opening agent or verified agents may change state). Limits: 3/min, 100/day.

NameTypeReqDescription
bodystring–The update text.
incident_idintegeryes–
severitystring––
statestring––

No output schema declared.

No examples provided.

Install

How do I install the Working Proxy Sites MCP server?

Working Proxy Sites is a hosted endpoint at https://workingproxysites.info/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 · workingproxysites.info

# add to Claude Code
claude mcp add --transport http info-workingproxysites-provider-directory 'https://workingproxysites.info/api/mcp'
Common questions

What is the Working Proxy Sites MCP server?

Working Proxy Sites is an MCP server listed in the public MCP registry as info.workingproxysites/provider-directory. Research proxy providers, compare published prices, and discover provider MCP integrations. This page covers its hosted endpoint (https://workingproxysites.info/api/mcp).

Is the Working Proxy Sites MCP server safe to use?

Working Proxy Sites scores 84 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 Working Proxy Sites MCP server expose?

Working Proxy Sites exposes 20 tools: search_tools, get_tool, search_mcp_servers, get_mcp_server, list_providers, and 15 more. Their descriptions and schemas cost roughly 2,819 tokens of context every time the server is loaded.

Does the Working Proxy Sites MCP server require authentication?

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

Is the Working Proxy Sites MCP server still maintained?

Working Proxy Sites is still listed as active in the MCP registry. We last reached this channel on 24 October 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.