Find the relevant guide
search_proxy_docsSearch the reviewed public library for proxy setup and troubleshooting passages, with canonical source links.
ipvolt / developer tools
Bring proxy setup notes, configuration examples and troubleshooting into a client that supports the Model Context Protocol (MCP).
The toolkit works with your existing proxy provider. ipvolt proxy service access is not open yet.
A focused toolkit
search_proxy_docsSearch the reviewed public library for proxy setup and troubleshooting passages, with canonical source links.
get_proxy_docRetrieve a bounded section of an approved document, including its source and review information.
generate_proxy_configGet a supported configuration template with environment-variable placeholders. Examples never require pasting a password into your agent.
diagnose_proxy_errorUse a status, exception and request phase to distinguish likely causes and choose the next check. An uncertain result stays uncertain.
check_proxy_routeMake an explicitly requested local connection through a configured HTTP proxy to ipvolt's fixed HTTPS diagnostic endpoint. Returns the address observed for that request.
Connection options
Use the four public documentation, configuration and diagnosis tools without running a local process or supplying proxy credentials.
Add this URL in your client's Streamable HTTP MCP server settings. Client configuration formats differ; use the remote-server instructions for your installed client.
https://mcp.ipvolt.com/mcpHosted tools do not connect to your proxy or request an arbitrary target URL.
Use the same four tools through stdio. The optional route check runs on your machine and must be enabled explicitly.
Install Node.js 24 or later. Add the command and arguments below to your client's stdio MCP configuration. This example uses the common mcpServers format; use your client's equivalent if it differs. The version is pinned; update it deliberately when a reviewed release is available.
{
"mcpServers": {
"ipvolt-proxy-toolkit": {
"command": "npx",
"args": [
"--yes",
"@ipvolt/proxy-toolkit-mcp@0.1.0"
]
}
}
}For the optional check, configure IPVOLT_PROXY_URL privately in the local server environment and set IPVOLT_ENABLE_ROUTE_CHECK=1. The tool accepts the profile name default, not a proxy URL or password. It supports HTTP proxies that tunnel HTTPS using CONNECT and contacts only https://mcp.ipvolt.com/egress.
Local route check setup detailsKeep proxy credentials in the documented local configuration, outside prompts and tool arguments. Enabling the package alone does not run a network check.
A debugging workflow
Give your agent the client, version, exception or status, and the request phase. Leave out passwords, private URLs and full logs.
My HTTPX request returns 407 during proxy connection. Help me identify the next check.
Ask for a configuration template and open its linked guide. The result identifies supported options and uses placeholders for secrets.
Show an HTTPX proxy configuration using an environment variable, and explain which settings control routing.
If you enable the local tool, ask it to check the configured profile. This makes one bounded request; it does not test a site's content or change other tools.
Check the route for my configured local proxy profile, then explain what the result establishes.
Interpreting results
A route result applies to that request, process, endpoint and time. It does not prove that your browser or every tool in an agent session uses the same proxy.
An observed IP address does not establish country coverage, residential or mobile classification, anonymity, or access to a particular website.
The diagnostic tools suggest causes and next checks. A timeout after sending a write does not establish that retrying it is safe.
The toolkit does not provision ipvolt proxies, manage accounts, purchase traffic or submit a signup.
Keep reading