# ProxyCove (remote · mcp.proxycove.com)

Buy and manage residential, mobile and datacenter proxies in 170+ countries, prepaid per GB

- Trust score: 70/100 (medium)
- Change this week: +3
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-09-28

## Components

- remote · `mcp.proxycove.com`: 70/100 (this document), [markdown](https://verifymcp.io/servers/com-proxycove-mcp-server/mcp.md), [page](https://verifymcp.io/servers/com-proxycove-mcp-server/mcp)

## Channel facts

- Endpoint: `https://mcp.proxycove.com/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `1.0.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-09-28.

- **Endpoint Security**: 57/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - Authorisation not fully verified: no authorisation is required to call this server, and 1 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe.
  - 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**: 80/100
  - AI-judged instruction clarity (excellent).
  - Tool/resource definitions use about 1256 tokens (~83/item across 15 items; 15 tools + 0 resources), lean.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 47/100
  - Stability observed for 14 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**: 75/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - 0 of 1 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation; "pay_from_agent_wallet" implies "pay" and declares readOnlyHint instead, contradicting what its own name says it does.
  - An AI judge read all 16 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 ProxyCove MCP server?

ProxyCove is a hosted endpoint at https://mcp.proxycove.com/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 com-proxycove-mcp-server 'https://mcp.proxycove.com/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "com-proxycove-mcp-server": {
      "url": "https://mcp.proxycove.com/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "com-proxycove-mcp-server": {
      "type": "http",
      "url": "https://mcp.proxycove.com/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.com-proxycove-mcp-server]
url = "https://mcp.proxycove.com/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "com-proxycove-mcp-server": {
      "type": "remote",
      "url": "https://mcp.proxycove.com/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add com-proxycove-mcp-server --url 'https://mcp.proxycove.com/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  com-proxycove-mcp-server:
    url: "https://mcp.proxycove.com/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "com-proxycove-mcp-server": {
      "Transport": "http",
      "Url": "https://mcp.proxycove.com/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add com-proxycove-mcp-server -t streamable-http -u 'https://mcp.proxycove.com/mcp'
```

### Other

```json
{
  "mcpServers": {
    "com-proxycove-mcp-server": {
      "type": "http",
      "url": "https://mcp.proxycove.com/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-09-28 (score 70, 0)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

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

### 2026-09-25 (score 69, +1)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-09-23 (score 68, +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.

### 2026-09-20 (score 67, +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-09-18 (score 66, +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-09-17 (score 65, −1)

- [security] The server rewrote its instructions, which are the text every model session reads
- [functional regression] Schema quality: 75 → 83
- [functional] Destructive annotations: pass → 0
- [functional] New tool “pay_from_agent_wallet”

### 2026-09-15 (score 66, +1)

- [functional improvement] Stability: unverified → 0.03

## MCP tools (15)

### `get_pricing` (~24 tokens)

Get pricing

Prices per GB (USD) for residential / mobile / datacenter proxies.

### `list_locations` (~25 tokens)

List available countries

Countries available for the given proxy type.

Input parameters:

- `type` (string, required): Proxy type

### `create_account` (~163 tokens)

Create ProxyCove account

Creates a new account WITHOUT registration forms and returns an API key (pc_live_...). IMPORTANT: if the human already has a ProxyCove account, do NOT create a new one — ask them for a key from the website cabinet or the Telegram bot instead. The key is shown ONCE and IS the account: there is no password. Tell the human to save it and add it as the Authorization header ("Bearer <key>") of this connector. Losing the key means losing the balance unless a recovery channel is attached — offer attach_recovery (email) or link_telegram right after the account is created.

Input parameters:

- `contact_email` (string): Optional email for account recovery
- `label` (string): Short account label, e.g. the human's project name

### `get_account` (~21 tokens)

Get account and balance

Current balance (USD), attached email and number of active proxies.

### `create_topup` (~129 tokens)

Create top-up payment link

Creates an invoice and returns payment_url. Give the URL to the human — they open it in the browser and pay. Methods: sbp (Russian instant bank transfer, default for RU users), card_ru (Russian bank card), crypto (crypto via the RU provider), card_international (international card, best for non-RU users), crypto_cryptomus (crypto via Cryptomus — alternative crypto gateway). Agents must NEVER collect card details.

Input parameters:

- `amount_usd` (number, required): Top-up amount in USD, min 1.5
- `method` (string): Payment method

### `pay_from_agent_wallet` (~129 tokens)

Pay directly from the agent wallet (no human)

Tops up the ProxyCove balance by paying yourself, without sending a link to a human. Requires a machine payment credential (MPP / Shared Payment Token) in your HTTP client. Returns the endpoint and instructions: POST {"amount_usd": N} with your ProxyCove key in the Authorization header, answer the HTTP 402 challenge, and the balance is credited at once. If you have no payment credential, use create_topup instead and hand the link to the human.

Input parameters:

- `amount_usd` (number, required): Amount in USD to add to the balance, min 1.5

### `get_payment_status` (~43 tokens)

Check payment status

Status of an invoice: pending | paid | cancelled. Poll after the human opens the payment link.

Input parameters:

- `invoice_id` (string, required): Invoice id from create_topup

### `buy_proxy` (~178 tokens)

Buy proxy

Buys a proxy, deducting the account balance. Returns connection credentials (host go.proxycove.com, port 824 = new IP every request, port 10000 = sticky IP by interval). Check get_pricing × traffic_gb against the balance first. IMPORTANT: wait ~5 seconds after the purchase before sending the first request through the proxy — the country filter takes a moment to propagate at the upstream provider, so an immediate first request may exit from another country.

Input parameters:

- `country` (string): Country code, e.g. "br" for Brazil. Omit for mixed pool
- `rotation_interval_minutes` (integer): Sticky IP: keep the same IP for N minutes. Omit = rotate on every request
- `traffic_gb` (integer, required): Prepaid traffic in GB
- `type` (string, required): Proxy type

### `list_proxies` (~21 tokens)

List proxies

All proxies of the account with remaining traffic and connection credentials.

### `get_credentials` (~42 tokens)

Get connection credentials

Connection string for one proxy: http://login:password@go.proxycove.com:port.

Input parameters:

- `proxy_id` (string, required): Proxy id from list_proxies

### `extend_proxy` (~48 tokens)

Add traffic to proxy

Adds prepaid GB to an existing proxy (same credentials keep working). Deducts balance.

Input parameters:

- `proxy_id` (string, required): Proxy id
- `traffic_gb` (integer, required): GB to add

### `get_usage` (~27 tokens)

Get traffic usage

Live used / remaining traffic for one proxy.

Input parameters:

- `proxy_id` (string, required): Proxy id

### `set_rotation` (~59 tokens)

Change IP rotation

Switch between rotate-every-request (port 824) and sticky interval 1..120 minutes (port 10000).

Input parameters:

- `interval_minutes` (integer): Sticky interval; omit to rotate every request
- `proxy_id` (string, required): Proxy id

### `link_telegram` (~72 tokens)

Link account to Telegram bot

Returns a short code the human sends to the ProxyCove Telegram bot (@ProxyCove_bot → "Link website account"). After linking, the human can manage the account and issue new API keys from the bot — a second way to keep access if the API key is lost. Code expires in 30 minutes.

### `attach_recovery` (~49 tokens)

Attach recovery email

Attaches an email to the account so the human can log in on proxycove.com (via "Forgot password") and never lose the balance.

Input parameters:

- `email` (string, required): Human's email

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/com-proxycove-mcp-server/mcp#diagnostics

## Score history

- 2026-09-28: 70
- 2026-09-27: 70
- 2026-09-26: 69
- 2026-09-25: 69
- 2026-09-24: 68
- 2026-09-23: 68
- 2026-09-22: 67
- 2026-09-21: 67
- 2026-09-20: 67
- 2026-09-19: 66
- 2026-09-18: 66
- 2026-09-17: 65
- 2026-09-16: 66
- 2026-09-15: 66
- 2026-09-14: 65

## Common questions

### What is the ProxyCove MCP server?

ProxyCove is an MCP server listed in the public MCP registry as com.proxycove/mcp-server. Buy and manage residential, mobile and datacenter proxies in 170+ countries, prepaid per GB. This page covers its hosted endpoint (https://mcp.proxycove.com/mcp).

### Is the ProxyCove MCP server safe to use?

ProxyCove scores 70 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 ProxyCove MCP server expose?

ProxyCove exposes 15 tools: get_pricing, list_locations, create_account, get_account, create_topup, and 10 more. Their descriptions and schemas cost roughly 1,030 tokens of context every time the server is loaded.

### Does the ProxyCove MCP server require authentication?

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

### Is the ProxyCove MCP server still maintained?

ProxyCove is still listed as active in the MCP registry. We last reached this channel on 28 September 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://mcp.proxycove.com/mcp
- Repository: https://github.com/proxycove/mcp-server
- Website: https://proxycove.com/
- Changelog RSS feed: https://verifymcp.io/servers/com-proxycove-mcp-server/mcp.xml
- Changelog JSON feed: https://verifymcp.io/servers/com-proxycove-mcp-server/mcp.json
- HTML version of this page: https://verifymcp.io/servers/com-proxycove-mcp-server/mcp