Ghost Networks
MCPB · LINUX-X64 · 4 COMPONENTS
Private, programmable networking for the AI age: manage networks, devices, hubs and VPN.
Available components
Last scanned (19 hours ago)
Scores higher than 73% of MCPB servers
Category Cloud Infrastructure
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 Security0
- 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.Unverified
- 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).Unverified
- Install-script risk not yet assessed.Unverified
- 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).Unverified
Provenance & Transparency32
- 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
- License check failed: no license is declared. See how to fix → Fail
- Actively maintained (last published 16 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability68
- AI-judged instruction clarity (good).Pass
- Tool/resource definitions use about 1742 tokens (~42/item across 41 items; 41 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management57
- Stability observed for 17 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Tool Safety75
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- 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. See how to fix → Fail
- An AI judge read all 41 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities20
- Spec-recency check failed: implements MCP spec 2024-11-05; the latest is 2026-07-28. See how to fix → Fail
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.
Checks we ran (12)
- Source repository
- Provenance
- License
- Maintenance
- Security disclosure
- Schema quality
- Stability
- Tool coverage
- Injection markers
- Destructive annotations
- Judged manipulation
- MCP protocol
Checks we could not complete (4)
These are gaps on our side, not findings about this package. We only credit what we can confirm, so a category made up entirely of them scores 0.
- Malware scan in Supply Chain Security (scores 0 for this)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 in Supply Chain Security (scores 0 for this)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 scripts in Supply Chain Security (scores 0 for this)Install-script risk not yet assessed.
- Dependency health in Supply Chain Security (scores 0 for this)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).
Does not apply to this package (2)
- Endpoint SecurityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.
- Transport & ReachabilityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.
The score does not measure everything. What the score does not measure →
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.
- 5 Nov 26 +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.
- 2 Nov 26 +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.
- 31 Oct 26 +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.
- 29 Oct 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.
- 27 Oct 26 +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.
- 25 Oct 26 +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.
- 23 Oct 26 +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.
- 21 Oct 26 +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.
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 5 Nov 2026 · Analysed mcpb/https://github.com/ghost-networks/ghost-mcp/releases/download/v0.41.0/ghost-mcp-linux-x64-v0.41.0.mcpb
Provenance No attestation
The registry publishes no build provenance for this version, so there is nothing to verify.
| Result | No attestation |
|---|---|
| Ecosystem | mcpb |
| Reason | No attestation published |
Background: How many MCP packages publish verified provenance →
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 →
ghost_bifrost_create ~96
Create a new BiFrost Pass for temporary guest access. May take several minutes if a BiFrost VM needs provisioning.
| Name | Type | Req | Description |
|---|---|---|---|
| expires | string | yes | Expiration duration (e.g. '24h', '7d') |
| hub | string | yes | Hub whose devices the guest will access |
| max_devices | integer | yes | Maximum guest devices |
| network | string | – | Network ID (uses default if omitted) |
No output schema declared.
No examples provided.
ghost_bifrost_list ~54
List BiFrost Passes (temporary guest access), optionally filtered by network/hub.
| Name | Type | Req | Description |
|---|---|---|---|
| hub | string | – | Hub ID to filter |
| network | string | – | Network ID (uses default if omitted) |
No output schema declared.
No examples provided.
ghost_bifrost_revoke ~32
Revoke a BiFrost Pass.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | BiFrost Pass ID |
No output schema declared.
No examples provided.
ghost_bifrost_status ~35
Get the status and details of a BiFrost Pass.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | BiFrost Pass ID |
No output schema declared.
No examples provided.
ghost_devices_add ~64
Add a pending device to the network using its 12-digit code.
| Name | Type | Req | Description |
|---|---|---|---|
| code | string | yes | 12-digit code shown on the device |
| name | string | yes | Nickname for the device |
| network | string | – | Network ID (uses default if omitted) |
No output schema declared.
No examples provided.
ghost_devices_bulk_revoke ~54
Revoke all devices in a hub. Optionally only revoke expired devices.
| Name | Type | Req | Description |
|---|---|---|---|
| expired_only | boolean | – | If true, only revoke expired devices |
| hub | string | yes | Hub ID whose devices to revoke |
No output schema declared.
No examples provided.
ghost_devices_get ~25
Get details for a specific device.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | Device ID |
No output schema declared.
No examples provided.
ghost_devices_list ~46
List devices in a network, optionally filtered by hub.
| Name | Type | Req | Description |
|---|---|---|---|
| hub | string | – | Hub ID to filter devices |
| network | string | – | Network ID (uses default if omitted) |
No output schema declared.
No examples provided.
ghost_devices_revoke ~46
Revoke (remove) a device from the network.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | Device ID to revoke |
| network | string | – | Network ID (uses default if omitted) |
No output schema declared.
No examples provided.
ghost_exitnode_broadcast ~53
Start broadcasting a device as an exit node (connector/Linux devices only).
| Name | Type | Req | Description |
|---|---|---|---|
| device | string | yes | Device ID to broadcast as exit node |
| network | string | – | Network ID (uses default if omitted) |
No output schema declared.
No examples provided.
ghost_exitnode_remove ~59
Stop routing a device's traffic through an exit node.
| Name | Type | Req | Description |
|---|---|---|---|
| device | string | yes | Device ID to stop routing |
| exit_node | string | yes | Exit node device ID |
| network | string | – | Network ID (uses default if omitted) |
No output schema declared.
No examples provided.
ghost_exitnode_stop_broadcast ~47
Stop broadcasting a device as an exit node.
| Name | Type | Req | Description |
|---|---|---|---|
| device | string | yes | Device ID to stop broadcasting |
| network | string | – | Network ID (uses default if omitted) |
No output schema declared.
No examples provided.
ghost_exitnode_use ~57
Route a device's traffic through an exit node.
| Name | Type | Req | Description |
|---|---|---|---|
| device | string | yes | Device ID to route |
| exit_node | string | yes | Exit node device ID |
| network | string | – | Network ID (uses default if omitted) |
No output schema declared.
No examples provided.
ghost_helbind_create ~103
Create a new Helbind Key for automated device onboarding.
| Name | Type | Req | Description |
|---|---|---|---|
| expires | string | yes | Expiration duration (e.g. '24h', '7d', '30d') |
| hub | string | – | Hub ID to assign devices to |
| max_devices | integer | yes | Maximum number of devices that can use this key |
| name | string | – | Friendly name for the key |
| network | string | – | Network ID (uses default if omitted) |
No output schema declared.
No examples provided.
ghost_helbind_list ~52
List Helbind Keys (device onboarding tokens), optionally filtered by network/hub.
| Name | Type | Req | Description |
|---|---|---|---|
| hub | string | – | Hub ID to filter |
| network | string | – | Network ID (uses default if omitted) |
No output schema declared.
No examples provided.
ghost_helbind_revoke ~30
Revoke a Helbind Key.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | Helbind Key ID |
No output schema declared.
No examples provided.
ghost_helbind_status ~33
Get the status and details of a Helbind Key.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | Helbind Key ID |
No output schema declared.
No examples provided.
ghost_hubs_add_device ~53
Add a device to a Phantom Hub.
| Name | Type | Req | Description |
|---|---|---|---|
| device | string | yes | Device ID to add |
| hub | string | yes | Hub ID |
| network | string | – | Network ID (uses default if omitted) |
No output schema declared.
No examples provided.
ghost_hubs_create ~45
Create a new Phantom Hub in a network.
| Name | Type | Req | Description |
|---|---|---|---|
| name | string | yes | Name for the new hub |
| network | string | – | Network ID (uses default if omitted) |
No output schema declared.
No examples provided.
ghost_hubs_delete ~26
Delete a Phantom Hub.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | Hub ID to delete |
No output schema declared.
No examples provided.
ghost_hubs_list ~32
List Phantom Hubs in a network.
| Name | Type | Req | Description |
|---|---|---|---|
| network | string | – | Network ID (uses default if omitted) |
No output schema declared.
No examples provided.
ghost_hubs_remove_device ~53
Remove a device from a Phantom Hub.
| Name | Type | Req | Description |
|---|---|---|---|
| device | string | yes | Device ID to remove |
| hub | string | yes | Hub ID |
| network | string | – | Network ID (uses default if omitted) |
No output schema declared.
No examples provided.
ghost_init ~66
Initialize Ghost CLI with an API key. Validates the key, generates crypto keys, and optionally joins a network via helbind key.
| Name | Type | Req | Description |
|---|---|---|---|
| api_key | string | yes | Ghost Networks API key |
| helbind_key | string | – | Path to key.json for automatic network join (optional) |
No output schema declared.
No examples provided.
ghost_logout ~15
Remove CLI configuration and log out.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
ghost_network_connect ~19
Connect to the active network via WireGuard tunnel.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
ghost_network_create ~27
Create a new Ghost network.
| Name | Type | Req | Description |
|---|---|---|---|
| name | string | yes | Name for the new network |
No output schema declared.
No examples provided.
ghost_network_disconnect ~16
Disconnect from the WireGuard tunnel.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
ghost_network_join ~58
Join an existing network. Without helbind_key, generates a 12-digit code that a network admin must approve. With helbind_key, joins automatically.
| Name | Type | Req | Description |
|---|---|---|---|
| helbind_key | string | – | Path to key.json for automatic join (optional) |
No output schema declared.
No examples provided.
ghost_network_list ~20
List all networks owned by or shared with this account.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
ghost_refresh ~19
Refresh plan, limits, and features from the server.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
ghost_roles_list ~41
List device roles in a network.
| Name | Type | Req | Description |
|---|---|---|---|
| hub | string | – | Hub ID to filter |
| network | string | – | Network ID (uses default if omitted) |
No output schema declared.
No examples provided.
ghost_roles_set ~86
Set a device's role. Valid roles: admin, hub-admin, blind-node.
| Name | Type | Req | Description |
|---|---|---|---|
| device | string | yes | Device ID |
| hubs | string | – | Comma-separated Hub IDs (required for hub-admin role) |
| network | string | – | Network ID (uses default if omitted) |
| role | string | yes | Role to assign: admin, hub-admin, or blind-node |
No output schema declared.
No examples provided.
ghost_status ~20
Show current account info, plan, limits, and features.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
ghost_use_network ~30
Set the default network for subsequent commands.
| Name | Type | Req | Description |
|---|---|---|---|
| network | string | yes | Network ID to set as default |
No output schema declared.
No examples provided.
ghost_vpn_assign ~40
Assign a VPN server to a network.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | VPN server ID |
| network | string | yes | Network ID to assign to |
No output schema declared.
No examples provided.
ghost_vpn_create ~48
Create a new Ghost VPN server in a specific region.
| Name | Type | Req | Description |
|---|---|---|---|
| network | string | – | Network ID (uses default if omitted) |
| region | string | yes | Region code for the VPN server |
No output schema declared.
No examples provided.
ghost_vpn_delete ~40
Delete a Ghost VPN server.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | VPN server ID |
| network | string | – | Network ID (uses default if omitted) |
No output schema declared.
No examples provided.
ghost_vpn_list ~32
List Ghost VPN servers in a network.
| Name | Type | Req | Description |
|---|---|---|---|
| network | string | – | Network ID (uses default if omitted) |
No output schema declared.
No examples provided.
ghost_vpn_regions ~18
List available regions for Ghost VPN servers.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
ghost_vpn_status ~29
Get the status of a Ghost VPN server.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | VPN server ID |
No output schema declared.
No examples provided.
ghost_wg_status ~23
Check WireGuard tunnel status: installed, connected, config path.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
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.
mcpb · linux-x64
Download bundleCheck the download matches the SHA-256 the MCP registry declares before you open it. If it does not match, do not open the file.
SHA-256
00cd7d2bd4e5cdf18252a85e727e77310536ca45b3adb1a8013b98dd1aac9b31
macOS / Linux
echo "00cd7d2bd4e5cdf18252a85e727e77310536ca45b3adb1a8013b98dd1aac9b31 ghost-mcp-linux-x64-v0.41.0.mcpb" | shasum -a 256 -c
Windows (PowerShell)
(Get-FileHash -Algorithm SHA256 .\ghost-mcp-linux-x64-v0.41.0.mcpb).Hash -eq "00cd7d2bd4e5cdf18252a85e727e77310536ca45b3adb1a8013b98dd1aac9b31"
Run it in the folder you saved the bundle to, then open the file with an MCPB-capable host such as Claude Desktop.
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.