Click on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type @ followed by the MCP server name and your instructions, e.g., "@Proxychains MCP Server run curl ifconfig.me through the proxy chain"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
MCP server for proxychains-ng (proxychains4) - route commands through proxy chains via SSH to a remote Linux host (e.g., Kali Linux).
This MCP server provides tools to manage and use proxychains configurations dynamically. It executes commands through SSH on a remote host where proxychains4 is installed, allowing AI assistants to route network traffic through proxy chains for privacy, security testing, or accessing geo-restricted resources.
Related MCP server: SSH MCP Server
Tool | Description |
| Execute commands through the configured proxy chain |
| Get, set, or reset the full configuration |
| Add a proxy to the chain (SOCKS4, SOCKS5, HTTP, RAW) |
| Remove a proxy by index or host:port |
| Set chain mode (strict, dynamic, random, round_robin) |
| Configure DNS handling mode |
| Test proxy chain connectivity and latency |
| List all configured proxies |
| Import proxies from file or URL |
| Export configuration in various formats |
Node.js 18+
SSH access to a Linux host with proxychains4 installed
The SSH host should be configured in ~/.ssh/config or accessible by hostname
# Clone the repository
git clone https://github.com/schwarztim/sec-proxychains-mcp.git
cd sec-proxychains-mcp
# Install dependencies
npm install
# Build
npm run buildAdd to your Claude Desktop or MCP client configuration:
{
"mcpServers": {
"proxychains": {
"command": "node",
"args": ["/path/to/sec-proxychains-mcp/dist/index.js"],
"env": {
"PROXYCHAINS_KALI_HOST": "kali",
"PROXYCHAINS_SSH_TIMEOUT": "30000"
}
}
}
}Variable | Default | Description |
|
| SSH hostname for the remote host |
|
| SSH command timeout in milliseconds |
|
| Local config storage directory |
Mode | Description |
| All proxies must work, used in order specified |
| Skip dead proxies, at least one must work |
| Random proxy selection for each connection |
| Rotate through proxies sequentially |
Type | Description |
| SOCKS5 proxy (recommended) |
| SOCKS4 proxy |
| HTTP CONNECT proxy |
| Raw TCP forwarding |
Mode | Description |
| Route DNS through proxy (recommended, prevents leaks) |
| Legacy mode using proxyresolv |
| Daemon-based DNS resolution |
| No DNS proxying (may leak DNS queries) |
// Add a SOCKS5 proxy (e.g., Tor)
proxychains_add({ type: "socks5", host: "127.0.0.1", port: 9050 })
// Add an authenticated HTTP proxy
proxychains_add({
type: "http",
host: "proxy.example.com",
port: 8080,
user: "admin",
pass: "secret"
})
// Set dynamic chain mode (skip dead proxies)
proxychains_mode({ mode: "dynamic_chain" })// Test connectivity
proxychains_test({ verbose: true })
// Test against specific target
proxychains_test({ target: "https://api.ipify.org" })// Check your proxied IP
proxychains_run({ command: "curl https://httpbin.org/ip" })
// Run nmap through proxies
proxychains_run({ command: "nmap -sT -Pn target.com" })
// Custom timeout for long operations
proxychains_run({ command: "wget https://example.com/large-file", timeout: 120000 })// Import from URL
proxychains_import({
source: "https://raw.githubusercontent.com/example/proxies/main/list.txt",
defaultType: "socks5"
})
// Import from file on remote host
proxychains_import({ source: "/tmp/proxies.txt" })// Export as proxychains.conf format
proxychains_export({ format: "proxychains" })
// Export as JSON
proxychains_export({ format: "json" })
// Export as simple ip:port list
proxychains_export({ format: "ip:port" })The remote host (e.g., Kali Linux) needs proxychains4 installed:
# Debian/Ubuntu/Kali
sudo apt update
sudo apt install proxychains4 curl
# Verify installation
proxychains4 --versionEnsure SSH access works without password prompts:
# Test SSH connection
ssh kali "echo 'Connection successful'"SSH Keys: Use SSH key authentication instead of passwords
DNS Leaks: Use proxy_dns mode to prevent DNS leakage
Proxy Trust: Only use trusted proxies; traffic is visible to proxy operators
Authentication: Proxy credentials are stored locally in ~/.proxychains-mcp/config.json
┌─────────────────┐ SSH ┌─────────────────┐ Proxies ┌─────────────┐
│ MCP Client │─────────────▶│ Remote Host │────────────────▶│ Target │
│ (Claude, etc) │ │ (Kali Linux) │ │ │
└─────────────────┘ │ proxychains4 │ └─────────────┘
└─────────────────┘Contributions are welcome! Please feel free to submit a Pull Request.
Fork the repository
Create your feature branch (git checkout -b feature/amazing-feature)
Commit your changes (git commit -m 'Add some amazing feature')
Push to the branch (git push origin feature/amazing-feature)
Open a Pull Request
This project is licensed under the MIT License - see the LICENSE file for details.
proxychains-ng - The proxychains implementation
Model Context Protocol - The MCP specification
Add a proxy to the chain. Supports SOCKS4, SOCKS5, and HTTP proxies.
Inputs: host (required), port (required), type (required), pass, +2 more.
Get or set the current proxychains configuration including chain mode, DNS settings, and proxy list.
Inputs: action (required), config.
Configure DNS handling. proxy_dns (recommended): DNS through proxy. proxy_dns_old: legacy mode. proxy_dns_daemon: daemon mode. none: no DNS proxying.
Inputs: mode (required).
Export current proxy configuration to a file.
Inputs: format.
Import proxies from a file or URL. Supports common proxy list formats.
Inputs: source (required), format, defaultType.
List all proxies currently configured in the chain.
Inputs: no named parameters.
Set the chain mode. strict_chain: all proxies must work. dynamic_chain: skip dead proxies. random_chain: random order. round_robin_chain: rotate through proxies.
Inputs: mode (required), chainLen.
Remove a proxy from the chain by index or by host:port.
Inputs: host, port, index.
Run a command through the proxy chain on Kali Linux. The command will be routed through all configured proxies.
Inputs: command (required), timeout.
Test the proxy chain by checking connectivity and measuring latency. Optionally test against a specific target.
Inputs: target, verbose.
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
Scored across 10 tools
Each tool has a clearly distinct purpose: running commands, managing proxies, configuring modes, DNS, and testing. No overlaps.
All tools follow a consistent 'proxychains_verb' snake_case pattern, making them predictable and easy to use.
10 tools is well-scoped for managing proxychains – covers all essential operations without bloat or gaps.
Covers CRUD for proxies, configuration, execution, testing, import/export, and DNS – no obvious missing functionality.
Control dedicated 4G mobile and residential proxies on mobileproxy.space from AI agents.
Work on your own computers from Claude or ChatGPT: run commands, edit and search files.
Linux VMs for AI agents: create VMs, run commands, edit files and open preview URLs.
Residential and mobile proxies and Private modems for AI agents: proxy URLs, stock, rotation, top-up
