ipvolt Proxy Toolkit
NPM · @IPVOLT/PROXY-TOOLKIT-MCP · 2 COMPONENTS · SCANNED SEP 25
Proxy guides, tested configurations and error diagnostics, with an optional local route check.
Available components
How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score → Why this is hard to score →
Supply Chain Security100
- No malware found by supply-chain analysis.Pass
- No known CVEs affecting this package version or its production dependencies.Pass
- No install/post-install scripts declared.Pass
- 0 of 5 dependencies flagged as unhealthy. View diagnostics → Pass
Provenance & Transparency45
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Provenance check failed: no build-provenance attestation is published. See how to fix → View diagnostics → Fail
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 10 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability69
- AI-judged instruction clarity (good).Pass
- Tool/resource definitions use about 426 tokens (~106/item across 4 items; 4 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management37
- Stability observed for 11 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage83
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 42% of tool parameters carry a description.Partial
- Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 4 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 4 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a current MCP spec version (2026-07-28).Pass
How do I install the ipvolt Proxy Toolkit MCP server?
ipvolt Proxy Toolkit runs locally as an npm package, launched with npx -y @ipvolt/proxy-toolkit-mcp. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
npm · @ipvolt/proxy-toolkit-mcp
claude mcp add ipvolt-proxy-toolkit -- npx -y @ipvolt/proxy-toolkit-mcp
{
"mcpServers": {
"ipvolt-proxy-toolkit": {
"command": "npx",
"args": [
"-y",
"@ipvolt/proxy-toolkit-mcp"
]
}
}
} {
"servers": {
"ipvolt-proxy-toolkit": {
"command": "npx",
"args": [
"-y",
"@ipvolt/proxy-toolkit-mcp"
]
}
}
} codex mcp add ipvolt-proxy-toolkit -- npx -y @ipvolt/proxy-toolkit-mcp
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"ipvolt-proxy-toolkit": {
"type": "local",
"command": [
"npx",
"-y",
"@ipvolt/proxy-toolkit-mcp"
],
"enabled": true
}
}
} openclaw mcp add ipvolt-proxy-toolkit --command npx --arg -y --arg @ipvolt/proxy-toolkit-mcp
mcp_servers:
ipvolt-proxy-toolkit:
command: "npx"
args: ["-y", "@ipvolt/proxy-toolkit-mcp"] {
"McpServers": {
"ipvolt-proxy-toolkit": {
"Transport": "stdio",
"Command": "npx",
"Arguments": [
"-y",
"@ipvolt/proxy-toolkit-mcp"
]
}
}
} assistant mcp add ipvolt-proxy-toolkit -t stdio -c npx -a -y @ipvolt/proxy-toolkit-mcp
{
"mcpServers": {
"ipvolt-proxy-toolkit": {
"command": "npx",
"args": [
"-y",
"@ipvolt/proxy-toolkit-mcp"
]
}
}
} Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 25 Sept 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 24 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 30 to 33. That category is still filling its 30-day observation window: 9 days of observed history at the previous scan, 10 at this one. The score rises as the window fills, whether or not the server changes.
- 22 Sept 26 +4
- Stability: unverified → 0.27 ▲ functional
- 15 Sept 26 +15
- Malware scan: unverified → pass ▲ security
- 14 Sept 26 53
First indexed and scored.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 25 Sept 2026 · Analysed npm/@ipvolt/proxy-toolkit-mcp@0.1.0
Provenance No attestation
The registry publishes no build provenance for this version, so there is nothing to verify.
| Result | No attestation |
|---|---|
| Ecosystem | npm |
Background: How many MCP packages publish verified provenance →
Dependencies 5 packages
| Packages resolved | 5 |
|---|---|
| Tree resolution | Complete |
Background: SBOMs and build attestations, explained →
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
diagnose_proxy_error Diagnose a proxy error ~192
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.
| Name | Type | Req | Description |
|---|---|---|---|
| client | string | yes | – |
| exception | string | – | Normalized category, not raw exception text. HTTPX ConnectError alone does not establish a TLS error. |
| method | string | – | – |
| phase | string | yes | – |
| 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 | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| candidates | array | yes | – |
| client | string | yes | – |
| evidence | object | yes | – |
| retry | object | yes | – |
| rulesRevision | string | yes | – |
| sources | array | yes | – |
| summary | string | yes | – |
| uncertainty | array | yes | – |
| version | string | yes | – |
No examples provided.
generate_proxy_config Generate a tested proxy configuration ~111
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.
| Name | Type | Req | Description |
|---|---|---|---|
| client | string | yes | Client whose exact tested configuration to generate. |
| protocol | string | – | HTTP proxy with HTTPS CONNECT. Other proxy protocols are not tested. |
| timeoutSeconds | integer | – | – |
| version | string | yes | Exact tested version matching the client. Other versions are unsupported. |
| Name | Type | Req | Description |
|---|---|---|---|
| behavior | object | yes | – |
| client | string | yes | – |
| code | string | yes | – |
| environment | array | yes | – |
| interface | string | yes | – |
| language | string | yes | – |
| limitations | array | yes | – |
| protocol | string | yes | – |
| sources | array | yes | – |
| summary | string | yes | – |
| templateRevision | string | yes | – |
| testedRuntime | string | yes | – |
| version | string | yes | – |
No examples provided.
get_proxy_doc Read a reviewed proxy document ~63
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.
| Name | Type | Req | Description |
|---|---|---|---|
| cursor | string | – | – |
| documentId | string | yes | – |
| section | string | – | – |
| Name | Type | Req | Description |
|---|---|---|---|
| chunk | number | yes | – |
| document | object | yes | – |
| markdown | string | yes | – |
| nextCursor | string|null | yes | – |
| provenance | object | yes | – |
| sections | array | yes | – |
| totalChunks | number | yes | – |
No examples provided.
search_proxy_docs Search reviewed proxy documentation ~60
Find reviewed ipvolt public guides and articles. Returns canonical document IDs, excerpts and content revision. Submit a short topic query, never credentials or logs.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | – |
| query | string | yes | – |
| topic | string | – | – |
| Name | Type | Req | Description |
|---|---|---|---|
| provenance | object | yes | – |
| results | array | yes | – |
No examples provided.
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 npm package (@ipvolt/proxy-toolkit-mcp).
Is the ipvolt Proxy Toolkit MCP server safe to use?
ipvolt Proxy Toolkit scores 73 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 25 September 2026. It declares no install or post-install scripts. 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.
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.
What licence is the ipvolt Proxy Toolkit MCP server under?
ipvolt Proxy Toolkit declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.