# Ghost Networks (mcpb · linux-x64)

Private, programmable networking for the AI age: manage networks, devices, hubs and VPN.

- Trust score: 40/100 (low)
- Change this week: +3
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-05

## Components

- mcpb · `linux-arm64`: 6/100, [markdown](https://verifymcp.io/servers/net-gh-o-ghost-mcp/ghost-mcp-linux-arm64.md), [page](https://verifymcp.io/servers/net-gh-o-ghost-mcp/ghost-mcp-linux-arm64)
- mcpb · `linux-x64`: 40/100 (this document), [markdown](https://verifymcp.io/servers/net-gh-o-ghost-mcp/ghost-mcp-linux-x64.md), [page](https://verifymcp.io/servers/net-gh-o-ghost-mcp/ghost-mcp-linux-x64)
- mcpb · `ghost-mcp-macos-v0.41.0.mcpb`: 6/100, [markdown](https://verifymcp.io/servers/net-gh-o-ghost-mcp/ghost-mcp-macos.md), [page](https://verifymcp.io/servers/net-gh-o-ghost-mcp/ghost-mcp-macos)
- mcpb · `win-x64`: 6/100, [markdown](https://verifymcp.io/servers/net-gh-o-ghost-mcp/ghost-mcp-windows-x64.md), [page](https://verifymcp.io/servers/net-gh-o-ghost-mcp/ghost-mcp-windows-x64)

## Channel facts

- Registry: `mcpb`
- Package: `https://github.com/ghost-networks/ghost-mcp/releases/download/v0.41.0/ghost-mcp-linux-x64-v0.41.0.mcpb`
- Transport: `stdio`
- SHA-256: `00cd7d2bd4e5cdf18252a85e727e77310536ca45b3adb1a8013b98dd1aac9b31`

## 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-05.

- **Supply Chain Security**: 0/100
  - No malware scan is available for this kind of package: the supply-chain vendors we use do not cover it. This is a permanent gap in our coverage, not a finding about the package.
  - Known CVEs could not be checked: we found no dependency list to check in this bundle: either it runs a compiled binary, whose bundled manifests we do not read, or none of the package.json, requirements.txt, pyproject.toml or uv.lock files it ships for its runtime declares a dependency we can read (a requirements.txt that only points at a setup.py project, a local path, or a nested requirements file we cannot follow counts as none).
  - Install-script risk not yet assessed.
  - Dependency health could not be checked: we found no dependency list to check in this bundle: either it runs a compiled binary, whose bundled manifests we do not read, or none of the package.json, requirements.txt, pyproject.toml or uv.lock files it ships for its runtime declares a dependency we can read (a requirements.txt that only points at a setup.py project, a local path, or a nested requirements file we cannot follow counts as none).
- **Provenance & Transparency**: 32/100
  - Source repository is publicly reachable at the declared URL.
  - Provenance check failed: no build-provenance attestation is published.
  - License check failed: no license is declared.
  - Actively maintained (last published 16 days ago).
  - Disclosure check failed: no security disclosure policy was found in the source repository.
- **Schema Quality & AI Usability**: 68/100
  - AI-judged instruction clarity (good).
  - Tool/resource definitions use about 1742 tokens (~42/item across 41 items; 41 tools + 0 resources), lean.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 57/100
  - Stability observed for 17 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
- **Tool Safety**: 75/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - 0 of 9 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation; "ghost_logout" implies "remove" and declares no destructiveHint at all, which the MCP spec reads as destructive by default.
  - An AI judge read all 41 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 20/100
  - Spec-recency check failed: implements MCP spec 2024-11-05; the latest is 2026-07-28.

**Unverified: 1 category.** A category scored 0 because we could not verify it: a data source with nothing on this package, evidence we could not reach, or a check we could not run. We only credit what we can confirm.

## Install

### How do I install the Ghost Networks MCP server?

Ghost Networks ships as an MCPB bundle, a single file you download and open in an MCP host that supports MCPB bundles, such as Claude Desktop. The host reads the launch command from the bundle's own manifest, so there is no command to copy. Before opening it, check the file's SHA-256 matches the one the MCP registry declares for it, 00cd7d2bd4e5cdf18252a85e727e77310536ca45b3adb1a8013b98dd1aac9b31; the commands to do that are on this page. If it does not match, do not open it.

- Download bundle: `https://github.com/ghost-networks/ghost-mcp/releases/download/v0.41.0/ghost-mcp-linux-x64-v0.41.0.mcpb`
- SHA-256: `00cd7d2bd4e5cdf18252a85e727e77310536ca45b3adb1a8013b98dd1aac9b31`

### Verify on macOS / Linux

```bash
echo "00cd7d2bd4e5cdf18252a85e727e77310536ca45b3adb1a8013b98dd1aac9b31  ghost-mcp-linux-x64-v0.41.0.mcpb" | shasum -a 256 -c
```

### Verify on Windows (PowerShell)

```powershell
(Get-FileHash -Algorithm SHA256 .\ghost-mcp-linux-x64-v0.41.0.mcpb).Hash -eq "00cd7d2bd4e5cdf18252a85e727e77310536ca45b3adb1a8013b98dd1aac9b31"
```

## 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-05 (score 40, +1)

No change was recorded against any check on this day. Stability & Change Management went from 53 to 57. That category is still filling its 30-day observation window: 16 days of observed history at the previous scan, 17 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-11-02 (score 39, +1)

No change was recorded against any check on this day. Stability & Change Management went from 43 to 47. That category is still filling its 30-day observation window: 13 days of observed history at the previous scan, 14 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-10-31 (score 38, +1)

No change was recorded against any check on this day. Stability & Change Management went from 37 to 40. That category is still filling its 30-day observation window: 11 days of observed history at the previous scan, 12 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-10-29 (score 37, +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.

### 2026-10-27 (score 36, +1)

No change was recorded against any check on this day. Stability & Change Management went from 23 to 27. That category is still filling its 30-day observation window: 7 days of observed history at the previous scan, 8 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-10-25 (score 35, +1)

No change was recorded against any check on this day. Stability & Change Management went from 17 to 20. That category is still filling its 30-day observation window: 5 days of observed history at the previous scan, 6 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-10-23 (score 34, +1)

No change was recorded against any check on this day. Stability & Change Management went from 10 to 13. That category is still filling its 30-day observation window: 3 days of observed history at the previous scan, 4 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-10-21 (score 33, +1)

No change was recorded against any check on this day. Stability & Change Management went from 3 to 7. That category is still filling its 30-day observation window: 1 days of observed history at the previous scan, 2 at this one. The score rises as the window fills, whether or not the server changes.

## MCP tools (41)

### `ghost_init` (~66 tokens)

Initialize Ghost CLI with an API key. Validates the key, generates crypto keys, and optionally joins a network via helbind key.

Input parameters:

- `api_key` (string, required): Ghost Networks API key
- `helbind_key` (string): Path to key.json for automatic network join (optional)

### `ghost_status` (~20 tokens)

Show current account info, plan, limits, and features.

### `ghost_refresh` (~19 tokens)

Refresh plan, limits, and features from the server.

### `ghost_use_network` (~30 tokens)

Set the default network for subsequent commands.

Input parameters:

- `network` (string, required): Network ID to set as default

### `ghost_logout` (~15 tokens)

Remove CLI configuration and log out.

### `ghost_network_create` (~27 tokens)

Create a new Ghost network.

Input parameters:

- `name` (string, required): Name for the new network

### `ghost_network_list` (~20 tokens)

List all networks owned by or shared with this account.

### `ghost_network_join` (~58 tokens)

Join an existing network. Without helbind_key, generates a 12-digit code that a network admin must approve. With helbind_key, joins automatically.

Input parameters:

- `helbind_key` (string): Path to key.json for automatic join (optional)

### `ghost_network_connect` (~19 tokens)

Connect to the active network via WireGuard tunnel.

### `ghost_network_disconnect` (~16 tokens)

Disconnect from the WireGuard tunnel.

### `ghost_wg_status` (~23 tokens)

Check WireGuard tunnel status: installed, connected, config path.

### `ghost_devices_list` (~46 tokens)

List devices in a network, optionally filtered by hub.

Input parameters:

- `hub` (string): Hub ID to filter devices
- `network` (string): Network ID (uses default if omitted)

### `ghost_devices_get` (~25 tokens)

Get details for a specific device.

Input parameters:

- `id` (string, required): Device ID

### `ghost_devices_add` (~64 tokens)

Add a pending device to the network using its 12-digit code.

Input parameters:

- `code` (string, required): 12-digit code shown on the device
- `name` (string, required): Nickname for the device
- `network` (string): Network ID (uses default if omitted)

### `ghost_devices_revoke` (~46 tokens)

Revoke (remove) a device from the network.

Input parameters:

- `id` (string, required): Device ID to revoke
- `network` (string): Network ID (uses default if omitted)

### `ghost_devices_bulk_revoke` (~54 tokens)

Revoke all devices in a hub. Optionally only revoke expired devices.

Input parameters:

- `expired_only` (boolean): If true, only revoke expired devices
- `hub` (string, required): Hub ID whose devices to revoke

### `ghost_hubs_list` (~32 tokens)

List Phantom Hubs in a network.

Input parameters:

- `network` (string): Network ID (uses default if omitted)

### `ghost_hubs_create` (~45 tokens)

Create a new Phantom Hub in a network.

Input parameters:

- `name` (string, required): Name for the new hub
- `network` (string): Network ID (uses default if omitted)

### `ghost_hubs_delete` (~26 tokens)

Delete a Phantom Hub.

Input parameters:

- `id` (string, required): Hub ID to delete

### `ghost_hubs_add_device` (~53 tokens)

Add a device to a Phantom Hub.

Input parameters:

- `device` (string, required): Device ID to add
- `hub` (string, required): Hub ID
- `network` (string): Network ID (uses default if omitted)

### `ghost_hubs_remove_device` (~53 tokens)

Remove a device from a Phantom Hub.

Input parameters:

- `device` (string, required): Device ID to remove
- `hub` (string, required): Hub ID
- `network` (string): Network ID (uses default if omitted)

### `ghost_helbind_list` (~52 tokens)

List Helbind Keys (device onboarding tokens), optionally filtered by network/hub.

Input parameters:

- `hub` (string): Hub ID to filter
- `network` (string): Network ID (uses default if omitted)

### `ghost_helbind_create` (~103 tokens)

Create a new Helbind Key for automated device onboarding.

Input parameters:

- `expires` (string, required): Expiration duration (e.g. '24h', '7d', '30d')
- `hub` (string): Hub ID to assign devices to
- `max_devices` (integer, required): Maximum number of devices that can use this key
- `name` (string): Friendly name for the key
- `network` (string): Network ID (uses default if omitted)

### `ghost_helbind_revoke` (~30 tokens)

Revoke a Helbind Key.

Input parameters:

- `id` (string, required): Helbind Key ID

### `ghost_helbind_status` (~33 tokens)

Get the status and details of a Helbind Key.

Input parameters:

- `id` (string, required): Helbind Key ID

### `ghost_bifrost_list` (~54 tokens)

List BiFrost Passes (temporary guest access), optionally filtered by network/hub.

Input parameters:

- `hub` (string): Hub ID to filter
- `network` (string): Network ID (uses default if omitted)

### `ghost_bifrost_create` (~96 tokens)

Create a new BiFrost Pass for temporary guest access. May take several minutes if a BiFrost VM needs provisioning.

Input parameters:

- `expires` (string, required): Expiration duration (e.g. '24h', '7d')
- `hub` (string, required): Hub whose devices the guest will access
- `max_devices` (integer, required): Maximum guest devices
- `network` (string): Network ID (uses default if omitted)

### `ghost_bifrost_revoke` (~32 tokens)

Revoke a BiFrost Pass.

Input parameters:

- `id` (string, required): BiFrost Pass ID

### `ghost_bifrost_status` (~35 tokens)

Get the status and details of a BiFrost Pass.

Input parameters:

- `id` (string, required): BiFrost Pass ID

### `ghost_vpn_list` (~32 tokens)

List Ghost VPN servers in a network.

Input parameters:

- `network` (string): Network ID (uses default if omitted)

### `ghost_vpn_create` (~48 tokens)

Create a new Ghost VPN server in a specific region.

Input parameters:

- `network` (string): Network ID (uses default if omitted)
- `region` (string, required): Region code for the VPN server

### `ghost_vpn_delete` (~40 tokens)

Delete a Ghost VPN server.

Input parameters:

- `id` (string, required): VPN server ID
- `network` (string): Network ID (uses default if omitted)

### `ghost_vpn_assign` (~40 tokens)

Assign a VPN server to a network.

Input parameters:

- `id` (string, required): VPN server ID
- `network` (string, required): Network ID to assign to

### `ghost_vpn_status` (~29 tokens)

Get the status of a Ghost VPN server.

Input parameters:

- `id` (string, required): VPN server ID

### `ghost_vpn_regions` (~18 tokens)

List available regions for Ghost VPN servers.

### `ghost_roles_list` (~41 tokens)

List device roles in a network.

Input parameters:

- `hub` (string): Hub ID to filter
- `network` (string): Network ID (uses default if omitted)

### `ghost_roles_set` (~86 tokens)

Set a device's role. Valid roles: admin, hub-admin, blind-node.

Input parameters:

- `device` (string, required): Device ID
- `hubs` (string): Comma-separated Hub IDs (required for hub-admin role)
- `network` (string): Network ID (uses default if omitted)
- `role` (string, required): Role to assign: admin, hub-admin, or blind-node

### `ghost_exitnode_broadcast` (~53 tokens)

Start broadcasting a device as an exit node (connector/Linux devices only).

Input parameters:

- `device` (string, required): Device ID to broadcast as exit node
- `network` (string): Network ID (uses default if omitted)

### `ghost_exitnode_stop_broadcast` (~47 tokens)

Stop broadcasting a device as an exit node.

Input parameters:

- `device` (string, required): Device ID to stop broadcasting
- `network` (string): Network ID (uses default if omitted)

### `ghost_exitnode_use` (~57 tokens)

Route a device's traffic through an exit node.

Input parameters:

- `device` (string, required): Device ID to route
- `exit_node` (string, required): Exit node device ID
- `network` (string): Network ID (uses default if omitted)

### `ghost_exitnode_remove` (~59 tokens)

Stop routing a device's traffic through an exit node.

Input parameters:

- `device` (string, required): Device ID to stop routing
- `exit_node` (string, required): Exit node device ID
- `network` (string): Network ID (uses default if omitted)

## Diagnostics

Captured diagnostic sections: Provenance. The full working is on the page: https://verifymcp.io/servers/net-gh-o-ghost-mcp/ghost-mcp-linux-x64#diagnostics

## Score history

- 2026-11-05: 40
- 2026-11-04: 39
- 2026-11-03: 39
- 2026-11-02: 39
- 2026-11-01: 38
- 2026-10-31: 38
- 2026-10-30: 37
- 2026-10-29: 37
- 2026-10-28: 36
- 2026-10-27: 36
- 2026-10-26: 35
- 2026-10-25: 35
- 2026-10-24: 34
- 2026-10-23: 34
- 2026-10-22: 33
- 2026-10-21: 33
- 2026-10-20: 32
- 2026-10-19: 32

## Common questions

### What is the Ghost Networks MCP server?

Ghost Networks is an MCP server listed in the public MCP registry as net.gh-o/ghost-mcp. Private, programmable networking for the AI age: manage networks, devices, hubs and VPN. This page covers its MCPB bundle (https://github.com/ghost-networks/ghost-mcp/releases/download/v0.41.0/ghost-mcp-linux-x64-v0.41.0.mcpb).

### Is the Ghost Networks MCP server safe to use?

Ghost Networks scores 40 out of 100 on VerifyMCP. 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 Ghost Networks MCP server expose?

Ghost Networks exposes 41 tools: ghost_init, ghost_status, ghost_refresh, ghost_use_network, ghost_logout, and 36 more. Their descriptions and schemas cost roughly 1,742 tokens of context every time the server is loaded.

### What did VerifyMCP test on the Ghost Networks MCP server?

VerifyMCP ran 12 checks on Ghost Networks, covering Source repository, Provenance, License, Maintenance and 8 more. 4 items could not be completed, a gap on our side rather than a finding about Ghost Networks: Malware scan, Known CVEs, Install scripts and Dependency health. One category scores 0 for that reason, because we only credit what we can confirm. Endpoint Security and Transport & Reachability do not apply to an MCPB bundle, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.

## Links

- Repository: https://github.com/ghost-networks/ghost-mcp
- Website: https://gh-o.net/
- Changelog RSS feed: https://verifymcp.io/servers/net-gh-o-ghost-mcp/ghost-mcp-linux-x64.xml
- Changelog JSON feed: https://verifymcp.io/servers/net-gh-o-ghost-mcp/ghost-mcp-linux-x64/changelog.json
- Trust report (JSON): https://verifymcp.io/servers/net-gh-o-ghost-mcp/ghost-mcp-linux-x64.json
- HTML version of this page: https://verifymcp.io/servers/net-gh-o-ghost-mcp/ghost-mcp-linux-x64