# HProxy (remote · mcp.hproxy.com)

Free proxy list, live proxy checker and IP lookup for AI agents. No key, nothing to install.

- Trust score: 86/100 (high trust)
- Change this week: 0
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-06

## Components

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

## Channel facts

- Endpoint: `https://mcp.hproxy.com/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `1.0.1`

## 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-06.

- **Endpoint Security**: 74/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.
  - 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**: 79/100
  - AI-judged instruction clarity (excellent).
  - Context-footprint check failed: tool/resource definitions use about 403 tokens (~134/item across 3 items; 3 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 100/100
  - No destabilizing schema changes in the last 30 days.
- **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**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 3 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 4 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 HProxy MCP server?

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

### Cursor

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

### VS Code

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

### Codex

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

### opencode

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

### OpenClaw

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

### Hermes

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

### Netclaw

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

### Vellum

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

### Other

```json
{
  "mcpServers": {
    "com-hproxy-mcp": {
      "type": "http",
      "url": "https://mcp.hproxy.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-11-06 (score 86, 0)

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

### 2026-11-05 (score 86, +1)

- [security] Stability: 0.97 → pass

### 2026-11-04 (score 85, −1)

- [functional] Stability: pass → 0.97

### 2026-11-03 (score 86, 0)

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

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

- [security] Stability: 0.97 → pass

### 2026-10-28 (score 85, +1)

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

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

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

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

## MCP tools (3)

### `proxy_list` (~183 tokens)

Free proxy list

Fetch live free proxies from HProxy's public pool, re-checked around the clock. No key. Returns ip, port, protocols, anonymity, country, city, network, latency and 24h uptime per proxy. Use this when the user wants free proxies to test with. Free proxies are public and come and go, so check them before relying on one.

Input parameters:

- `anonymity` (string): Only proxies of exactly this anonymity grade: elite hides both your address and the fact that a proxy is used, anonymous hides your address, transparent passes it on.
- `country` (string): ISO 3166 alpha-2 country code, e.g. 'de'. Omit for every country.
- `limit` (integer): How many to return. The full list is thousands; ask for what you need.
- `protocol` (string): Only proxies speaking this protocol.

### `proxy_check` (~96 tokens)

Proxy checker

Run a real live test on one or more proxies: is it alive, which protocols it speaks, its anonymity grade, latency and location. No key. Each check opens a real connection, so a dead proxy can take a few seconds. Up to 25 per call.

Input parameters:

- `proxies` (array, required): Proxies as ip:port, e.g. ['203.0.113.7:1080']. Up to 25.

### `ip_lookup` (~62 tokens)

IP lookup

Look up any public IP address: country, region, city, coordinates, timezone, ASN and the network that runs it. No key. Up to 50 per call.

Input parameters:

- `ips` (array, required): IPv4 or IPv6 addresses. One is the common case.

## Diagnostics

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

## Score history

- 2026-11-06: 86
- 2026-11-05: 86
- 2026-11-04: 85
- 2026-11-03: 86
- 2026-11-02: 86
- 2026-11-01: 86
- 2026-10-31: 86
- 2026-10-30: 86
- 2026-10-29: 85
- 2026-10-28: 85
- 2026-10-27: 84
- 2026-10-26: 84
- 2026-10-25: 83
- 2026-10-24: 83
- 2026-10-23: 83
- 2026-10-22: 82
- 2026-10-21: 82
- 2026-10-20: 81
- 2026-10-19: 81
- 2026-10-18: 80
- 2026-10-17: 80
- 2026-10-16: 79
- 2026-10-15: 79
- 2026-10-14: 78
- 2026-10-13: 78
- 2026-10-12: 77
- 2026-10-10: 76
- 2026-10-06: 75
- 2026-10-04: 74
- 2026-10-03: 73

## Common questions

### What is the HProxy MCP server?

HProxy is an MCP server listed in the public MCP registry as com.hproxy/mcp. Free proxy list, live proxy checker and IP lookup for AI agents. No key, nothing to install. This page covers its hosted endpoint (https://mcp.hproxy.com/mcp).

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

HProxy scores 86 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 HProxy MCP server expose?

HProxy exposes 3 tools: proxy_list, proxy_check, ip_lookup. Their descriptions and schemas cost roughly 341 tokens of context every time the server is loaded.

### Does the HProxy MCP server require authentication?

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

### Is the HProxy MCP server still maintained?

HProxy is still listed as active in the MCP registry. We last reached this channel on 6 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 HProxy MCP server?

VerifyMCP ran 13 checks on HProxy, 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://mcp.hproxy.com/mcp
- Repository: https://github.com/hproxy-com/hproxy-mcp
- Website: https://hproxy.com/tools/ai
- Changelog RSS feed: https://verifymcp.io/servers/com-hproxy-mcp/mcp.xml
- Changelog JSON feed: https://verifymcp.io/servers/com-hproxy-mcp/mcp/changelog.json
- Trust report (JSON): https://verifymcp.io/servers/com-hproxy-mcp/mcp.json
- HTML version of this page: https://verifymcp.io/servers/com-hproxy-mcp/mcp