ProxyCove
REMOTE · MCP.PROXYCOVE.COM · SCANNED SEP 28
Buy and manage residential, mobile and datacenter proxies in 170+ countries, prepaid per GB
Available components
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 Security57
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- 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. See how to fix → View diagnostics → Unverified
- 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 Usability80
- AI-judged instruction clarity (excellent).Pass
- Tool/resource definitions use about 1256 tokens (~83/item across 15 items; 15 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management47
- Stability observed for 14 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 Safety75
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- 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. See how to fix → Fail
- An AI judge read all 16 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
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.
remote · mcp.proxycove.com
claude mcp add --transport http com-proxycove-mcp-server 'https://mcp.proxycove.com/mcp'
{
"mcpServers": {
"com-proxycove-mcp-server": {
"url": "https://mcp.proxycove.com/mcp"
}
}
} {
"servers": {
"com-proxycove-mcp-server": {
"type": "http",
"url": "https://mcp.proxycove.com/mcp"
}
}
} [mcp_servers.com-proxycove-mcp-server] url = "https://mcp.proxycove.com/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"com-proxycove-mcp-server": {
"type": "remote",
"url": "https://mcp.proxycove.com/mcp",
"enabled": true
}
}
} openclaw mcp add com-proxycove-mcp-server --url 'https://mcp.proxycove.com/mcp' --transport streamable-http
mcp_servers:
com-proxycove-mcp-server:
url: "https://mcp.proxycove.com/mcp" {
"McpServers": {
"com-proxycove-mcp-server": {
"Transport": "http",
"Url": "https://mcp.proxycove.com/mcp"
}
}
} assistant mcp add com-proxycove-mcp-server -t streamable-http -u 'https://mcp.proxycove.com/mcp'
{
"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.
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.
- 28 Sept 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 27 Sept 26 +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.
- 25 Sept 26 +1
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 23 Sept 26 +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.
- 20 Sept 26 +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.
- 18 Sept 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.
- 17 Sept 26 −1
- The server rewrote its instructions, which are the text every model session reads security
- Schema quality: 75 → 83 ▼ functional
- Destructive annotations: pass → 0 functional
- New tool “pay_from_agent_wallet” functional
- 15 Sept 26 +1
- Stability: unverified → 0.03 ▲ functional
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 28 Sept 2026 · Probed https://mcp.proxycove.com/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=proxycove.com | CN=WE1,O=Google Trust Services,C=US | 23 Sept 2026 | 22 Dec 2026 | ECDSA 256 | ECDSA-SHA256 | c153200c769add9138e0f2b375357ec |
| SANs: proxycove.com, *.proxycove.com | ||||||
| CN=WE1,O=Google Trust Services,C=US (CA) | CN=GTS Root R4,O=Google Trust Services LLC,C=US | 13 Dec 2023 | 20 Feb 2029 | ECDSA 256 | ECDSA-SHA384 | 7ff31977972c224a76155d13b6d685e3 |
| CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) | CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE | 15 Nov 2023 | 28 Jan 2028 | ECDSA 384 | SHA256-RSA | 7fe530bf331343bedd821610493d8a1b |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of mcp.proxycove.com. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| com. | present | 19718 | 13 | Verified |
| proxycove.com. | 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://mcp.proxycove.com/mcp | Verified | 200 | |
| http (plaintext) | http://mcp.proxycove.com/mcp | HTTPS enforced | 301 | https://mcp.proxycove.com/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 →
attach_recovery Attach recovery email ~49
Attaches an email to the account so the human can log in on proxycove.com (via "Forgot password") and never lose the balance.
| Name | Type | Req | Description |
|---|---|---|---|
| string | yes | Human's email |
No output schema declared.
No examples provided.
buy_proxy Buy proxy ~178
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.
| Name | Type | Req | Description |
|---|---|---|---|
| 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 | yes | Prepaid traffic in GB |
| type | string | yes | Proxy type |
No output schema declared.
No examples provided.
create_account Create ProxyCove account ~163
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.
| Name | Type | Req | Description |
|---|---|---|---|
| contact_email | string | – | Optional email for account recovery |
| label | string | – | Short account label, e.g. the human's project name |
No output schema declared.
No examples provided.
create_topup Create top-up payment link ~129
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.
| Name | Type | Req | Description |
|---|---|---|---|
| amount_usd | number | yes | Top-up amount in USD, min 1.5 |
| method | string | – | Payment method |
No output schema declared.
No examples provided.
extend_proxy Add traffic to proxy ~48
Adds prepaid GB to an existing proxy (same credentials keep working). Deducts balance.
| Name | Type | Req | Description |
|---|---|---|---|
| proxy_id | string | yes | Proxy id |
| traffic_gb | integer | yes | GB to add |
No output schema declared.
No examples provided.
get_account Get account and balance ~21
Current balance (USD), attached email and number of active proxies.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
get_credentials Get connection credentials ~42
Connection string for one proxy: http://login:password@go.proxycove.com:port.
| Name | Type | Req | Description |
|---|---|---|---|
| proxy_id | string | yes | Proxy id from list_proxies |
No output schema declared.
No examples provided.
get_payment_status Check payment status ~43
Status of an invoice: pending | paid | cancelled. Poll after the human opens the payment link.
| Name | Type | Req | Description |
|---|---|---|---|
| invoice_id | string | yes | Invoice id from create_topup |
No output schema declared.
No examples provided.
get_pricing Get pricing ~24
Prices per GB (USD) for residential / mobile / datacenter proxies.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
get_usage Get traffic usage ~27
Live used / remaining traffic for one proxy.
| Name | Type | Req | Description |
|---|---|---|---|
| proxy_id | string | yes | Proxy id |
No output schema declared.
No examples provided.
link_telegram Link account to Telegram bot ~72
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.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
list_locations List available countries ~25
Countries available for the given proxy type.
| Name | Type | Req | Description |
|---|---|---|---|
| type | string | yes | Proxy type |
No output schema declared.
No examples provided.
list_proxies List proxies ~21
All proxies of the account with remaining traffic and connection credentials.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
pay_from_agent_wallet Pay directly from the agent wallet (no human) ~129
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.
| Name | Type | Req | Description |
|---|---|---|---|
| amount_usd | number | yes | Amount in USD to add to the balance, min 1.5 |
No output schema declared.
No examples provided.
set_rotation Change IP rotation ~59
Switch between rotate-every-request (port 824) and sticky interval 1..120 minutes (port 10000).
| Name | Type | Req | Description |
|---|---|---|---|
| interval_minutes | integer | – | Sticky interval; omit to rotate every request |
| proxy_id | string | yes | Proxy id |
No output schema declared.
No examples provided.
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.