VPN Bypass runs on your own machine — the client starts it, so there is no endpoint to ping. 338 installs a week from npm. Last commit 28 Oct 2026.
Read and change VPN Bypass (macOS) routing: domain lists, services, modes, kernel routes, logs
We read the source, 4 d ago · rules 995398eba69f
What this server is able to do. For an MCP server this is often the job itself — a terminal server runs commands because that is what it is for. Listed so you know what you are plugging in, not as an accusation.
postinstall: node postinstall.js
const archive = path.join(tmp, name);
const child = spawn(binPath, process.argv.slice(2), { stdio: "inherit" });
Is this your server and something here is wrong? Tell us — corrections are free and do not require a plan.
We found places where it runs commands, builds paths or queries from values it is given. None of that is a flaw by itself — it becomes one when the code changes, and code changes quietly between releases. We re-read it on every one.
This server runs on your own machine — install it with the package manager and the client starts it for you. Package name taken from the official registry entry.
claude mcp add vpn-bypass-mcp -- npx -y vpn-bypass-mcp
{
"mcpServers": {
"vpn-bypass-mcp": {
"command": "npx",
"args": [
"-y",
"vpn-bypass-mcp"
]
}
}
}
[mcp_servers.vpn-bypass-mcp]
command = "npx"
args = ["-y", "vpn-bypass-mcp"]
{
"mcpServers": {
"vpn-bypass-mcp": {
"command": "npx",
"args": [
"-y",
"vpn-bypass-mcp"
]
}
}
}
{
"servers": {
"vpn-bypass-mcp": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"vpn-bypass-mcp"
]
}
}
}
Optional settings from the registry entry, left out of the block above:
VPNB_SOCKET (Path of the VPN Bypass control socket (default ~/Library/Application Support/VPNBypass/control.sock)), VPN_BYPASS_MCP_READ_ONLY (Set to 1 to register only the 8 read tools and the diagnose_site prompt; any value except empty, 0, false or no turns it on).
Read-only access to your Infrly services, deploys, logs, metrics and billing.
macOS OpenVPN/FortiGate VPN status, logs and diagnosis; read-only by default, never returns secrets
Read-only Kubernetes diagnostics: pods, logs, events, workloads, services, PVCs and nodes.
Agent-to-agent cloud service: deploys and runs your apps and services — domains, logs, real status.
Read refrigeration units, service history, F-gas logs and alarms in Maci. Read only.
Deploy services, add databases, run agents, read logs, check vulnerabilities and publish pages.
Read Kisi places, doors, users, groups, access rights and access logs (no unlocking).
Render services, deploys, env vars and logs as MCP tools.
Answers built from our own checks of this server.