ProxyCove MCP server
2026년 9월 14일 커밋170개 이상의 국가에서 선불 GB 방식을 통해 주거용, 모바일 및 데이터센터 프록시를 구매하고 관리할 수 있도록 AI agent에게 권한을 부여합니다.
다른 이름 proxycove/mcp-server, mcp-server
- 스타
- 0
- Tools
- 14
- 다운로드, 30일
- —
- 최신 버전
- 1.0.0
- 마지막 커밋
- 2026년 9월 14일
- 라이선스
- MIT
ProxyCove MCP란?
170개 이상의 국가에서 선불 GB 방식을 통해 주거용, 모바일 및 데이터센터 프록시를 구매하고 관리할 수 있도록 AI agent에게 권한을 부여합니다. 14개 도구를 제공합니다. 예: get_pricing, list_locations, create_account.
프로젝트 README에서 생성된 요약
ProxyCove MCP server 정보
ProxyCove는 AI agent가 170개 이상의 국가에서 주거용, 모바일 및 데이터센터 프록시를 구매하고 관리할 수 있도록 지원하는 원격 MCP server를 제공합니다. 자동화, 스크래핑 또는 테스트용 agent를 구축하는 개발자를 위해 설계된 이 server를 통해 agent는 프록시 관리의 전체 라이프사이클을 처리할 수 있습니다. agent는 create_account를 호출하여 API key를 발급받고, get_pricing으로 가격을 확인하며, 사용 가능한 위치를 조회함으로써 스스로 초기 설정을 완료할 수 있습니다.
보안 유지를 위해 agent는 민감한 결제 정보를 직접 다루지 않습니다. 대신 create_topup을 사용하여 결제 URL을 생성하며, 사용자가 해당 URL을 열어 은행 카드, 암호화폐 또는 기타 방법으로 결제합니다. 잔액이 충전되면 agent는 buy_proxy를 사용하여 연결 자격 증명을 획득할 수 있습니다. 이 server는 stateless 방식이며 streamable HTTP를 사용하므로 Claude Desktop, Cursor, ChatGPT와 같은 클라이언트와 호환됩니다. 사용자는 공개 원격 엔드포인트에 연결하거나 Docker 또는 npm을 사용하여 Node 기반 server를 로컬에 직접 호스팅할 수 있습니다.
활용 사례
- 1동적 IP 로테이션 관리개발자는 agent에게 요청당 새로운 IP를 사용하는 방식과 스티키 세션(sticky session) 방식 사이를 전환하도록 지시할 수 있습니다.
프로젝트의 README를 바탕으로 작성되었습니다. 모든 활용 사례는 해당 내용의 인용문과 대조하여 확인합니다.
ProxyCove MCP 설치 방법
형식 확인: 2026년 11월 10일Cursor에 추가Goose에 추가Claude Code에 ProxyCove MCP 설치
$ claude mcp add --transport http mcp-server https://mcp.proxycove.com/mcpCursor에 ProxyCove MCP 설치
~/.cursor/mcp.json
{
"mcpServers": {
"mcp-server": {
"url": "https://mcp.proxycove.com/mcp"
}
}
}VS Code에 ProxyCove MCP 설치
.vscode/mcp.json
{
"servers": {
"mcp-server": {
"type": "http",
"url": "https://mcp.proxycove.com/mcp"
}
}
}VS Code CLI에 ProxyCove MCP 설치
$ code --add-mcp '{"name":"mcp-server","type":"http","url":"https://mcp.proxycove.com/mcp"}'Codex에 ProxyCove MCP 설치
$ codex mcp add mcp-server --url https://mcp.proxycove.com/mcpCodex config.toml에 ProxyCove MCP 설치
~/.codex/config.toml
[mcp_servers.mcp-server] url = "https://mcp.proxycove.com/mcp"
Gemini CLI에 ProxyCove MCP 설치
$ gemini mcp add -s user --transport http mcp-server https://mcp.proxycove.com/mcpGemini settings.json에 ProxyCove MCP 설치
~/.gemini/settings.json
{
"mcpServers": {
"mcp-server": {
"url": "https://mcp.proxycove.com/mcp",
"type": "http"
}
}
}ProxyCove MCP 도구 14
README에서 감지됨get_pricinglist_locationscreate_accountget_accountcreate_topupget_payment_statusbuy_proxylist_proxiesget_credentialsextend_proxyget_usageset_rotation
| get_pricing | — | |
| list_locations | — | |
| create_account | — | |
| get_account | — | |
| create_topup | — | |
| get_payment_status | — | |
| buy_proxy | — | |
| list_proxies | — | |
| get_credentials | — | |
| extend_proxy | — | |
| get_usage | — | |
| set_rotation | — |
도구 14개 모두 보기도구 수 줄이기
link_telegramattach_recovery
| link_telegram | — | |
| attach_recovery | — |
구성
BACKEND_BASE_URLMCP_PORTMCP_SECRET_PATHPROXYCOVE_API_KEY
| 이름 | 설명 | 유형 |
|---|---|---|
| BACKEND_BASE_URL | — | |
| MCP_PORT | — | |
| MCP_SECRET_PATH | — | |
| PROXYCOVE_API_KEY | — |
자동 검사
2026년 11월 14일에 실행됨전체 보고서 →아직 인증되지 않았습니다. 서버는 80점 이상의 점수, 심각한 결함 없음, 그리고 검사에 충분한 데이터를 갖추어야 합니다. 검사 방식 · 점수를 높이기 위해 수정할 항목
- 소스 저장소 연결 및 접근 가능proxycove/mcp-server is public and reachablegithub.com/proxycove/mcp-server ↗통과
- 패키지가 이 저장소를 소스로 명시검사되지 않음
- 빌드 출처(Sigstore 증명)검사되지 않음
- 오픈 소스 라이선스 (OSI)MITspdx.org/licenses/MIT.html ↗통과
- 최근 1년 내 커밋 또는 릴리스Last commit or release 2026-09-14github.com/proxycove/mcp-server ↗통과
- OpenSSF Scorecard검사되지 않음
- 패키지 이름이 인기 패키지와 유사하지 않음검사되지 않음
- 패키지 및 해당 종속성에 중요한 보안 권고 없음검사되지 않음
- 모델에 대한 숨겨진 지침 없음14 tool descriptions and the README read; no override phrases, credential paths or hidden characters통과
- 파괴적인 도구에 라벨 표시됨No tool named like delete, drop or exec통과
- 원격 엔드포인트가 MCP 핸드셰이크에 응답initialize answered with protocol 2025-06-18 in 431 ms통과
README
GitHub에서 보기ProxyCove MCP Server
Let an AI agent buy and manage real proxies — no signup, no dashboard, no card details in the chat.
ProxyCove sells residential, mobile and datacenter proxies prepaid per GB across 170+ countries. This MCP server exposes that as 14 tools, so an agent can create its own account, hand the human a payment link, buy a proxy and get working connection credentials — all inside one conversation.
https://mcp.proxycove.com/mcp ← remote endpoint (streamable HTTP)
Status: live. The endpoint above is public — connect and use it. Anonymous calls are allowed for
get_pricing,list_locationsandcreate_account; everything else needs a key. Clients that prefer OAuth 2.1 can discover it at/.well-known/oauth-protected-resource.
Who it's for: developers building scraping / automation / testing agents, anyone whose agent needs an exit IP in a specific country, and MCP clients that want a proxy provider they can call directly instead of wrapping a REST API by hand.
What an agent can do end to end
create_account→ gets an API key (pc_live_...). No registration form, no email required.create_topup→ gets apayment_url. The human pays in the browser (SBP, bank card, crypto).buy_proxy→ getshttp://login:password@go.proxycove.com:824and starts using it.
Prices: residential $2.7/GB · mobile $3.8/GB · datacenter $1.5/GB. Traffic is prepaid and does not expire while the account is active.
Quick start
The server is remote — nothing to install. Add the endpoint to your client and (once you have a key) send it as a bearer token.
You can add the connector without a key: get_pricing, list_locations and create_account work unauthenticated. Run create_account, save the returned pc_live_... key, put it in the header, reconnect.
Claude Code
claude mcp add --transport http proxycove https://mcp.proxycove.com/mcp \
--header "Authorization: Bearer pc_live_YOUR_KEY"
Without a key yet (to call create_account first):
claude mcp add --transport http proxycove https://mcp.proxycove.com/mcp
Claude Desktop / Claude.ai (Connectors)
Settings → Connectors → Add custom connector
| Field | Value |
|---|---|
| Name | ProxyCove |
| Remote MCP server URL | https://mcp.proxycove.com/mcp |
Until OAuth ships, Claude Desktop can also reach the server through the stdio bridge, which is where the header lives:
{
"mcpServers": {
"proxycove": {
"command": "npx",
"args": [
"-y", "mcp-remote",
"https://mcp.proxycove.com/mcp",
"--header", "Authorization: Bearer pc_live_YOUR_KEY"
]
}
}
}
ChatGPT (developer mode)
Settings → Connectors → Advanced → enable Developer mode, then Create:
| Field | Value |
|---|---|
| Name | ProxyCove |
| MCP server URL | https://mcp.proxycove.com/mcp |
| Authentication | Access token / API key → paste pc_live_YOUR_KEY |
Cursor
~/.cursor/mcp.json (global) or .cursor/mcp.json (per project):
{
"mcpServers": {
"proxycove": {
"url": "https://mcp.proxycove.com/mcp",
"headers": {
"Authorization": "Bearer pc_live_YOUR_KEY"
}
}
}
}
Codex CLI
~/.codex/config.toml:
[mcp_servers.proxycove]
url = "https://mcp.proxycove.com/mcp"
bearer_token_env_var = "PROXYCOVE_API_KEY"
export PROXYCOVE_API_KEY=pc_live_YOUR_KEY
Any other MCP client
{
"mcpServers": {
"proxycove": {
"type": "http",
"url": "https://mcp.proxycove.com/mcp",
"headers": {
"Authorization": "Bearer pc_live_YOUR_KEY"
}
}
}
}
Transport is streamable HTTP, stateless — POST only, one JSON-RPC request per call, no SSE stream and no session id. GET/DELETE on the endpoint return 405.
Agent skill
Beyond the tool descriptions, this repo ships an agent skill that tells an agent which tool to reach for: how to pick a proxy type for a job, when a sticky session is required, what each error code actually means, and the rules that keep the human in control — never handle payment details, quote the price before spending, save the key.
npx skills add proxycove/mcp-server
Tools
| Tool | What it does | API key |
|---|---|---|
get_pricing |
Price per GB (USD) for residential / mobile / datacenter | no |
list_locations |
Countries available for a given proxy type | no |
create_account |
Creates an account with no signup form, returns a pc_live_... key |
no |
get_account |
Balance (USD), attached email, number of active proxies | yes |
create_topup |
Creates an invoice, returns payment_url for the human |
yes |
get_payment_status |
Invoice status: pending / paid / cancelled |
yes |
buy_proxy |
Buys a proxy from the balance, returns connection credentials | yes |
list_proxies |
All proxies with remaining traffic and credentials | yes |
get_credentials |
Connection string for one proxy | yes |
extend_proxy |
Adds prepaid GB to an existing proxy (credentials unchanged) | yes |
get_usage |
Live used / remaining traffic for one proxy | yes |
set_rotation |
Rotate every request ↔ sticky IP for 1–120 minutes | yes |
link_telegram |
Returns a code to link the account to the Telegram bot (second way back in if the key is lost) | yes |
attach_recovery |
Attaches an email so the human can log in on the website | yes |
Read-only tools carry readOnlyHint. No tool deletes anything — there is no destructive operation in this server, and no tool can move money out of the account.
Connection model
Every proxy is reachable at go.proxycove.com:
| Port | Behaviour |
|---|---|
824 |
New IP on every request |
10000 |
Sticky IP, held for the configured 1–120 minutes |
set_rotation switches a proxy between the two modes; the login and password stay the same.
After
buy_proxy, wait ~5 seconds before the first request. The country filter takes a moment to propagate upstream, and an immediate first request may exit from another country.
Authentication
- The account API key looks like
pc_live_...and is sent asAuthorization: Bearer pc_live_.... create_accountissues one. The three no-auth tools exist precisely so an agent can bootstrap: check prices, check countries, create the account — then the human stores the key in the connector config.- The MCP server holds no state of its own. It forwards your
Authorizationheader to the ProxyCove REST API and returns the JSON response. - Calling an authenticated tool without a key returns a structured
no_api_keyerror explaining what to do — not a crash. - OAuth 2.1 + PKCE is coming next, which will remove the manual header step for clients that support it. The bearer key will keep working.
Payments: the agent never touches card data
This is a hard boundary, enforced by the tool design:
create_topupreturns apayment_url. That is all the agent gets.- The agent gives the URL to the human, who opens it in their own browser and pays there.
- Methods:
sbp(Russian instant bank transfer),card_ru,card_international,crypto,crypto_cryptomus. Minimum top-up $1.50. - No tool accepts a card number, CVV, or any payment credential. There is no field for one anywhere in the schema.
- The agent then polls
get_payment_statusuntilpaidand continues.
Purchases (buy_proxy, extend_proxy) spend the prepaid balance only. An agent cannot spend money that the human has not already deposited.
Self-hosting / running locally
The server is a thin, stateless wrapper over the public ProxyCove REST API — roughly 200 lines of Node with no database, no cache and no persistence. Self-host it if you want to audit the traffic, pin a version, or run it inside your own network.
Requirements: Node 20+ (or Docker).
git clone https://github.com/proxycove/mcp-server.git
cd mcp-server
npm install
export BACKEND_BASE_URL=https://proxycove.com
export MCP_PORT=4010
export MCP_SECRET_PATH=/mcp
npm start
# → http://localhost:4010/mcp
Docker:
docker build -t proxycove-mcp .
docker run -d --name proxycove-mcp \
-p 4010:4010 \
-e BACKEND_BASE_URL=https://proxycove.com \
-e MCP_PORT=4010 \
-e MCP_SECRET_PATH=/mcp \
proxycove-mcp
Environment variables
| Variable | Default | Purpose |
|---|---|---|
MCP_PORT |
4010 |
Port the HTTP server listens on |
MCP_SECRET_PATH |
/mcp |
Path the MCP endpoint is mounted at |
BACKEND_BASE_URL |
http://backend:5000 |
Base URL of the ProxyCove API; use https://proxycove.com when self-hosting |
PUBLIC_API_INVITE_CODE |
(empty) | Optional invite code forwarded by create_account |
Configuration is entirely from env — there is no config file and no secret baked into the image.
GET /healthz returns { "ok": true, "service": "proxycove-mcp" }.
Point your client at your own instance the same way:
{
"mcpServers": {
"proxycove": {
"type": "http",
"url": "http://localhost:4010/mcp",
"headers": { "Authorization": "Bearer pc_live_YOUR_KEY" }
}
}
}
REST API (non-MCP integrations)
Everything the MCP server does is available directly over HTTP — same endpoints, same key:
- Base URL:
https://proxycove.com/api/v1 - OpenAPI spec:
https://proxycove.com/api/v1/openapi.json
curl https://proxycove.com/api/v1/pricing
curl https://proxycove.com/api/v1/account \
-H "Authorization: Bearer pc_live_YOUR_KEY"
Use this if you are writing a normal client, a LangChain/LlamaIndex tool, a CI job, or anything that is not an MCP host.
Security
- The API key is shown once, at
create_account. Save it immediately — ProxyCove cannot show it again. - A key can be revoked at any time from the account on proxycove.com or by writing to support. Revoking it kills agent access instantly; the balance and proxies stay.
- Run
attach_recoveryorlink_telegramearly. Without a recovery channel on the account, a lost key means a lost balance. - Treat
pc_live_...like a password: it is a spending credential. Never paste it into a shared chat, a public repo, or an issue on this tracker. - Prefer env-var indirection (
bearer_token_env_var,${VAR}substitution) over literal keys in config files that get committed. - Found a vulnerability, or something that lets an agent spend more than it should? Email support@proxycove.com — please do not open a public issue for security reports.
Contributing
Issues and pull requests are welcome — bug reports, client-config recipes for MCP hosts not covered above, and tool-description improvements especially. The tool schemas are the product surface here; if a description misled your agent, that is a bug worth filing.
License
MIT © ProxyCove
Website: proxycove.com · MCP endpoint: https://mcp.proxycove.com/mcp · REST API: https://proxycove.com/api/v1 · Support: support@proxycove.com
ProxyCove MCP 질문
ProxyCove MCP를 Claude Code에 추가하려면 어떻게 하나요?
터미널에서 claude mcp add --transport http mcp-server https://mcp.proxycove.com/mcp를 실행합니다. 모든 프로젝트에서 사용할 수 있게 하려면 --scope user를 추가합니다.
ProxyCove MCP를 Cursor에 추가하려면 어떻게 하나요?
~/.cursor/mcp.json를 열고 mcpServers 아래에 서버를 추가합니다. 위 설치 섹션에 표시된 Cursor 구성을 사용합니다.
ProxyCove MCP는 어떤 도구를 제공하나요?
14개 도구를 제공합니다. 예: get_pricing, list_locations, create_account, get_account, create_topup.
API key를 분실하면 어떻게 되나요?
복구 이메일을 등록하거나 Telegram bot을 연결하지 않은 경우, 키를 분실하면 잔액에 대한 접근 권한도 상실됩니다. 초기 단계에서 attach_recovery 또는 link_telegram을 사용하는 것을 권장합니다.
프록시 트래픽에 만료 기간이 있나요?
아니요, 트래픽은 선불 방식이며 계정이 활성 상태인 한 유효합니다.