VAMP Vault for Apple Silicon

io.github.wayfarer6由 GitHub 帳號 wayfarer6 發布v0.1.24更新於 Nov 22, 2026

Manage KeePassXC credentials, VeraCrypt volumes and SSH Vaults on Apple Silicon.

概覽

AI 產生的概覽

專為 Apple Silicon 設計的在地 MCP 套件,讓助理檢視並使用 KeePassXC 憑證、VeraCrypt 加密磁碟區與 SSH Vault。

可以做什麼
  • 檢查 Vault 狀態,以及 KeePassXC、VeraCrypt 命令列工具是否可用
  • 查詢已儲存的憑證,並在核准後把憑證值投遞到設定好的接收端並回傳回執
  • 掛載指定的 VeraCrypt 加密磁碟區,並從磁碟區匯出解密後的文件副本
  • 將憑證使用與磁碟區掛載記錄到本機稽核日誌,可依時間、腳本或代理查詢
適用情境
當 Apple Silicon Mac 上的助理工作流程需要已儲存的憑證或加密磁碟區時適用,例如掛載容器並匯出檔案,而不必把機密貼進對話中。
執行需求
以本機程序方式在 Apple Silicon Mac 上執行;README 要求 Node.js 22 或更新版本,並使用原生 arm64 Node.js。對應功能需要已安裝 KeePassXC 與 VeraCrypt 命令列工具。未宣告任何環境變數或標頭。
安裝前請注意
它會處理憑證與加密磁碟區:憑證投遞會在使用者核准後把機密值傳送到設定的接收端,磁碟區操作可能暴露解密後的資料。掛載與匯出會寫入磁碟,並記錄在本機稽核日誌中。請檢查接收端設定,並避免把真實機密與資料放進共享的工作流程包。

安裝

在 SourceWeft 中

  1. 開啟 儀表板中的 VAMP Vault for Apple Silicon,將其新增到工作區。
  2. 為需要使用其工具的對話啟用該服務。

Desktop only,透過 STDIO。 STDIO 服務會啟動本機處理程序,因此需要 SourceWeft 桌面主機。

其他 MCP 客戶端

參照 儲存庫 中的啟動說明。

README

[VAMP Logo]

VAMP · Virtual Agent Machine Platform

Run AI computer-use agents in VMs on your own hardware.

[CI checks on main] [Latest Release] [VS Code Extension] [Script Hub] [License: MIT]

English · 한국어 · User Guide · Script Hub · Roadmap


MCP listening IP and port

By default each server advertises two tools, vamp_search_tools and vamp_execute_tool for VAMP, or vault_search_tools and vault_execute_tool for Vault. Ask “Which ports are the two servers listening on?” The model can search for listener status, then execute the matching tool with an empty arguments object. Search an exact name to read its input schema. Reconnect clients that cache the old catalog. For client-side approvals per individual tool, set VAMP_TOOL_MODE=full in the server environment and restart. In search mode, client approval for the executor covers every tool it can invoke. Server-side approvals still apply.

Open VAMP: Security Settings or VAMP Vault: Security Settings. Choose a NIC and port, then copy the client bearer token from the same menu. Use the server’s reachable IP in http://<ip>:<port>/mcp. Each listener starts disabled. 0.0.0.0 listens on all IPv4 interfaces. Use a trusted encrypted network or TLS tunnel for remote access. The MCP tools vamp_listener_status, vamp_listener_configure, vault_listener_status and vault_listener_configure manage the same listeners. A standalone MCP can also listen for the lifetime of its stdio session.

One-line MCP install

With Codex CLI and Node.js 22 or later installed, run the command for your computer. On Apple Silicon, use native arm64 Node.js.

Windows PowerShell

powershell
irm https://raw.githubusercontent.com/wayfarer6/vamp-mcp/577c376d40a6d50dc3d0d8a8eda205b1deb6531f/scripts/windows/install-mcp.ps1 | iex

Ubuntu Desktop, Ubuntu Server, or Ubuntu in WSL 2 (Bash)

