# ipvolt Proxy Toolkit (remote · mcp.ipvolt.com)

Proxy guides, tested configurations and error diagnostics, with an optional local route check.

- Trust score: 74/100 (medium)
- Change this week: +4
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-09-25

## Components

- remote · `mcp.ipvolt.com`: 74/100 (this document), [markdown](https://verifymcp.io/servers/ipvolt-proxy-toolkit/mcp.md), [page](https://verifymcp.io/servers/ipvolt-proxy-toolkit/mcp)
- npm · `@ipvolt/proxy-toolkit-mcp`: 73/100, [markdown](https://verifymcp.io/servers/ipvolt-proxy-toolkit/ipvolt-proxy-toolkit-mcp.md), [page](https://verifymcp.io/servers/ipvolt-proxy-toolkit/ipvolt-proxy-toolkit-mcp)

## Channel facts

- Endpoint: `https://mcp.ipvolt.com/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `0.1.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-09-25.

- **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. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one.
  - 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**: 69/100
  - AI-judged instruction clarity (good).
  - Tool/resource definitions use about 426 tokens (~106/item across 4 items; 4 tools + 0 resources), lean.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 37/100
  - Stability observed for 11 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 83/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 42% of tool parameters carry a description.
  - Structured output schemas are declared (100% of tools); any adoption earns full credit.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 4 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 current MCP spec version (2026-07-28).

## Install

### How do I install the ipvolt Proxy Toolkit MCP server?

ipvolt Proxy Toolkit is a hosted endpoint at https://mcp.ipvolt.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 ipvolt-proxy-toolkit 'https://mcp.ipvolt.com/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "ipvolt-proxy-toolkit": {
      "url": "https://mcp.ipvolt.com/mcp"
    }
  }
}
```

### VS Code

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

### Codex

```toml
[mcp_servers.ipvolt-proxy-toolkit]
url = "https://mcp.ipvolt.com/mcp"
```

### opencode

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

### OpenClaw

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

### Hermes

```yaml
mcp_servers:
  ipvolt-proxy-toolkit:
    url: "https://mcp.ipvolt.com/mcp"
```

### Netclaw

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

### Vellum

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

### Other

```json
{
  "mcpServers": {
    "ipvolt-proxy-toolkit": {
      "type": "http",
      "url": "https://mcp.ipvolt.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-09-25 (score 74, +1)

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

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

### 2026-09-21 (score 72, +1)

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

### 2026-09-19 (score 71, +1)

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

### 2026-09-16 (score 70, +1)

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

### 2026-09-15 (score 69, 0)

- [functional improvement] Stability: unverified → 0.03

### 2026-09-14 (score 69)

First indexed and scored.

## MCP tools (4)

### `search_proxy_docs` (~60 tokens)

Search reviewed proxy documentation

Find reviewed ipvolt public guides and articles. Returns canonical document IDs, excerpts and content revision. Submit a short topic query, never credentials or logs.

Input parameters:

- `limit` (integer)
- `query` (string, required)
- `topic` (string)

Output parameters:

- `provenance` (object)
- `results` (array)

### `get_proxy_doc` (~63 tokens)

Read a reviewed proxy document

Read a bounded chunk or named section using a document ID returned by search_proxy_docs. Follow nextCursor to continue; cursors are bound to the content revision.

Input parameters:

- `cursor` (string)
- `documentId` (string, required)
- `section` (string)

Output parameters:

- `chunk` (number)
- `document` (object)
- `markdown` (string)
- `nextCursor` (string|null)
- `provenance` (object)
- `sections` (array)
- `totalChunks` (number)

### `generate_proxy_config` (~111 tokens)

Generate a tested proxy configuration

Generate an HTTPS GET example for an exact tested curl, Requests, HTTPX or Playwright APIRequestContext version. Credentials and target are local environment placeholders. It does not execute the example or configure other agent tools.

Input parameters:

- `client` (string, required): Client whose exact tested configuration to generate.
- `protocol` (string): HTTP proxy with HTTPS CONNECT. Other proxy protocols are not tested.
- `timeoutSeconds` (integer)
- `version` (string, required): Exact tested version matching the client. Other versions are unsupported.

Output parameters:

- `behavior` (object)
- `client` (string)
- `code` (string)
- `environment` (array)
- `interface` (string)
- `language` (string)
- `limitations` (array)
- `protocol` (string)
- `sources` (array)
- `summary` (string)
- `templateRevision` (string)
- `testedRuntime` (string)
- `version` (string)

### `diagnose_proxy_error` (~192 tokens)

Diagnose a proxy error

Use structured client/version, phase, status or exception observations to identify possible causes and the next check. Returns uncertainty and retry boundaries. Do not send raw logs, URLs or credentials.

Input parameters:

- `client` (string, required)
- `exception` (string): Normalized category, not raw exception text. HTTPX ConnectError alone does not establish a TLS error.
- `method` (string)
- `phase` (string, required)
- `requestMayHaveBeenSent` (boolean): Whether this target request may already have reached the application. Omit when unknown.
- `responseSource` (string): Use target/proxy only when established by response provenance, not merely the status code.
- `retryAfterSeconds` (integer): Parsed bounded Retry-After delay, if actually observed. Never submit the raw header.
- `status` (integer): Observed HTTP status; identify its responding layer separately.
- `version` (string, required)

Output parameters:

- `candidates` (array)
- `client` (string)
- `evidence` (object)
- `retry` (object)
- `rulesRevision` (string)
- `sources` (array)
- `summary` (string)
- `uncertainty` (array)
- `version` (string)

## Diagnostics

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

## Score history

- 2026-09-25: 74
- 2026-09-24: 73
- 2026-09-23: 73
- 2026-09-22: 72
- 2026-09-21: 72
- 2026-09-20: 71
- 2026-09-19: 71
- 2026-09-18: 70
- 2026-09-17: 70
- 2026-09-16: 70
- 2026-09-15: 69
- 2026-09-14: 69

## Common questions

### What is the ipvolt Proxy Toolkit MCP server?

ipvolt Proxy Toolkit is an MCP server listed in the public MCP registry as io.github.ipvolt/proxy-toolkit. Proxy guides, tested configurations and error diagnostics, with an optional local route check. This page covers its hosted endpoint (https://mcp.ipvolt.com/mcp).

### Is the ipvolt Proxy Toolkit MCP server safe to use?

ipvolt Proxy Toolkit scores 74 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 ipvolt Proxy Toolkit MCP server expose?

ipvolt Proxy Toolkit exposes 4 tools: search_proxy_docs, get_proxy_doc, generate_proxy_config, diagnose_proxy_error. Their descriptions and schemas cost roughly 426 tokens of context every time the server is loaded.

### Does the ipvolt Proxy Toolkit MCP server require authentication?

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

### Is the ipvolt Proxy Toolkit MCP server still maintained?

ipvolt Proxy Toolkit is still listed as active in the MCP registry. We last reached this channel on 25 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

## Links

- Remote endpoint: https://mcp.ipvolt.com/mcp
- Repository: https://github.com/ipvolt/proxy-toolkit-mcp
- Website: https://ipvolt.com/
- Changelog RSS feed: https://verifymcp.io/servers/ipvolt-proxy-toolkit/mcp.xml
- Changelog JSON feed: https://verifymcp.io/servers/ipvolt-proxy-toolkit/mcp.json
- HTML version of this page: https://verifymcp.io/servers/ipvolt-proxy-toolkit/mcp