Prototype · Preview: every server in the official registry, synced every 30 minutes. Reviews and accounts come in a later step.
PopNx MCPMCP servers for people who use AI · explained in plain words

ipvolt Proxy Toolkit

by ipvoltversion 0.1.1i★ –iComputer or cloud
Registry nameio.github.ipvolt/proxy-toolkit

Install

Overview

Description from the maker (original English)

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

PopNx MCP’s three pillars

These three are never merged into one score: opinions, measurements and popularity are different things.

What you can do with it

We have not written a plain-language summary for this one yet. Below are the facts we read from the registry.

  • Connection: Computer or cloud
  • Transport: stdio, Streamable HTTP
  • Category: Other
  • You need to fill in: IPVOLT_PROXY_URL

Install

Pick the AI app you use, then copy the settings.

Before you install

  • Basic checks: 1 of 1 passed
  • Runs on the maker’s server: what you ask it goes through their server.
  • You fill in yourself: IPVOLT_ENABLE_ROUTE_CHECK, IPVOLT_PROXY_URL

Values marked secret are keys to your account. Never share them or paste them into a chat.

You need

  • Runs in the cloudNothing to install; it connects over the internet
  • npmNode.js installed (for the npx command)

Which app do you use?

Pick your app above. We remember it, so next time the button says “Install in …”.

Works in Claude on the web, desktop and mobile:

  1. Open Settings → Connectors
  2. Press Add custom connector
  3. Paste the address below and press Add
  4. If it asks you to sign in, sign in with the maker
SettingsConnectors1+ Add2https://…3
https://mcp.ipvolt.com/mcp

Or run it on your computer

Open Claude Desktop → Settings → Developer → Edit Config, and paste this into claude_desktop_config.json

{
  "mcpServers": {
    "proxy-toolkit": {
      "command": "npx",
      "args": [
        "-y",
        "@ipvolt/proxy-toolkit-mcp"
      ],
      "env": {
        "IPVOLT_ENABLE_ROUTE_CHECK": "your-value",
        "IPVOLT_PROXY_URL": "your-value"
      }
    }
  }
}

Run this in your terminal

claude mcp add --transport http proxy-toolkit https://mcp.ipvolt.com/mcp

Or run it on your computer

claude mcp add proxy-toolkit --env IPVOLT_ENABLE_ROUTE_CHECK=your-value --env IPVOLT_PROXY_URL=your-value -- npx -y @ipvolt/proxy-toolkit-mcp

Fill in the empty values before running it.

Open in Cursor

Or copy the settings yourself

Paste into .cursor/mcp.json in your project, or ~/.cursor/mcp.json

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

Or run it on your computer

Open in Cursor

Or copy the settings yourself

Paste into .cursor/mcp.json in your project, or ~/.cursor/mcp.json

{
  "mcpServers": {
    "proxy-toolkit": {
      "command": "npx",
      "args": [
        "-y",
        "@ipvolt/proxy-toolkit-mcp"
      ],
      "env": {
        "IPVOLT_ENABLE_ROUTE_CHECK": "your-value",
        "IPVOLT_PROXY_URL": "your-value"
      }
    }
  }
}

Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.

Open in VS Code

Or copy the settings yourself

Paste into .vscode/mcp.json in your project

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

Or run it on your computer

Open in VS Code

Or copy the settings yourself

Paste into .vscode/mcp.json in your project

{
  "servers": {
    "proxy-toolkit": {
      "type": "stdio",
      "command": "npx",
      "args": [
        "-y",
        "@ipvolt/proxy-toolkit-mcp"
      ],
      "env": {
        "IPVOLT_ENABLE_ROUTE_CHECK": "your-value",
        "IPVOLT_PROXY_URL": "your-value"
      }
    }
  }
}

Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.

ChatGPT connects only to servers on the internet:

  1. Open ChatGPT on the web → Settings → Connectors (Apps)
  2. Press Create or Add (some plans need Developer mode under Advanced first)
  3. Paste the address below, give it a name and save
  4. If it asks you to sign in, sign in with the maker
