# TrueProxies [Health: Active]

**Category:** 💻 Developer Tools  
**Repository:** https://github.com/trueproxies-com/trueproxies-mcp  
**GitHub Stars:** 1  
**Views:** 0  
**Installs:** 0  
**Upvotes:** 0  
**Directory Page:** https://allmcps.com/mcp/trueproxies

## Description
Plans, services, usage, invoices, endpoints and connection checks for your TrueProxies account

## Tools
Capabilities this server exposes over MCP:

- **list_plans** — none
- **get_account** — services:read
- **list_services** — services:read
- **get_service** — services:read
- **get_traffic_used** — services:read
- **get_live_traffic** — services:read
- **get_usage_history** — services:read
- **list_invoices** — billing:read
- **get_invoice** — billing:read
- **generate_endpoints** — proxy:read
- **check_connection** — proxy:read
- **list_trusted_ips** — proxy:read

## Claude Desktop Quick Installation
Remote MCP endpoint (confidence: high). Install path detected from listing signals. Add as a URL/SSE server in your client:

```json
"mcpServers": {
  "trueproxies": {
    "url": "https://mcp.trueproxies.com/mcp"
  }
}
```

## Documentation

## What the TrueProxies MCP server does

The TrueProxies MCP server gives an MCP-compatible client read access to selected parts of a TrueProxies account. It can retrieve available plans and pricing without authentication, then use an API key to inspect account information, proxy services, traffic, usage history, invoices, and trusted IPs.

The server also handles two proxy-oriented tasks. It can produce connection lines for a service, including the username and password needed to connect, and it can send one request through that service to report the request result and exit IP. The connection test uses a small amount of traffic and may start an unused free trial.

Operations are intentionally limited. The server does not buy plans, make payments, change a proxy password, or modify trusted IP addresses. All tools are read-only except for the connection check, which performs the described network request.

## How it works

The hosted endpoint is available at `https://mcp.trueproxies.com/mcp` and accepts a bearer token containing a TrueProxies API key. For each hosted call, the service forwards the key to `api.trueproxies.com`. The hosted service keeps no account data, and its logs contain the tool name, status, request ID, and duration rather than arguments, results, or keys.

Hosted traffic passes through Cloudflare, so the API key and generated proxy endpoints pass through that service while in transit. Running the TrueProxies MCP server locally avoids this hosted path. Local operation is available either through a Docker image or a Go-installed executable using MCP stdio transport.

## Setup and configuration

Create an API key in the TrueProxies dashboard under API keys, then expose it to the process as `TRUEPROXIES_API_KEY`. For account and billing inspection, grant `services:read` and `billing:read`. Add `proxy:read` only when the client needs to generate endpoints, test connections, or list trusted IPs; generated endpoints contain the proxy password.

The hosted setup uses an HTTP MCP registration with an `Authorization: Bearer` header. A local Docker setup builds the repository image, then runs it interactively with the API key passed into the container. A Go setup installs the module and starts `trueproxies-mcp stdio` with the same environment variable.

## Tools and capabilities

The TrueProxies MCP server exposes these capabilities:

- List plans, traffic packs, prices, cities, and free-trial availability.
- Retrieve the account and list or inspect proxy services.
- Check total traffic used, remaining traffic, current download and upload speeds, and daily usage.
- Review connection success, traffic, and connection errors over 24-hour, 7-day, or 30-day periods.
- List invoices or retrieve an individual invoice.
- Generate proxy connection lines for a service.
- Send one request through a service and return its result and exit IP.
- List trusted IPs associated with a service.

Permissions are attached to individual tools. Plan discovery needs no API-key scope, account and service data use `services:read`, invoice tools use `billing:read`, and endpoint, connection, and trusted-IP tools use `proxy:read`.

## Limitations and notes

Treat generated endpoints as credentials because they include a proxy username and password. Restrict `proxy:read` access when an agent only needs reporting or billing information. The connection-check tool is not a passive lookup: it sends a request through the service, consumes some traffic, and can trigger an unused free trial. The server cannot perform purchases, payments, password changes, or trusted-IP changes.

_Full upstream README: https://allmcps.com/mcp/trueproxies/readme_