# VPN Bypass (npm · vpn-bypass-mcp)

Read and change VPN Bypass (macOS) routing: domain lists, services, modes, kernel routes, logs

- Trust score: 48/100 (low)
- Change this week: 0
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-04

## Components

- npm · `vpn-bypass-mcp`: 48/100 (this document), [markdown](https://verifymcp.io/servers/geiserx-vpn-bypass-mcp/vpn-bypass-mcp.md), [page](https://verifymcp.io/servers/geiserx-vpn-bypass-mcp/vpn-bypass-mcp)

## Channel facts

- Registry: `npm`
- Package: `vpn-bypass-mcp`
- Version: `0.2.0`
- Transport: `stdio`

## Trust breakdown

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. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-11-04.

- **Supply Chain Security**: 94/100
  - No malware found by supply-chain analysis.
  - No known CVEs affecting this package version or its production dependencies.
  - Declares code that runs automatically (postinstall) and that we could not recognise. It may be perfectly ordinary, but we have not established what it does.
  - No production dependencies, so there is no dependency health to assess.
- **Provenance & Transparency**: 100/100
  - Source repository is publicly reachable at the declared URL.
  - Cryptographically verified build provenance (signed, bound to GeiserX/vpn-bypass-mcp).
  - Clear OSI-approved license (MIT).
  - Actively maintained (last published 7 days ago).
  - Publishes a security disclosure policy (SECURITY.md).
- **Schema Quality & AI Usability**: 0/100
  - Schema quality not yet verified: our sandbox could not run this package, so we have no schema to assess.
- **Stability & Change Management**: 0/100
  - Stability not yet verified: our sandbox could not run this package, so we have no schema to compare.
- **Tool Coverage**: 0/100
  - Tool coverage not yet verified: our sandbox could not run this package, so we have no tool definitions to assess.
- **Tool Safety**: 0/100
  - Tool safety not yet verified: our sandbox could not run this package, so we have no tool text to scan.
- **Capabilities**: 0/100
  - Protocol version not yet verified: our sandbox could not run this package, so we never saw its MCP handshake.

**Unverified: 5 categories.** Categories scored 0 because our sandbox could not run this package, so we have no schema for these checks to read. That is a gap on our side rather than a finding about the package, and we only credit what we can confirm, so the score stands at 0 until we can run it.

## Install

### How do I install the VPN Bypass MCP server?

VPN Bypass runs locally as an npm package, launched with npx -y vpn-bypass-mcp. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

### Claude

```bash
claude mcp add geiserx-vpn-bypass-mcp -- npx -y vpn-bypass-mcp
```

### Cursor

```json
{
  "mcpServers": {
    "geiserx-vpn-bypass-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "vpn-bypass-mcp"
      ]
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "geiserx-vpn-bypass-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "vpn-bypass-mcp"
      ]
    }
  }
}
```

### Codex

```bash
codex mcp add geiserx-vpn-bypass-mcp -- npx -y vpn-bypass-mcp
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "geiserx-vpn-bypass-mcp": {
      "type": "local",
      "command": [
        "npx",
        "-y",
        "vpn-bypass-mcp"
      ],
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add geiserx-vpn-bypass-mcp --command npx --arg -y --arg vpn-bypass-mcp
```

### Hermes

```yaml
mcp_servers:
  geiserx-vpn-bypass-mcp:
    command: "npx"
    args: ["-y", "vpn-bypass-mcp"]
```

### Netclaw

```json
{
  "McpServers": {
    "geiserx-vpn-bypass-mcp": {
      "Transport": "stdio",
      "Command": "npx",
      "Arguments": [
        "-y",
        "vpn-bypass-mcp"
      ]
    }
  }
}
```

### Vellum

```bash
assistant mcp add geiserx-vpn-bypass-mcp -t stdio -c npx -a -y vpn-bypass-mcp
```

### Other

```json
{
  "mcpServers": {
    "geiserx-vpn-bypass-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "vpn-bypass-mcp"
      ]
    }
  }
}
```

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-11-03 (score 48, 0)

- [functional improvement] Security disclosure: unverified → pass

### 2026-11-02 (score 48, 0)

- [functional regression] Security disclosure: pass → unverified

### 2026-10-27 (score 48, 0)

- [functional] Package version: 0.1.2 → 0.2.0

### 2026-10-22 (score 48, 0)

- [functional improvement] Security disclosure: unverified → pass

### 2026-10-21 (score 48, 0)

- [functional regression] Security disclosure: pass → unverified

### 2026-10-05 (score 48, 0)

- [security] Stability: Stability not yet verified: our sandbox could not run this package, so we have no schema to compare.
- [security] Tool safety: Tool safety not yet verified: our sandbox could not run this package, so we have no tool text to scan.
- [functional] Schema quality: Schema quality not yet verified: our sandbox could not run this package, so we have no schema to assess.
- [functional] Capabilities: Protocol version not yet verified: our sandbox could not run this package, so we never saw its MCP handshake.
- [functional] Tool coverage: Tool coverage not yet verified: our sandbox could not run this package, so we have no tool definitions to assess.

### 2026-10-04 (score 48, 0)

- [security] Tool safety: Tool safety not yet verified: we do not have a sandbox capture of the tool definitions this version of the package serves yet.
- [security] Stability: Stability not yet verified: we do not have a sandbox capture of the MCP schema this version of the package serves yet.
- [functional] Capabilities: Protocol version not yet verified: we do not have a sandbox capture of the MCP handshake this version of the package performs yet.
- [functional] Tool coverage: Tool coverage not yet verified: we do not have a sandbox capture of the tool definitions this version of the package serves yet.
- [functional] Schema quality: Schema quality not yet verified: we do not have a sandbox capture of the MCP schema this version of the package serves yet.
- [functional] Package version: 0.1.1 → 0.1.2

### 2026-10-03 (score 48, +5)

- [security improvement] Source repository: unverified → pass

## MCP tools (0)

Tools for package channels are captured by running the package in an isolated sandbox. Our sandbox could not run this package, so no tool list has been captured. That is a gap on our side, not a finding about the package.

## Diagnostics

Captured diagnostic sections: Provenance, Install scripts, Dependencies. The full working is on the page: https://verifymcp.io/servers/geiserx-vpn-bypass-mcp/vpn-bypass-mcp#diagnostics

## Score history

- 2026-11-04: 48
- 2026-11-03: 48
- 2026-11-02: 48
- 2026-11-01: 48
- 2026-10-31: 48
- 2026-10-30: 48
- 2026-10-29: 48
- 2026-10-28: 48
- 2026-10-27: 48
- 2026-10-26: 48
- 2026-10-25: 48
- 2026-10-24: 48
- 2026-10-23: 48
- 2026-10-22: 48
- 2026-10-21: 48
- 2026-10-20: 48
- 2026-10-19: 48
- 2026-10-18: 48
- 2026-10-17: 48
- 2026-10-16: 48
- 2026-10-15: 48
- 2026-10-14: 48
- 2026-10-13: 48
- 2026-10-12: 48
- 2026-10-05: 48
- 2026-10-04: 48
- 2026-10-03: 48
- 2026-10-02: 43
- 2026-10-01: 48
- 2026-09-30: 23

## Common questions

### What is the VPN Bypass MCP server?

VPN Bypass is an MCP server listed in the public MCP registry as io.github.GeiserX/vpn-bypass-mcp. Read and change VPN Bypass (macOS) routing: domain lists, services, modes, kernel routes, logs. This page covers its npm package (vpn-bypass-mcp).

### Is the VPN Bypass MCP server safe to use?

VPN Bypass scores 48 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 4 November 2026. Its build provenance is signed and verified. 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.

### Is the VPN Bypass MCP server still maintained?

VPN Bypass is still listed as active in the MCP registry. We last reached this channel on 4 November 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 VPN Bypass MCP server under?

VPN Bypass declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.

## Links

- npm package: https://www.npmjs.com/package/vpn-bypass-mcp
- Socket report: https://socket.dev/npm/package/vpn-bypass-mcp
- Repository: https://github.com/GeiserX/vpn-bypass-mcp
- Website: https://geiserx.github.io/vpn-bypass-mcp/
- Changelog RSS feed: https://verifymcp.io/servers/geiserx-vpn-bypass-mcp/vpn-bypass-mcp.xml
- Changelog JSON feed: https://verifymcp.io/servers/geiserx-vpn-bypass-mcp/vpn-bypass-mcp.json
- HTML version of this page: https://verifymcp.io/servers/geiserx-vpn-bypass-mcp/vpn-bypass-mcp