# Proxmint (remote · proxmint.com)

Fetch pages through your proxies, plus proxy lines, balance, usage and pricing for Proxmint

- Trust score: 80/100 (high trust)
- Change this week: +3
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-05

## Components

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

## Channel facts

- Endpoint: `https://proxmint.com/api/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `1.1.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**: 80/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - No authorisation is required to call this server. Nothing on it is marked destructive, but we can't show that an anonymous caller can only read: full credit needs the server to list at least one tool and every tool to be verifiably read-only. We use a best-effort check of tool names and descriptions to tell read-only tools from tools that change things, so some genuinely read-only tools may not get full credit. Names that start with a read verb (get, list, read, search and similar) and accurate readOnlyHint annotations help. Meet that to earn full credit, or require authorisation.
  - HTTPS is enforced; there's no plaintext access path.
  - The HSTS (Strict-Transport-Security) header is present.
  - 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**: 68/100
  - AI-judged instruction clarity (good).
  - Context-footprint check failed: tool/resource definitions use about 842 tokens (~140/item across 6 items; 6 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 80/100
  - Stability observed for 24 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; "check_connection" implies "send" and declares readOnlyHint instead, contradicting what its own name says it does.
  - An AI judge read all 7 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 60/100
  - Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28.

## Install

### How do I install the Proxmint MCP server?

Proxmint is a hosted endpoint at https://proxmint.com/api/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-proxmint-mcp 'https://proxmint.com/api/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "com-proxmint-mcp": {
      "url": "https://proxmint.com/api/mcp"
    }
  }
}
```

### VS Code

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

### Codex

```toml
[mcp_servers.com-proxmint-mcp]
url = "https://proxmint.com/api/mcp"
```

### opencode

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

### OpenClaw

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

### Hermes

```yaml
mcp_servers:
  com-proxmint-mcp:
    url: "https://proxmint.com/api/mcp"
