io.github.bolivian-peru/proxies-sx-mcp-server
REMOTE · API.PROXIES.SX · 2 COMPONENTS
Residential and mobile proxies and Private modems for AI agents: proxy URLs, stock, rotation, top-up
Available components
Last scanned (20 hours ago)
Scores higher than 57% of remote servers
Reachable. Last reached 4 Nov 2026.
Category Cloud Infrastructure
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 Security74
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one. See how to fix → View diagnostics → Partial
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability63
- AI-judged instruction clarity (good).Pass
- Context-footprint check failed: tool/resource definitions use about 1084 tokens (~216/item across 5 items; 5 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
- 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 Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 5 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 6 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
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.
- 3 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 10 to 13. That category is still filling its 30-day observation window: 3 days of observed history at the previous scan, 4 at this one. The score rises as the window fills, whether or not the server changes.
- 1 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 3 to 7. That category is still filling its 30-day observation window: 1 days of observed history at the previous scan, 2 at this one. The score rises as the window fills, whether or not the server changes.
- 31 Oct 26 0
- Stability: unverified → 0.03 ▲ functional
- 30 Oct 26 69
First indexed and scored.
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 4 Nov 2026 · Probed https://api.proxies.sx/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=api.proxies.sx | CN=YE2,O=Let's Encrypt,C=US | 4 Oct 2026 | 2 Jan 2027 | ECDSA 256 | ECDSA-SHA384 | 525a99396c5df8d73eff6caacb795c77789 |
| SANs: admin.proxies.sx, api.proxies.sx, client.proxies.sx | ||||||
| CN=YE2,O=Let's Encrypt,C=US (CA) | CN=Root YE,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | ECDSA 384 | ECDSA-SHA384 | 4df3b15dd6c0784c507cd37b58e6f115 |
| 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 api.proxies.sx. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| sx. | present | 16495 | 8 | Verified |
| proxies.sx. | 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 |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://api.proxies.sx/mcp | Verified | 200 | |
| http (plaintext) | http://api.proxies.sx/mcp | HTTPS enforced | 301 | https://api.proxies.sx/mcp |
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 →
get_service_status ~62
Check whether Proxies.sx is healthy right now: open Pool Gateway incidents, the state of the API, gateway and relay, and recent uptime. No account needed. Call it when requests fail with 5xx or E_INTERNAL before retrying in a loop.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
pool_build_proxy_url ~560
Build a ready-to-use Pool Gateway proxy URL (gw.proxies.sx, HTTP 7000 or SOCKS5 7001). Local, no network. Take proxyUsername and password from pool_get_my_credentials (a reseller passes a customer pak_ key as password). pool: "peer" is the main network (residential and mobile, most countries), "mbl" is carrier modems in US, GB, FR, NL, PL and GE (Georgia) only, "any" or "best" let the gateway choose. Rotation: sticky and hard both hold one device, auto5/auto10/auto20/auto60 move to another device on that interval, ondemand picks again on each new connection; sticky, hard and auto* only persist across connections with a sid. Sticky holds the device, not the IP: a mobile carrier can still change the exit IP. The result contains the password.
| Name | Type | Req | Description |
|---|---|---|---|
| asn | number | – | Only use one network, by AS number |
| carrier | string | – | Carrier from pool_get_facets: the part of a carrier id before the |, for example tmobile |
| city | string | – | City from pool_get_facets (preferred, not guaranteed) |
| country | string | – | 2-letter ISO country code, or "any" (default: any) |
| failover | string | – | What may replace a device that goes offline (gateway default: samecountry) |
| ipType | string | – | Only use one IP class: mobile (cellular carriers), residential (home broadband) or isp (static addresses on ISP-registered networks, hosted on servers). The isp class is served only when named here.… |
| isp | string | – | ISP name to match, for example comcast |
| pakKey | string | – | Alias of password (a pak_ key) |
| password | string | – | Proxy password, or a pak_ key |
| pool | string | – | Pool (default: any) |
| protocol | string | – | http (default) or socks5 |
| proxyUsername | string | yes | Bare proxy username, for example psx_abc123 |
| rotation | string | – | Rotation mode (gateway default: auto10) |
| sid | string | – | Session id: 1-64 characters, lowercase letters, digits and _. Other characters are removed. |
| state | string | – | State or region code from pool_get_facets, for example ny (preferred, not guaranteed) |
| strict | boolean | – | With sticky or hard: prefer the devices whose exit IP holds longest |
| ttl | number | – | Session lifetime in seconds (gateway default: 3600) |
No output schema declared.
No examples provided.
pool_explain_error ~109
Explain a Pool Gateway error and say what to do about it. Pass the error text your HTTP client got from gw.proxies.sx (it looks like "E_NO_STOCK_COUNTRY: ... (req: ...)") or just the code. Covers E_AUTH_INVALID, E_BALANCE_EXHAUSTED, E_NO_STOCK_COUNTRY, the rate and session limits and the rest. Local, no network.
| Name | Type | Req | Description |
|---|---|---|---|
| error | string | yes | The error text or code from the gateway |
No output schema declared.
No examples provided.
pool_get_facets ~140
List the cities, states, carriers (with ASN and class) and IP classes that have stock in one country, with counts, no account needed. The values are the ones pool_build_proxy_url accepts for city, state, carrier and asn. Pass city, state or carrier to see what remains once that filter is applied.
| Name | Type | Req | Description |
|---|---|---|---|
| carrier | string | – | Narrow to one carrier |
| city | string | – | Narrow to one city |
| country | string | yes | 2-letter ISO country code |
| pool | string | – | Which pool to look at (default: peer) |
| state | string | – | Narrow to one state or region |
No output schema declared.
No examples provided.
pool_get_stock ~89
Get live Pool Gateway stock, no account needed. With a country: the mbl and peer endpoint counts there and the peer counts per class (mobile, residential, isp). Without: totals plus the count per country for both pools. Use it to pick a pool and country before pool_build_proxy_url.
| Name | Type | Req | Description |
|---|---|---|---|
| country | string | – | 2-letter ISO country code, for example us or de |
No output schema declared.
No examples provided.
How do I install the io.github.bolivian-peru/proxies-sx-mcp-server server?
io.github.bolivian-peru/proxies-sx-mcp-server is a hosted endpoint at https://api.proxies.sx/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 · api.proxies.sx
claude mcp add --transport http bolivian-peru-proxies-sx-mcp-server 'https://api.proxies.sx/mcp'
What is the io.github.bolivian-peru/proxies-sx-mcp-server server?
io.github.bolivian-peru/proxies-sx-mcp-server is listed in the public MCP registry as io.github.bolivian-peru/proxies-sx-mcp-server. Residential and mobile proxies and Private modems for AI agents: proxy URLs, stock, rotation, top-up. This page covers its hosted endpoint (https://api.proxies.sx/mcp).
Is the io.github.bolivian-peru/proxies-sx-mcp-server server safe to use?
io.github.bolivian-peru/proxies-sx-mcp-server scores 71 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 io.github.bolivian-peru/proxies-sx-mcp-server server expose?
io.github.bolivian-peru/proxies-sx-mcp-server exposes 5 tools: pool_get_stock, pool_get_facets, pool_build_proxy_url, pool_explain_error, get_service_status. Their descriptions and schemas cost roughly 960 tokens of context every time the server is loaded.
Does the io.github.bolivian-peru/proxies-sx-mcp-server server require authentication?
No. We connected to io.github.bolivian-peru/proxies-sx-mcp-server without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the io.github.bolivian-peru/proxies-sx-mcp-server server still maintained?
io.github.bolivian-peru/proxies-sx-mcp-server is still listed as active in the MCP registry. We last reached this channel on 4 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.