SettingsConnectors1+ Create2https://…3
https://mcp.ipvolt.com/mcp

Menu names can differ slightly by plan and over time.

Your choice stays on this device in a cookie; no account needed.

Values you fill in

  • IPVOLT_ENABLE_ROUTE_CHECK env
    Optional local route diagnostic. Set 1 only when you want the extra tool to make a bounded request through your configured proxy.
  • IPVOLT_PROXY_URL secret env
    Private HTTP proxy URL, required only when the local route diagnostic is enabled. Supply through the client's local secret environment; never as a tool argument.

These settings are generated from the maker’s registry entry. If the README says otherwise, follow the README.

What it can do

We have not read this server’s tool list yet; we check endpoints in rotation.

Basic checksi

We check information anyone can see; we have not read the code. Checks that do not apply are left out of the count. · Checked Nov 6, 2026

  • ✓ Pass

    Maker matches the repo

    The registry name was verified with the GitHub account ipvolt, which owns the repo

  • … Not checked yet

    Still maintained

    We have not read this repo from GitHub yet

  • … Not checked yet

    Has a licence

    We have not read this repo from GitHub yet

  • … Not checked yet

    Endpoint responds

    Not checked yet; we check endpoints in rotation

  • … Not checked yet

    Sign-in with OAuth

    Not checked yet; we check endpoints in rotation

  • … Not checked yet

    No hidden instructions in tool descriptions

    Not checked yet; we read the tool list when we check the endpoint

Compared with others in Otheri

  • More stars than 0% of the other 32441 servers in this category
  • Published to the registry more recently than 43% of the other 32441 servers in this category
  • Basic checks equal to or better than 100% of the other 32441 servers in this category

Compared with every active server in this category in the registry. Stars count only when the publisher owns the repo.

Common questions

Is ipvolt Proxy Toolkit safe?

It passed 1 of 1 applicable basic checks. We have not read the code. Before adding a key or token, see what access the server asks for and use a key with only the permissions you need.

What keys or codes does it need?

You need to fill in: IPVOLT_PROXY_URL

Does it run on my computer or in the cloud?

Either way works: install it on your computer or connect to the cloud version.

Is it still maintained?

The GitHub repo last changed –, and the latest version (0.1.1) reached the registry 2 months ago.

Which apps can use it?

Apps that support MCP, such as Claude Desktop, Claude Code, Cursor and VS Code. It connects by URL, so apps that accept remote MCP servers work too, such as ChatGPT in developer mode.

What can I use instead?

In the same category: Spec Driven Development, Remote Desktop Commander, Intervals MCP

Alternatives

Servers in the same category from other makers, sorted by stars.

Reading a card:★ GitHub starsiThree pillars: reviews · checks · usageiUpdated = latest version published to the registryi

Spec Driven Development

by formulahendry

MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.

Runs on your computer★ 440MITUpdated 14 months ago
Install

Remote Desktop Commander

by desktop-commander

Remote Desktop Commander: use files, terminal and processes on your own computers from any AI app.

Runs in the cloud★ 211Updated yesterday
Install

Remote MCP server for intervals.icu run data and analysis

Runs on your computerUpdated today
Install

README from the maker

Open the README

Copied from the maker’s repo as written. PopNx MCP has not reviewed or endorsed it. HTML, images and scripts are removed. Links lead off this site.

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

ToolWhat it doesAvailability
search_proxy_docsSearch reviewed guides and articles; return canonical links, excerpts and a content revision.Hosted and local
get_proxy_docRetrieve a named document or section in bounded chunks, with revision-bound continuation cursors.Hosted and local
generate_proxy_configReturn an exact-version HTTPS GET template with local environment placeholders. It does not execute code.Hosted and local
diagnose_proxy_errorInterpret structured observations such as CONNECT407, TLS failure or an ambiguous timeout; state uncertainty and retry boundaries.Hosted and local
check_proxy_routeMake one bounded request through an explicitly configured local proxy to the fixed ipvolt echo endpoint.Local, explicitly enabled

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