```

### Netclaw

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

### Vellum

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

### Other

```json
{
  "mcpServers": {
    "com-proxmint-mcp": {
      "type": "http",
      "url": "https://proxmint.com/api/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-04 (score 80, +1)

No change was recorded against any check on this day. Stability & Change Management went from 73 to 77. That category is still filling its 30-day observation window: 22 days of observed history at the previous scan, 23 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-11-01 (score 79, +1)

- [functional] Server version: 1.0.0 → 1.1.0

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

- [security] Tool “get_account” rewrote its description, which is the text the model reads
- [cosmetic] “generate_proxies” reworded the description of “format”

### 2026-10-30 (score 78, +1)

- [security] The server rewrote its instructions, which are the text every model session reads
- [security] Tool “get_pricing” rewrote its description, which is the text the model reads

### 2026-10-29 (score 77, +1)

No change was recorded against any check on this day. Stability & Change Management went from 53 to 57. That category is still filling its 30-day observation window: 16 days of observed history at the previous scan, 17 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-10-26 (score 76, +1)

No change was recorded against any check on this day. Stability & Change Management went from 43 to 47. That category is still filling its 30-day observation window: 13 days of observed history at the previous scan, 14 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-10-24 (score 75, +1)

No change was recorded against any check on this day. Stability & Change Management went from 37 to 40. That category is still filling its 30-day observation window: 11 days of observed history at the previous scan, 12 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-10-22 (score 74, +1)

No change was recorded against any check on this day. Stability & Change Management went from 30 to 33. That category is still filling its 30-day observation window: 9 days of observed history at the previous scan, 10 at this one. The score rises as the window fills, whether or not the server changes.

## MCP tools (6)

### `get_pricing` (~51 tokens)

Pack prices

Regular Proxmint pack prices for each proxy product: pack size, price and price per GB. Packs are prepaid and never expire. No sign-in needed.

Input parameters:

- `product` (string): Only this product

### `get_account` (~42 tokens)

Account

Wallet balance and every product on the account, with its status, bandwidth used and left, and the proxy host, ports and username. The proxy password is left out.

### `get_usage` (~52 tokens)

Usage

Bandwidth and requests per product per UTC day, oldest first, with totals per product. Days with no traffic are left out.

Input parameters:

- `days` (integer): Days back from today, today included (1-90)

### `generate_proxies` (~284 tokens)

Generate proxy lines

Build proxy lines for one product, with optional location targeting and sticky sessions. Rotating lines get a new IP on every request; each sticky line keeps one IP for sticky_minutes (1-120). The lines include the proxy password.

Input parameters:

- `asn` (string): Carrier or ISP network number (ASN), digits only. Needs country.
- `city` (string): City, e.g. newyork. Needs country.
- `count` (integer): Number of sticky lines, each with its own IP (rotating returns one line)
- `country` (string): ISO 3166 alpha-2 country code, e.g. us. Leave every location field empty to use the targeting saved in the dashboard.
- `format` (string): url: protocol://user:pass@host:port. host:port:user:pass: the colon format many tools import
- `product` (string, required): Proxy product
- `protocol` (string): http (also carries HTTPS) or socks5
- `session` (string): rotating: a new IP on every request. sticky: each line keeps one IP for sticky_minutes
- `state` (string): State or region, e.g. california. Needs country.
- `sticky_minutes` (integer): How long each sticky line keeps its IP
- `zip` (string): ZIP or postal code. Needs country.

### `check_connection` (~91 tokens)

Check connection

Send one request through a product's proxy and report the exit IP, the country Cloudflare sees it in, and the time taken. Uses a few kilobytes of the product's bandwidth.

Input parameters:

- `country` (string): ISO 3166 alpha-2 country code, e.g. us. Leave every location field empty to use the targeting saved in the dashboard.
- `product` (string, required): Proxy product

### `fetch_url` (~172 tokens)

Fetch a page

Fetch one web page through a product's proxy, so the request leaves from that product's IPs and targeting: status, final URL (up to 5 redirects), title, and the page as readable text or raw HTML, cut at 50,000 characters. Each call gets a new exit IP. Uses the product's bandwidth for the bytes transferred; binary files are not read.

Input parameters:

- `country` (string): ISO 3166 alpha-2 country code, e.g. us. Leave every location field empty to use the targeting saved in the dashboard.
- `format` (string): text: readable text, with scripts, styles and tags removed. html: the raw markup
- `product` (string, required): Proxy product
- `url` (string, required): The page to fetch: an http or https URL

## Diagnostics

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

## Score history

- 2026-11-05: 80
- 2026-11-04: 80
- 2026-11-03: 79
- 2026-11-02: 79
- 2026-11-01: 79
- 2026-10-31: 78
- 2026-10-30: 78
- 2026-10-29: 77
- 2026-10-28: 76
- 2026-10-27: 76
- 2026-10-26: 76
- 2026-10-25: 75
- 2026-10-24: 75
- 2026-10-23: 74
- 2026-10-22: 74
- 2026-10-21: 73
- 2026-10-20: 73
- 2026-10-19: 72
- 2026-10-18: 72
- 2026-10-17: 71
- 2026-10-16: 71
- 2026-10-15: 70
- 2026-10-14: 70
- 2026-10-13: 69
- 2026-10-12: 69

## Common questions

### What is the Proxmint MCP server?

Proxmint is an MCP server listed in the public MCP registry as com.proxmint/mcp. Fetch pages through your proxies, plus proxy lines, balance, usage and pricing for Proxmint. This page covers its hosted endpoint (https://proxmint.com/api/mcp).

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

Proxmint scores 80 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 Proxmint MCP server expose?

Proxmint exposes 6 tools: get_pricing, get_account, get_usage, generate_proxies, check_connection, fetch_url. Their descriptions and schemas cost roughly 692 tokens of context every time the server is loaded.

### Does the Proxmint MCP server require authentication?

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

### Is the Proxmint MCP server still maintained?

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

### What did VerifyMCP test on the Proxmint MCP server?

VerifyMCP ran 13 checks on Proxmint, covering TLS certificate, Authorization, HTTPS, HSTS header and 9 more. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.

## Links

- Remote endpoint: https://proxmint.com/api/mcp
- Repository: https://github.com/proxmint/mcp
- Website: https://proxmint.com/docs/mcp
- Changelog RSS feed: https://verifymcp.io/servers/com-proxmint-mcp/api-mcp.xml
- Changelog JSON feed: https://verifymcp.io/servers/com-proxmint-mcp/api-mcp/changelog.json
- Trust report (JSON): https://verifymcp.io/servers/com-proxmint-mcp/api-mcp.json
- HTML version of this page: https://verifymcp.io/servers/com-proxmint-mcp/api-mcp