ipvolt Proxy Toolkit MCP server

ipvolt Proxy Toolkit

An MCP server for finding reviewed proxy documentation, generating tested configuration examples and diagnosing structured proxy failures. The public tools run locally against a bundled catalog. They do not need an API key or access to an ipvolt proxy account.

The toolkit is separate from ipvolt's commercial proxy service, which is not open yet. It does not provision proxies, buy traffic, access account data or configure another agent's network route.

Availability

The published npm version 0.1.0 and public hosted service provide four tools using a bundled public catalog. Check release status for verified npm availability, the hosted endpoint and registry listings. Source builds work independently of those distribution channels. Registry metadata in server.json describes the intended release and is not evidence that a channel is live.

Tools

For example, search with {"query":"curl proxy","topic":"setup"}, then retrieve {"documentId":"/guides/curl-proxy-setup"}. Generate a synchronous HTTPX example with {"client":"httpx","version":"0.28.1"}. Diagnose a proxy authentication failure with {"client":"httpx","version":"0.28.1","phase":"proxy_connect","status":407}. A 407 observation points to proxy authentication; it does not establish whether a password, account state or access policy is responsible.

Use short topic queries and structured observations. Supply credentials only through your local environment when you execute a generated example or enable the local diagnostic. Never send credentials, private URLs or raw logs as tool arguments.

Build and connect locally

Requires Node.js 24 or newer and npm. From the repository directory:

npm ci
npm run build
npm run check:content
node dist/transports/stdio.js --version

For a client that accepts a mcpServers configuration, use an absolute path to the compiled entry:

{
  "mcpServers": {
    "ipvolt": {
      "command": "node",
      "args": ["/absolute/path/to/proxy-toolkit-mcp/dist/transports/stdio.js"]
    }
  }
}

The default local server exposes four tools, sends no telemetry and makes no network requests. A client may send tool results to its own model provider. The server cannot control that client's data handling.

For the npm distribution, use the pinned package version after confirming its availability in release status:

{
  "mcpServers": {
    "ipvolt": {
      "command": "npx",
      "args": ["--yes", "@ipvolt/proxy-toolkit-mcp@0.1.0"]
    }
  }
}

Exact real-application and protocol results are recorded in client compatibility.

Tested configuration examples

Shortened. The full README is on GitHub.