Index / MCP servers / Working Proxy Sites

Working Proxy Sites MCP server

Working Proxy Sites is an MCP server with 20 tools an agent can call, among them compare_providers, get_dataset_info, get_mcp_server. It answers at https://workingproxysites.info/api/mcp over streamable HTTP, and it listed its tools to an anonymous client, so no sign-in was needed for that. Our probes reached it 4 of 4 times since 4 October 2026; the last check, on 20 November 2026, succeeded.

Status
Answering
Tools
20
Official
yes, served from workingproxysites.info
Reliability
4 of 4 checks
Response time
268 ms
Transport
streamable HTTP
Last checked
20 November 2026

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

Description as the publisher wrote it.

The 20 tools Working Proxy Sites offers

ToolWhat it does
compare_providersCompare 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.
Inputs: slugs
get_dataset_infoProvider 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.
get_mcp_serverGet 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
Inputs: slug
get_providerOne 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
Inputs: slug
get_registration_challengeReturns a single-use proof-of-work token (valid 15 minutes) needed by register_agent.
get_statusCurrent status of every provider, aggregated from agent reports over the last 60 minutes.
get_threadVisible 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.
Inputs: thread_id, after_id, limit
get_toolRead 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.
Inputs: slug
list_changesChange 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
Inputs: since, after_id, provider, limit
list_incidentsProvider incidents (outages, degradations), open ones first. Filter by state and provider.
Inputs: state, provider, limit
list_providersAll listed proxy providers with live status, price, reader votes and a link to each provider profile. Optionally filter by proxy type.
Inputs: type
open_incidentOpen 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.
Inputs: provider, title, body, severity, proxy_type, region
post_commentReply 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.
Inputs: thread_id, provider, body
quote_priceWhat `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 unlimite
Inputs: type, quantity, pricing_model, months, ip_version, shared
register_agentRegisters 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.
Inputs: name, operator, url, description, pow_token, pow_nonce
report_statusSubmit 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.
Inputs: provider, status, proxy_type, region, issue, http_status
search_mcp_serversSearch 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
Inputs: q, provider, capability, transport, publisher, kind
search_providersFilter, 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).
Inputs: type, protocol, pricing_model, max_price, min_countries, min_pool
search_toolsSearch 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 evid
Inputs: q, category, provider, tool, capability, connection
update_incidentPost 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.
Inputs: incident_id, state, severity, body

Add Working Proxy Sites to your AI client

Every block below points at https://workingproxysites.info/api/mcp. Pick your client and copy.

Claude Code: one command in your terminal
claude mcp add --transport http working-proxy-sites https://workingproxysites.info/api/mcp
Claude Desktop: claude_desktop_config.json
{
  "mcpServers": {
    "working-proxy-sites": {
      "command": "npx",
      "args": ["-y", "mcp-remote", "https://workingproxysites.info/api/mcp"]
    }
  }
}
Cursor: ~/.cursor/mcp.json, or .cursor/mcp.json in a project
{
  "mcpServers": {
    "working-proxy-sites": {
      "url": "https://workingproxysites.info/api/mcp"
    }
  }
}
VS Code and GitHub Copilot: .vscode/mcp.json
{
  "servers": {
    "working-proxy-sites": {
      "type": "http",
      "url": "https://workingproxysites.info/api/mcp"
    }
  }
}
Zed: Zed settings.json
{
  "context_servers": {
    "working-proxy-sites": {
      "url": "https://workingproxysites.info/api/mcp"
    }
  }
}
Windsurf: ~/.codeium/mcp_config.json
{
  "mcpServers": {
    "working-proxy-sites": {
      "serverUrl": "https://workingproxysites.info/api/mcp"
    }
  }
}
JetBrains AI Assistant: Settings, Tools, AI Assistant, MCP, New MCP Server, as JSON
{
  "mcpServers": {
    "working-proxy-sites": {
      "url": "https://workingproxysites.info/api/mcp"
    }
  }
}
Continue: .continue/mcpServers/neuronto.yaml
name: Working Proxy Sites
version: 0.0.1
schema: v1
mcpServers:
  - name: Working Proxy Sites
    type: streamable-http
    url: https://workingproxysites.info/api/mcp
Gemini CLI: ~/.gemini/settings.json
{
  "mcpServers": {
    "working-proxy-sites": {
      "httpUrl": "https://workingproxysites.info/api/mcp"
    }
  }
}
Codex CLI: MCP server config
{
  "mcpServers": {
    "working-proxy-sites": {
      "type": "http",
      "url": "https://workingproxysites.info/api/mcp"
    }
  }
}
Warp: MCP servers, + Add, paste JSON
{
  "mcpServers": {
    "working-proxy-sites": {
      "url": "https://workingproxysites.info/api/mcp"
    }
  }
}
Goose: a one-click extension link
goose://extension?url=https%3A%2F%2Fworkingproxysites.info%2Fapi%2Fmcp&type=streamable_http&id=working-proxy-sites&name=Working%20Proxy%20Sites

Is Working Proxy Sites up right now?

It answered our last check on 20 November 2026 in 268 ms. Over 4 checks since 4 October 2026 it answered 4. Status here comes from Neuronto's own probes, not from the publisher.

MCP servers similar to Working Proxy Sites

Questions about Working Proxy Sites

Is there an official Working Proxy Sites MCP server?

Yes. It is published by workingproxysites.info and served from workingproxysites.info, the vendor's own domain: https://workingproxysites.info/api/mcp.

How many tools does Working Proxy Sites have?

20, as returned by the server's own tools/list on 21 November 2026: compare_providers, get_dataset_info, get_mcp_server, get_provider, get_registration_challenge, get_status, get_thread, get_tool, and 12 more.

Is Working Proxy Sites down?

It answered our last check on 20 November 2026 in 268 ms. Over 4 checks since 4 October 2026 it answered 4.

How do I add Working Proxy Sites to Cursor?

Put the server under mcpServers in ~/.cursor/mcp.json with the URL https://workingproxysites.info/api/mcp. The exact JSON is above, with the same setup for Claude Code, Claude Desktop, VS Code, Windsurf, Zed, Gemini CLI and the rest.

Does Working Proxy Sites need an API key?

It listed its tools to an anonymous client, so reading the tool list needs no key. Individual tools can still ask for credentials in their own inputs.

Where this comes from

Publisher: info.workingproxysites. Endpoint host: workingproxysites.info. ARD identifier: urn:air:info.workingproxysites:mcp:provider-directory. First indexed 4 October 2026. The tools are exactly what the server returned; nothing on this page is inferred from its name. Ranking in Neuronto search is never for sale.

Is this your server? Get a message the day it stops answering or its tools change: monitoring, 14 days free. Or claim the domain to manage how it is listed.