P
pom6i4/enclave-gateway
Run commands, transfer files and forward TCP connections from a macOS (Apple
★ 2·updated 2026-11-19
View on GitHub ↗Direct link · no redirect page
We have no copy-paste install command and no public remote endpoint, so we do not print a config. The step above is reference only, not a command we can vouch for. A made-up one is worse than none. How each client wires MCP up →
- Star count
- 2 ★ · pom6i4/enclave-gateway · read from the GitHub search API · (checked 2026-11-19 20:00:48)
- Source
- collected from the punkpeye/awesome-mcp-servers list · type: MCP server
- Harvest history
- first seen 2026-11-18 · last seen 2026-11-20 · seen 3× · listed by 3 sources
- Score
- score 300 · 2 ★ · 3 sources · mcp
FAQ (answers come from our records)
Who is it for?
We filed it under these tags: MCP servers. The tags come from the entry itself, not a taxonomy we imposed.
Who maintains it?
repository
pom6i4/enclave-gateway;first catalogued 2026-11-18;last seen 2026-11-20。There is no official certification or quality rating here — we record sources and dates only.README excerpt (English, untranslated) · Read the full README on GitHub →
# Enclave Gateway (egw)
Excerpted from the repository README (abridged)
English · Русский
Run commands, transfer files and forward TCP connections from a macOS (Apple
Silicon arm64 or Intel x86_64), Linux or Windows Host through an isolated Windows
VPN Appliance and an RDP Bastion (TCP 3389), even when inbound SSH to Bastion is
closed. The Appliance uses QEMU HVF / KVM / WHPX with matching Host/guest
architectures; Windows Direct mode uses the existing Host instead of an isolated
VM. Use the organization's approved Windows VPN client: ViPNet Client,
АПКШ Континент, Cisco AnyConnect / Secure Client, OpenVPN, WireGuard or a custom
provider. egw connects a local CLI or MCP client to the enclave's TargetNodes.
text
Host → QGA → Windows Appliance → RDP redirected drive → Bastion worker → SSH → TargetNode
The diagram shows the RDP route. When policy permits SSH, use the
agentless route without a Bastion worker.
Beta software. Standard mode is for a trusted operator and RDP session.
Enterprise adds signed native isolation and verified identities. Neither mode
replaces the organization's endpoint policy, VPN entitlement or host-key approval.
The current version is 0.3.0 Beta 6 (0.3.0b6). The foreground
structured_only profile is experimental and requires explicit endpoint
approval. KES compatibility is not certified. See release boundaries.
## Key capabilities
QEMU Appliance & 6 VPN Provider Adapters — vipnet, kontinent,
anyconnect, openvpn, wireguard, custom. Installed-binary probes inspect
PE architecture (arm64 / x86_64 / x86), Authenticode and exact configured
versions/publisher. Matching configuration does not qualify a driver or VPN
session. Optional egw provider install|connect|disconnect|import_key plans use
a hash-pinned lifecycle manifest; apply requires its reviewed approval digest.
No proprietary command line or key-import procedure is inferred.
Transactional RDP VFS Transport — [MS-RDPEFS] / \\tsclient redirected
files, without custom virtual-channel .dll installation. Parallel Striped I/O
and block deltas use SHA-256, default 4 MiB blocks and optional zlib compression.
Standard executes commands in warm PowerShell runspaces; transfer scripts use
a RunspacePool. No C# compiler or additional worker .exe is required.
Operator-started OpenSSH — the experimental structured_only profile
can use operator with Stream for egw exec and egw cp to one Linux target
through an approved RDP session.
Use egw cp --chunked for files up to 512 MiB after the worker advertises
chunked_copy_slots_v1: true. Every 1 MiB block is verified with SHA-256.
On the isolated Windows Server 2022 RDP lab with KES 14.1, 3 MiB and 65 MiB
transferred in both directions. All 136 blocks met the 15 s limit, with a
slowest block of 2.692 s and zero new KES events.
Setup and qualification scope.
Multi-Hop SSH, SOCKS5 & Port Forwarding — egw exec, cp and sync;
bidirectional TCP multiplexing and RFC 1928 SOCKS5 (egw socks5); OpenSSH
ProxyCommand (egw ssh, stdio-proxy, ssh-config); supervised forwards
(egw forward), terminal monitoring (egw top) and layered L1–L7 diagnostics
(egw doctor, heal). SSH requires verified host keys and credentials on the
executing hop; transport compatibility and latency need deployment validation.
Run commands, transfer files and forward TCP connections from a macOS (Apple
Silicon arm64 or Intel x86_64), Linux or Windows Host through an isolated Windows
VPN Appliance and an RDP Bastion (TCP 3389), even when inbound SSH to Bastion is
closed. The Appliance uses QEMU HVF / KVM / WHPX with matching Host/guest
architectures; Windows Direct mode uses the existing Host instead of an isolated
VM. Use the organization's approved Windows VPN client: ViPNet Client,
АПКШ Континент, Cisco AnyConnect / Secure Client, OpenVPN, WireGuard or a custom
provider. egw connects a local CLI or MCP client to the enclave's TargetNodes.
text
Host → QGA → Windows Appliance → RDP redirected drive → Bastion worker → SSH → TargetNode
The diagram shows the RDP route. When policy permits SSH, use the
agentless route without a Bastion worker.
Beta software. Standard mode is for a trusted operator and RDP session.
Enterprise adds signed native isolation and verified identities. Neither mode
replaces the organization's endpoint policy, VPN entitlement or host-key approval.
The current version is 0.3.0 Beta 6 (0.3.0b6). The foreground
structured_only profile is experimental and requires explicit endpoint
approval. KES compatibility is not certified. See release boundaries.
## Key capabilities
QEMU Appliance & 6 VPN Provider Adapters — vipnet, kontinent,
anyconnect, openvpn, wireguard, custom. Installed-binary probes inspect
PE architecture (arm64 / x86_64 / x86), Authenticode and exact configured
versions/publisher. Matching configuration does not qualify a driver or VPN
session. Optional egw provider install|connect|disconnect|import_key plans use
a hash-pinned lifecycle manifest; apply requires its reviewed approval digest.
No proprietary command line or key-import procedure is inferred.
Transactional RDP VFS Transport — [MS-RDPEFS] / \\tsclient redirected
files, without custom virtual-channel .dll installation. Parallel Striped I/O
and block deltas use SHA-256, default 4 MiB blocks and optional zlib compression.
Standard executes commands in warm PowerShell runspaces; transfer scripts use
a RunspacePool. No C# compiler or additional worker .exe is required.
Operator-started OpenSSH — the experimental structured_only profile
can use operator with Stream for egw exec and egw cp to one Linux target
through an approved RDP session.
Use egw cp --chunked for files up to 512 MiB after the worker advertises
chunked_copy_slots_v1: true. Every 1 MiB block is verified with SHA-256.
On the isolated Windows Server 2022 RDP lab with KES 14.1, 3 MiB and 65 MiB
transferred in both directions. All 136 blocks met the 15 s limit, with a
slowest block of 2.692 s and zero new KES events.
Setup and qualification scope.
Multi-Hop SSH, SOCKS5 & Port Forwarding — egw exec, cp and sync;
bidirectional TCP multiplexing and RFC 1928 SOCKS5 (egw socks5); OpenSSH
ProxyCommand (egw ssh, stdio-proxy, ssh-config); supervised forwards
(egw forward), terminal monitoring (egw top) and layered L1–L7 diagnostics
(egw doctor, heal). SSH requires verified host keys and credentials on the
executing hop; transport compatibility and latency need deployment validation.
Listed badge (optional)
Copy this line into the README if you want the listing mark. Optional, and it does not affect being listed.
[](https://anclum.com/en/s/pom6i4-enclave-gateway/)
- Source
- awesome · https://github.com/pom6i4/enclave-gateway
- Browse by field
- MCP servers
- Traction
- 2 ★
- Listed by
- 3 independent sources
- added
- today
More MCP servers
Filed under
Every tag opens the full list for that filter. Counts are the live catalogue figures.