ClientVersionTested interface
curl8.22.0Command line, macOS/OpenSSL
Requests2.34.2Session, Python 3.14.7
HTTPX0.28.1Synchronous Client, Python 3.14.7
Playwright1.63.0APIRequestContext, Node 24.20.0

Templates use an HTTP proxy with HTTPS CONNECT, verify destination TLS, disable redirects and automatic retries, and print status or a bounded failure category. The destination and proxy remain local TARGET_URL and PROXY_URL variables. Requests and HTTPX timeouts are phase/inactivity budgets; they are not total job deadlines. Playwright's example uses its request API, buffers the response and is intended for small diagnostic targets. It does not configure browser navigation.

The exact matrix was executed against controlled authenticated proxies and HTTPS origins. See fixture method and evidence. Other versions, proxy protocols and platforms are not claimed to have been tested. Review generated code before executing it against an authorized destination.

Optional local route diagnostic

Set IPVOLT_ENABLE_ROUTE_CHECK=1 and provide the private IPVOLT_PROXY_URL through your MCP client's local secret environment. Invoke check_proxy_route with {"profile":"default"}. The tool accepts no proxy URL, credential or destination argument. Enabling it performs no request until the tool is called.

The check uses an HTTP CONNECT proxy and verified destination TLS to request only https://mcp.ipvolt.com/egress, with a random nonce. It has a ten-second total deadline, no redirect or direct fallback, one active request, bounded headers/body and cancellation cleanup. The HTTP connection to the proxy is not encrypted; HTTP proxy authentication can be observed on that first hop. Use a trusted network or a local tunnel appropriate to your setup.

Success reports the exit address seen by that one echo request. It does not prove anonymity, country, proxy type, ownership, or the routing of a browser, shell, SDK or other agent tool. It consumes a small amount of proxy bandwidth. The echo service receives the request's exit address; application access logging is disabled. Diagnostic debug/TLS settings that could expose credentials or weaken verification are rejected.

The diagnostic requires the hosted echo service to be available. Check release status before enabling it. Controlled fixture checks do not claim a successful request through a live supplier.

Hosted service

The public remote URL is https://mcp.ipvolt.com/mcp, using Streamable HTTP. Select that transport in your MCP client and enter the URL. Public HTTPS, all four tools on both supported protocol versions, and the echo endpoint were verified on 14 September 2026; see hosted verification. It exposes the four public tools without signup or an API key. The local route diagnostic is omitted and direct attempts to call it are rejected. No proxy configuration is accepted by this service.

For a local development instance:

IPVOLT_MCP_PUBLIC_URL=http://127.0.0.1:3040/mcp npm start

The process binds to loopback. Production configuration and coordinated rollback are documented in deployment instructions. Default bounds are 32 KiB request bodies, 8 KiB headers, 16 concurrent requests and 120 requests per minute per observed peer address. Exact browser origins are allowlisted. Reverse-proxy address headers are trusted only with an explicitly configured loopback proxy that overwrites them.

Hosted metrics contain only the tool name, success/error status, duration and toolkit version. Tool arguments, result bodies, credentials and exit addresses are not logged. Rate limiting retains temporary keyed address hashes for up to 60 seconds; local stdio usage is untracked. Machine endpoints use noindex and remain separate from the public website's consent-controlled analytics.

Maintain and verify

npm run typecheck

npm run build npm test npm run check:content npm run check:manifest npm run check:package python3 -m unittest discover -s deploy -p 'test_*.py' -v

check:package inspects the actual npm tarball, installs it in a temporary consumer directory and discovers/calls all four tools with the current and legacy protocol paths. check:content -- --live compares every bundled Markdown document to its public canonical export; it performs only those allowlisted public reads.

The runtime does not crawl the website. A maintainer exports only the reviewed public guide/blog catalogs from a verified website source using scripts/export-content.ts, reviews the resulting diff and publishes a new immutable package version. Drafts and private operational applications are outside that allowlist. Bundle and document SHA-256 values make source changes observable.

Code is MIT licensed. Bundled editorial content has a separate content license. Support belongs in the repository's issue tracker; omit credentials and private logs from reports.

Ask PopNx