# io.github.bolivian-peru/proxies-sx-mcp-server (remote · api.proxies.sx)

Residential and mobile proxies and Private modems for AI agents: proxy URLs, stock, rotation, top-up

- Trust score: 72/100 (medium)
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-05

## Components

- remote · `api.proxies.sx`: 72/100 (this document), [markdown](https://verifymcp.io/servers/bolivian-peru-proxies-sx-mcp-server/api.md), [page](https://verifymcp.io/servers/bolivian-peru-proxies-sx-mcp-server/api)
- npm · `@proxies-sx/mcp-server`: 63/100, [markdown](https://verifymcp.io/servers/bolivian-peru-proxies-sx-mcp-server/proxies-sx-mcp-server.md), [page](https://verifymcp.io/servers/bolivian-peru-proxies-sx-mcp-server/proxies-sx-mcp-server)

## Channel facts

- Endpoint: `https://api.proxies.sx/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `3.2.0`

## Trust breakdown

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. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-11-05.

- **Endpoint Security**: 74/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one.
  - HTTPS is enforced; there's no plaintext access path.
  - HSTS check failed: the Strict-Transport-Security header is absent.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 63/100
  - AI-judged instruction clarity (good).
  - 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.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 20/100
  - Stability observed for 6 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 5 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 6 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

## Install

### 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.

### Claude

```bash
claude mcp add --transport http bolivian-peru-proxies-sx-mcp-server 'https://api.proxies.sx/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "bolivian-peru-proxies-sx-mcp-server": {
      "url": "https://api.proxies.sx/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "bolivian-peru-proxies-sx-mcp-server": {
      "type": "http",
      "url": "https://api.proxies.sx/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.bolivian-peru-proxies-sx-mcp-server]
url = "https://api.proxies.sx/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "bolivian-peru-proxies-sx-mcp-server": {
      "type": "remote",
      "url": "https://api.proxies.sx/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add bolivian-peru-proxies-sx-mcp-server --url 'https://api.proxies.sx/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  bolivian-peru-proxies-sx-mcp-server:
    url: "https://api.proxies.sx/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "bolivian-peru-proxies-sx-mcp-server": {
      "Transport": "http",
      "Url": "https://api.proxies.sx/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add bolivian-peru-proxies-sx-mcp-server -t streamable-http -u 'https://api.proxies.sx/mcp'
```

### Other

```json
{
  "mcpServers": {
    "bolivian-peru-proxies-sx-mcp-server": {
      "type": "http",
      "url": "https://api.proxies.sx/mcp"
    }
  }
}
```

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-11-05 (score 72, +1)

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

### 2026-11-03 (score 71, +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.

### 2026-11-01 (score 70, +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.

### 2026-10-31 (score 69, 0)

- [functional improvement] Stability: unverified → 0.03

### 2026-10-30 (score 69)

First indexed and scored.

## MCP tools (5)

### `pool_get_stock` (~89 tokens)

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.

Input parameters:

- `country` (string): 2-letter ISO country code, for example us or de

### `pool_get_facets` (~140 tokens)

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.

Input parameters:

- `carrier` (string): Narrow to one carrier
- `city` (string): Narrow to one city
- `country` (string, required): 2-letter ISO country code
- `pool` (string): Which pool to look at (default: peer)
- `state` (string): Narrow to one state or region

### `pool_build_proxy_url` (~560 tokens)

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.

Input parameters:

- `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, required): 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)

### `pool_explain_error` (~109 tokens)

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.

Input parameters:

- `error` (string, required): The error text or code from the gateway

### `get_service_status` (~62 tokens)

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.

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/bolivian-peru-proxies-sx-mcp-server/api#diagnostics

## Score history

- 2026-11-05: 72
- 2026-11-04: 71
- 2026-11-03: 71
- 2026-11-02: 70
- 2026-11-01: 70
- 2026-10-31: 69
- 2026-10-30: 69

## Common questions

### 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 72 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 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

## Links

- Remote endpoint: https://api.proxies.sx/mcp
- Repository: https://github.com/bolivian-peru/proxies-sx-mcp-server
- Website: https://agents.proxies.sx/mcp/
- Changelog RSS feed: https://verifymcp.io/servers/bolivian-peru-proxies-sx-mcp-server/api.xml
- Changelog JSON feed: https://verifymcp.io/servers/bolivian-peru-proxies-sx-mcp-server/api.json
- HTML version of this page: https://verifymcp.io/servers/bolivian-peru-proxies-sx-mcp-server/api