Open Bash on your Ubuntu PC or in an SSH session to your Ubuntu server. For WSL 2, open the Ubuntu terminal in Windows. In that shell, check that node --version reports v22 or later and codex --version finds the Linux CLI. The installer also uses curl and Python 3.

bash
(set -o pipefail; curl -fsSL https://raw.githubusercontent.com/wayfarer6/vamp-mcp/577c376d40a6d50dc3d0d8a8eda205b1deb6531f/scripts/linux/install-mcp.sh | bash)

Run the installer as the user who runs Codex. It writes to ~/.vamp/mcp/vamp-mcp-linux/0.3.26/. Paste the printed prompt into Codex on that same Ubuntu host and account to register the server and verify it with rpa_search. An empty list is a successful connection. On WSL, this registration belongs to Ubuntu and is separate from Windows.

Apple Silicon Mac terminal

bash
curl -fsSL https://raw.githubusercontent.com/wayfarer6/vamp-mcp/577c376d40a6d50dc3d0d8a8eda205b1deb6531f/scripts/macos/install-mcp.sh | bash

Paste the English prompt printed by the installer into Codex. On Windows, open Codex as administrator. If this is the first registration, reopen Codex and paste the same prompt again to verify the connection.

Reuse part of a GUI recording

A pair of Python comments marks an editable step. Choose Block between step comments and enter its ID to keep the step attached to the code when lines move.

python
# vamp-step: open-menup.press('f2')# vamp-end: open-menu

For an existing recording, ask the agent to preview step comments with rpa_revision(action="annotate"). The preview includes the source and updated step plan. Applying it creates a revision that needs review.

In RPA Library, select a Python recording and choose Create GUI RPA → Reusable steps → Add step. Give the step a name, select its first and last source lines, and enter visible text for its starting and finished screens. After review, a second RPA can select Step from a reviewed revision and append its own local steps. VAMP pins the original Git commit and saves the combined actions in the new RPA.

mermaid
flowchart LR  A["Reviewed menu step at a fixed revision"] --> B["Check Inventory menu"]  B --> C["Warehouse report step"]  B --> D["Factory report step"]  D --> E{"Production balance visible?"}  E -->|Yes| F["Record checkpoint"]  E -->|No| G["Stop and inspect effects"]  G --> H["Edit report step and review"]  H --> I["Recheck entry and resume report"]

Select the script in the source preview and click Edit to open the file in VS Code. For a saved skill, use Edit details and steps to review and save the new revision. When a run stops, inspect the reported step and any changes already made. To resume in MCP, provide the reviewed expected_commit, from_step, and effects_reconciled: true with the usual target, inputs and confirmation. VAMP checks that step’s entry screen before sending input. English demo · Captions

After annotating a shared step, existing workflows still reference their original commit. Review the new shared revision, then update the pin in the workflows that should adopt it. Watch the preview, review and pin update · Captions

See VAMP in 30 seconds

Try a warehouse close. Ask “Close the warehouse for the month.” Codex finds a reviewed GUI recording and LibreOffice Calc writes an Excel workbook for four synthetic SKUs. The demo checks all 24 formulas and the closing value after saving. English video · Example and setup · Finished XLSX

Record a task yourself. Open the guest recorder, enable button crops for later YOLO review, and choose Save Python. A writable recording share makes the source visible on the host. Review and save it in RPA Library for agent reuse. Manual demonstrations do not generate fallback code. A failed verified click stops replay. Watch the guide · Captions

From the VAMP VS Code extension, open a VirtualBox guest and verify that its Debian desktop is live.

[Demo preview: open a VirtualBox guest by name and verify its live Debian desktop in VAMP]

▶ Watch the English demo (0:30)

English and Korean video guides include the 30-second demo, installation and AI connection, architecture, and a hands-on VM lab.

See which Linux KVM calls were recorded automatically, how to read the two outcomes, and what a Vault credential lookup proves. Audit log video · English, 1:51

Find a saved run by script and agent, then open its queued and verified events in VS Code. SQLite audit walkthrough · English, 0:47 · GUI and CLI library design proposal

Build the automation today. Tomorrow, just change the order number.

Today, work with a large model to export an order from your ERP to CSV. Save the steps along with a check that the new file contains the requested order number. Tomorrow, ask a smaller model to “export order 1042 the same way.” It finds the workflow in the RPA Library and passes the new order number through MCP. VAMP runs the saved steps on your device and checks the CSV.

You can share a reviewed workflow with a colleague. Export a specific version of a GUI RPA as a source ZIP. Your colleague can inspect the code and inputs, then reuse it in a compatible environment on their device with their own order number. Leave passwords and real order data out of the package. Reusing the steps can lower model costs on repeat runs because a large model no longer has to plan each click or command anew.

VAMP 0.3.21 uses Apple Neural Engine and CPU through Core ML for YOLO and PaddleOCR on Apple Silicon. Run the vision setup with native Python 3.12 after upgrading. Mac setup

Import a saved GUI RPA ZIP or unpacked export folder with vamp-mcp rpa install ./workflow.zip. Import a shared Python or Playwright workflow JSON from a terminal with vamp-mcp rpa install ./workflow.json (add --dry-run to preview), and inspect the catalog with vamp-mcp rpa list. Import neither runs the workflow nor installs dependencies. Set up the VM workspace and review the exact revision in VS Code before running it. Catalog and revision options

VAMP 0.3.20 streams CLI workflow artifacts over SSH. Upgrade the host and guest worker together for files larger than 1 MiB. Guest worker setup

VAMP 0.3.15 includes saved Python and Playwright workflows alongside GUI recordings. Open the RPA Library to import an order-export example, review its code for your VM and run it with a different order number. The CLI worker supports Linux guests on VirtualBox, KVM and Hyper-V. GUI RPA guide · CLI setup and order example

mermaid
flowchart TD    A["Define steps and success checks with a large model"] --> G["GUI RPA · available today"]    A --> C["Python or Playwright workflow"]    G --> L["Review and save a version on your device"]    C --> L    L --> M["Your small model calls it with its ID and inputs"]    L --> P["Share a reviewed version"]    P --> T["Colleague reviews and sets it up on their device"]    T --> N["Their small model calls it with their own inputs"]    M --> R["VAMP runs and verifies the task on each device"]    N --> R    R --> DB["SQLite audit log for this profile"]    V["Vault credential use and volume mounts"] --> DB    DB --> Q["MCP search by time, script or agent"]    DB --> U["VS Code audit log and run details"]

If an AI provider raises its API prices or discontinues its service, you can keep using the saved workflow by maintaining its execution environment and connecting another small model that supports MCP. You decide how to edit the script and whom to share it with.

Even if you switch models, the workflows you’ve built stay on your device.

Which agent ran a script?

VAMP: Open Audit Log shows the latest matching event per run over the last 24 hours. Combine a local time range, script name or UUID, agent ID and activity type. Select a row to open its timeline.

Ask your AI to “Find runs of the order export script by orders-agent between 9 and 10 this morning and show their verification results.” It can use audit_search and audit_run_details. For a stable ID across restarts, set VAMP_AGENT_ID=orders-agent on that agent’s dedicated MCP server. Otherwise the server automatically assigns a process-session ID. SQLite location, profiles and query examples

Verify a recorded click

When saving a recording, enter the text on each button or its specific YOLO class. Replay checks the guest before each press. The default minimum score is 90%. In RPA Library → Recorded click verification, set 1–100% or turn verification off. You can also tell your agent “Use 95% for this run only.” Recognition, fallback and MCP examples

Ask your AI to install VAMP

In Claude Code or Codex with terminal access, paste the request for your operating system.

text
https://github.com/wayfarer6/vamp-mcpInstall VAMP MCP on my Windows PC from the latest official release. Verify the packagechecksum, connect it to this AI client, and list my VMs using the backend I use onthis PC (VirtualBox or Hyper-V) to confirm it works.
text
https://github.com/wayfarer6/vamp-mcpInstall VAMP MCP on my Linux PC from the latest official release. Verify the packagechecksum, connect it to this AI client, and list my VMs using the backend I use onthis PC (VirtualBox or KVM) to confirm it works.

macOS (Apple Silicon)

text
https://github.com/wayfarer6/vamp-mcpInstall VAMP MCP on my Apple Silicon Mac and connect it to this AI client.Check that Node.js 22 or later and UTM are installed. Use the official MCP Registryentry io.github.wayfarer6/vamp-mcp-macos to find the current darwin-arm64.mcpband verify its SHA-256. If this client needs a stdio command, use Node.js andthe entry point in the extracted bundle’s manifest. Then call utm_candidatesand show me the VM names and power states, or confirm that the inventory is empty.

English first-run guide: web-chat prompts, install commands, screenshots, and the order CSV demo · English walkthrough video (3:02) · 한국어 가이드

Next video · VAMP MCP architecture in Korean (3:04). Follow a request from the AI client to the guest and compare VirtualBox, KVM, and Hyper-V.

English architecture video · VirtualBox, KVM and Hyper-V architecture (1:53).

How to use

Supported hosts: Windows, Linux, and macOS on Apple Silicon. On Apple Silicon, UTM is the only local VM backend. The Mac VSIX and MCPB packages support Debian 13 arm64 guests, rootless Podman in the guest, and remote SSH targets. macOS setup guide and videos

Hyper-V on Windows. Enable Hyper-V and select VM Manager → Connection → Virtualization platform → Hyper-V. VAMP supports VM creation and lifecycle management, the external VMConnect console, and file transfer with supported Windows guests. The Robot Framework console workflow can start the VM and open VMConnect. It is distinct from embedded screenshot and input control and from saved GUI device replay. Hyper-V setup and Robot console workflow

Windows MCP requirement. VAMP and VAMP Vault MCP servers require Windows administrator privileges. The vamp-mcp CLI can request UAC to start the server in a separate elevated process while the MCP client stays open. For a direct server command, start it from an administrator terminal. To use the MCP servers provided by the VS Code extensions, start VS Code with Run as administrator. Direct server startup exits when Windows has not granted administrator privileges.

Contributions are welcome. See the contribution guide and AI contributor instructions.

Run GUI automation inside a guest while you keep using your host desktop. With saved RPA, local replay can check the screen and output files without sending frames to a model. An external agent can receive screen data if its client requests it during exploration or targeted fallback. Vault-managed secrets can be delivered through the approved guest connection.

For SSH-based remote GUI automation, see the WSL2 remote MCP worker guide.

WSL2 remote MCP guides (English · 한국어).

Watch the VAMP overview in English for the architecture and first steps. The English installation guide starts on the Windows host with MCP package and VSIX installation and follows both routes through Debian startup in VirtualBox.

Watch the Windows VirtualBox Notepad verification in English or Korean. The Robot Framework run opens Notepad and checks the Windows (CRLF) status bar in a 1920×1080 guest.

💡 Why VAMP?

When you export an ERP order every day, the order number changes but the steps often stay the same. Keep the reviewed workflow and its outcome check on your own machine. On the next run, give an MCP-capable model the new order number. GUI replay checks buttons on the guest screen. CLI workflows run their scripts inside a bound Linux guest. Reusing the steps can reduce repeated vision API calls and lets colleagues run the same workflow with their own inputs.


⚖️ How VAMP Compares

MetricScreen-driven CUAFixed recorded RPAVAMP saved RPA
Vision token costProvider usage depends on screenshot callsNo provider calls during fixed replayLocal replay and verification use no provider vision tokens. AI-assisted repair is measured separately.
Execution latencyIncludes screen-driven model callsIncludes scripted inputs and waitsIncludes guest inputs, waits, and configured local checks
After a layout changeCan inspect the new screen before actingRequires explicit starting-screen and outcome checks to detect a mismatchCan stop before input on a configured starting-screen mismatch and hand off for targeted repair
Windows VirtualBox ERP checkElapsed timeVerified outcome
Saved replay on the original layout35.97 s17 actions and a fresh CSV with all three expected orders
Saved replay after scratch verification and review54.44 s30 actions and a fresh CSV with the expected SHA-256
Robot Framework scenario across both layouts239.05 sTwo matching CSVs and zero inputs from the stale replay

In a separate matched comparison with three runs per method and layout, VAMP saved replay verified all three v1 CSVs and stopped all three v2 runs before sending input. Fixed keyboard replay produced three incorrect v2 CSVs, and screen-driven CUA verified all six CSVs across both layouts. Median timings and evidence


⚡ Core Architecture & Highlights

Guest control and VM management

VirtualBox, KVM and Hyper-V provide VM lifecycle operations. Saved GUI device replay (rpa_run_saved) supports VirtualBox and KVM with local VNC. On Hyper-V, open the guest console in VMConnect directly or with the Robot console workflow. Python and Playwright CLI workflows have been validated in Linux guests on all three backends. The runner sends the reviewed version over SSH and runs it in rootless Podman inside the bound guest. CLI guest setup and examples

Screen verification and Vault

OCR and YOLO workers on the replay host analyze guest frames. VAMP Vault is a separate MCP server. For managed Windows mounts, it checks approval and the KeePassXC entry’s binding to the volume file, then sends the stored key to the WSL VeraCrypt CLI over stdin. After initial setup and Vault unlock, subsequent approved mounts can reuse the key. Screen verification · Vault setup

📦 Guest bootstrapping

VirtualBox fetches post-install resources over its build NAT. Hyper-V Windows uses the selected switch's host IPv4, while Hyper-V Debian reads offline answer media and uses a static network profile after installation. QEMU's default build NAT reaches the host at 10.0.2.2, independently of the deployed libvirt network. VM MCP setup and troubleshooting

For a Debian golden image on Hyper-V, prepare a dedicated internal switch with WinNAT and reserve a static guest address before starting the build. If an older image build stalled at Default Switch DHCP or network preseed, start a fresh build with the offline answer ISO. Keep the golden export separate from the live VM disk. Debian Hyper-V setup and recovery


🚀 Quick Start

1. Use MCP without VS Code

With Node.js 22 or later, install the VAMP bundle in an MCPB-compatible client. Add the separate Vault bundle if you use it. On Windows, the bundle requires an already elevated host. For manual downloads, verify the file against the release’s SHA256SUMS. VAMP MCP · Vault MCP · GitHub Releases

On Apple Silicon, install the Mac registry entries. Call utm_candidates to check VAMP and vault_status to check the optional Vault and its KeePassXC and VeraCrypt CLIs. VAMP MCP · macOS · VAMP Vault · macOS

On first local startup, VAMP prepares Packer and Vagrant. Check host_cli_status for the paths and set VAMP_AUTO_DOWNLOAD=0 to opt out. Vault prepares VeraCrypt through WinGet on Windows, native Installer on macOS (including FUSE-T when required), and verified portable downloads on supported Linux hosts. Vault also prepares a missing KeePassXC CLI through WinGet on Windows, a verified app bundle on macOS, or a verified AppImage on supported Linux hosts. Check vault_status for the result. Set VAULT_AUTO_DOWNLOAD=0 to opt out.

2. Use the VS Code extensions

  1. Download both VSIX files from GitHub Releases. Use Extensions: Install from VSIX separately for each file. Install VAMP MCP Tools first, wait for it to finish, then install VAMP Vault and reload VS Code.
  2. Open the VAMP activity bar. Use Open VM Manager for VMs, Open Containers for the Podman inventory and desktop actions, and RPA Library for reviewed workflows. Manage credentials in VAMP Vault separately.
  3. For WSL, follow the manual setup guide. See Container desktops for rootless Podman, noVNC, capture, and limitations.

For Windows host PowerShell policy and separate Hyper-V/CIM permission checks, see the Windows host guide.

After installing, check the VAMP entries with code --list-extensions --show-versions. The versions should match the two downloaded file names. If a bundled Marketplace version appears, reinstall the corresponding VSIX separately.

Record, replay, and repair a task

  1. Set up the guest and use the same guest resolution for recording and replay. The Windows VirtualBox setup uses 1920×1080 after initialization.
  2. In RPA Library, search for a reviewed workflow first. To create a new one, record the task in the guest, review the captured actions, and remove sensitive input before saving. For a standalone Robot Framework package, use the PyAutoGUI conversion guide.
  3. Replay the reviewed workflow on the selected guest. Check the expected screen or output file before treating it as successful.
  4. If the screen changed, inspect the affected area and propose a targeted repair. Test the repair in a separate VirtualBox guest, then review the verified revision before using it again. See the recording and repair workflow.

For Windows replay on VirtualBox or KVM with a local VNC display that may encounter a guest UAC prompt, enable pause_on_uac. The recording and guest display must both be 1920×1080. VAMP checks the guest screen with local OCR and stops for operator review. To continue the same run after approval in the guest console, also set uac_wait_seconds and a unique uac_resume_text that appears in the expected app. See the guest UAC replay workflow.


🏗️ Architecture Overview

mermaid
flowchart TD    subgraph Host ["Host machine"]        Agent["AI agent / MCP client"]        MCP["VAMP MCP (vamp-mcp)"]        subgraph VaultService ["VAMP Vault MCP (vamp-mcp-vault)"]            Vault["Vault tools · user approval"]            DB["KeePassXC KDBX · credentials and volume owner agent IDs"]            VC["VeraCrypt"]            Vault --> DB            Vault -->|Approved Windows mount| WSL["WSL VeraCrypt CLI"]            WSL --> VC            Vault --> VC        end        HTTP["Postinstall Script Server :8421"]        RPA["Robot Framework / Python RPA runner"]        Vision["Local YOLO / OCR workers"]        Desktop["Desktop adapter"]
        Agent <-->|MCP Stdio Protocol| MCP        Agent <-->|MCP stdio · tools and receipts| Vault        MCP --> HTTP        UI["VS Code · RPA Library"]        Catalog["Reviewed workflows and click settings"]        CLI["CLI runner over SSH"]        Audit["Profile-scoped SQLite audit log"]        MCP --> Catalog        UI --> Catalog        Catalog --> RPA        Catalog --> CLI        RPA --> Audit        CLI --> Audit        Vault --> Audit        Audit --> Query["MCP audit queries and VS Code audit panel"]        RPA -->|Recorded press with verification enabled| Guard{"One target above threshold and stable after pointer move?"}        Guard -->|Yes| Desktop        Guard -->|Blocked| Audit        RPA -->|Keyboard or explicitly unchecked press| Desktop        Desktop -->|Captured frames| RPA        RPA -->|Selected images| Vision        Vision -->|Detections and text| RPA    end
    subgraph Infrastructure ["Virtualization Abstraction Layer"]        Packer["Packer (Golden Image Provisioning)"]        Vagrant["Vagrant & DesktopAdapter"]        MCP --> Packer        MCP --> Vagrant        Packer -->|Golden Images| Vagrant        Vagrant -->|VirtualBox / KVM / Hyper-V| VM    end
    VM["Isolated VM desktop"]    Container["Isolated desktop container"]    CLI --> GuestJob["Linux guest · rootless Podman · script and outcome check"]    Disk["Assigned VeraCrypt volume"]    VC --> Disk    Disk -->|Secondary disk| VM    Disk -->|Scoped workspace| Container    Vault -->|Approved credential to configured receiver| VM    Vault -->|Approved credential to configured receiver| Container    Desktop <-->|Console capture and input| VM    Desktop <-->|Managed RFB capture and input| Container

Robot Framework and Python run on the controller host, alongside the local YOLO and OCR workers. The desktop adapter captures the target's screen and sends keyboard and mouse events, as a person would through a VM console. With a remote VM, the remote hypervisor host handles console capture and input over SSH while the controller can analyze the returned frames locally. Supported operations depend on the desktop backend.

The MCP client calls VAMP MCP for desktop control and calls VAMP Vault MCP separately for credentials and encrypted volumes. After user approval, vault_deliver_credential sends a value directly to the configured receiver and returns a delivery receipt over MCP.


When the screen changes between checking and clicking (TOCTOU)

An ERP’s Save button can be correctly recognized, then covered by a tooltip as the pointer moves. A list refresh can also put a different order at the same coordinates. This gap between observing state (time of check) and acting on it (time of use) creates a TOCTOU race. A 99% recognition score describes the first frame. The interface can still change before the press. TOCTOU definition

  1. Identify the target on the first frame. Require one matching reviewed OCR label or specific YOLO class, a score at or above the configured minimum (90% by default), and a location consistent with the recording.
  2. Move the pointer and capture again. Check the guest geometry and compare pixels around the target and click point. Press only if the region is stable. Repeat the check for each press in a multi-click action.
  3. Hold the click when the target changes. A missing target, low score or changed region gets one fresh attempt. A second failure stops later input. Duplicate matches stop immediately. Explicit coordinate-only replay skips this visual check.

The final capture and input delivery are separate operations. Identical-looking buttons can also refer to different records. Give the workflow an independent outcome check, such as verifying that the newly exported CSV contains the requested order ID. Click guard implementation · Proposed hover handling

Where the code lives

ComponentSource
Recording and conversionvamp-recorder.py · recording_converter.py
GUI replay and click checksreplay.py · click_guard.py
CLI catalog and runscli-catalog.cjs · cli-runs.cjs
Audit storage and UIaudit.cjs · audit-panel.cjs
Vault MCP and mountingserver.mjs · vault_cli.mjs
VS Code extensions and MCP distributionvscode-extension · registry

🌐 Community Script Hub

Don't reinvent the wheel. Browse pre-built, community-verified RPA packages on the VAMP Script Hub:

  • Portal logins (Naver, Google, GitHub, Slack)
  • Enterprise PDF document generation
  • File extraction and scheduled status reporting

🔒 Responsible Use & Security

VAMP is built for research, productivity, and secure local automation.

  • User approval: Require explicit confirmation for sensitive actions.
  • Isolated Sandbox: Use sandboxed credentials and test environments. You remain responsible for all operations executed inside guest VMs.
  • Open Source: Licensed under the MIT License. Third-party components retain their respective licenses (see THIRD_PARTY_NOTICES.md).

來源:README.md,提交 df633d3

工具

0
SourceWeft 曾在隔離沙箱中以無憑證方式啟動該軟體包一次,以列出其工具,但未能完成:該軟體包類型無法在沙箱中執行。

版本歷史

3
  1. v0.1.24最新Nov 22, 2026
  2. v0.1.21Nov 22, 2026
  3. v0.1.19Nov 22, 2026

評分

已滿足適用檢查項的 50%

該評分衡量此收錄條目的完整程度,依據註冊中心條目、端點與公開來源計算得出。它不是對伺服器本身的評價,也不表示伺服器安全或目前可用:可連通性是帶日期的檢查結果,評分也不包含安裝量或使用者評價。

  • 近 30 天內可連通25 分

    請保持端點能夠回應 MCP 握手;SourceWeft 每 30 天探測一次。

  • 已宣告認證方式10 分

    請在註冊中心條目中宣告憑證請求標頭,或保持端點能夠回應探測,以便判定其認證方式。

  • 已列出工具15 分

    請讓伺服器在無憑證時回應 tools/list,或發布可在沙箱中無憑證啟動的軟體包。

  • 描述必需15 分
  • 圖示10 分
  • 文件15 分
  • 授權條款10 分