P
pom6i4/enclave-gateway
Run commands, transfer files and forward TCP connections from a macOS (Apple
★ 2·更新 2026-11-19
在 GitHub 查看 ↗直链 · 无中转页
我们没有可直接复制的安装命令,也没有公开的远端端点,所以不出配置。上面那条命令仅供参考,不是我们能担保的可复制命令——编一条出来比不给更糟。 各客户端的接法 →
- ★ 数取值
- 2 ★ · pom6i4/enclave-gateway · 取自 GitHub 搜索 API · (2026-11-19 20:00:48 核对)
- 来源明细
- 收录自 punkpeye/awesome-mcp-servers 榜单(我们从中收集的条目之一) · 条目类型:MCP 服务
- 收录与活跃
- 收录于 2026-11-18 · 最近见到 2026-11-20 · 共见到 3 次 · 被 3 个来源列出
- 评分构成
- 综合分 300 · 2 ★ · 3 个来源 · mcp
常见问题(答案都来自我们的记录)
它适合谁 / 用来做什么?
我们把它归在这些标签下: MCP 服务。标签来自条目自身,不是我们强加的分类。
谁维护它、还在更新吗?
仓库
pom6i4/enclave-gateway;我们收录于 2026-11-18;最近见到 2026-11-20。这里没有"官方认证"或"质量评级"——我们只记录来源与时间。README 原文(英文,未翻译) · 在 GitHub 读完整 README →
# Enclave Gateway (egw)
以下摘录自该仓库的 README(片段)
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.
收录徽章(可选)
想把收录标记放进 README 就复制这行,可选,不影响收录。
[](https://anclum.com/zh/s/pom6i4-enclave-gateway/)
- 来源
- awesome · https://github.com/pom6i4/enclave-gateway
- 按领域浏览
- MCP 服务
- Traction
- 2 ★
- 收录来源
- 3 个独立来源
- 收录于
- 今天
更多 MCP 服务器
所属领域与标签
每个标签都能点进去看同类的全部条目。数字是当前库里的真实条数。