ipvolt Proxy Toolkit
OfficialServer Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| IPVOLT_PROXY_URL | No | The private proxy URL used by the optional local route diagnostic. Provide it through your MCP client's local secret environment. | |
| IPVOLT_ENABLE_ROUTE_CHECK | No | Set to 1 to enable the optional local route diagnostic tool (check_proxy_route). Enabling it performs no request until the tool is called. |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": false
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| search_proxy_docsB | Find reviewed ipvolt public guides and articles. Returns canonical document IDs, excerpts and content revision. Submit a short topic query, never credentials or logs. |
| get_proxy_docA | 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. |
| generate_proxy_configA | 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. |
| diagnose_proxy_errorA | 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. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 4 tools
Each tool occupies a distinct phase of a support workflow: discovery (search_proxy_docs), retrieval (get_proxy_doc), generation (generate_proxy_config), and troubleshooting (diagnose_proxy_error). The search/retrieve pair is explicitly linked via document IDs and cursors, and generate vs. diagnose are clearly separated by intent. No two tools could be mistaken for one another.
All four tools use a consistent verb_noun snake_case pattern with a stable 'proxy' domain prefix (search_proxy_docs, get_proxy_doc, generate_proxy_config, diagnose_proxy_error). The verb choice matches the action in every case, and the only variation (docs vs. doc) is a natural plural/singular distinction.
Four tools is a tight, well-scoped set that covers the core workflow without redundancy, which fits a focused proxy guidance toolkit. It sits at the thin end of the range, since broader operations like listing available client versions or documents are absent, but nothing feels padded or missing at the task level.
Search-plus-retrieve covers the documentation lifecycle, and generate/diagnose address the two main user actions (writing config, fixing errors), so agents have a path through the domain. Minor gaps remain: no tool to enumerate supported client/version combinations or to validate a generated example before use.