Remote MCP · Endpoint

Working Proxy Sites MCP server

No. Working Proxy Sites answered an MCP handshake 1 hour ago.

UpLast checked 1 hour ago

Server URL

https://workingproxysites.info/api/mcp

The last check completed an MCP handshake.

Registry name
info.workingproxysites/provider-directory
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
160 ms
Tools exposed
20 tools
Uptime, last 30 days
92.3% from 13 checks
Described by its publisher as
Research proxy providers, compare published prices, and discover provider MCP integrations.
Listing
From the official MCP registry (active).
Recent checks of Working Proxy Sites
CheckedResultHandshake
1 hour agoHandshake completed160 ms
2 days agoFailed - the server returned an HTTP error—
5 days agoHandshake completed119 ms
7 days agoHandshake completed115 ms
9 days agoHandshake completed172 ms
11 days agoHandshake completed150 ms
13 days agoHandshake completed139 ms
15 days agoHandshake completed117 ms
17 days agoHandshake completed95 ms
19 days agoHandshake completed120 ms
20 days agoHandshake completed161 ms
21 days agoHandshake completed154 ms
23 days agoHandshake completed161 ms

The last 13 checks. Full history is kept for 30 days; the all-time counter stands at 12 responding of 13.

How to read this

  • ·Handshake latency is one measurement from one probe, from our infrastructure. It is a smoke signal about the endpoint, not a benchmark of your own connection to it.
  • ·An authentication challenge counts as responding. A hosted server that refuses an anonymous prober is behaving correctly.
  • ·A tool count of “behind credentials” means the handshake worked but listing tools needed a token we do not hold.
  • ·Uptime covers the last 30 days of our own checks, at most one an hour, and says how many checks it is drawn from.

Listing data comes from the official MCP registry. Glide is not affiliated with Working Proxy Sites and makes no claim about it beyond what these checks measured.