Silicon Transfer Mcp Server
io.github.SiliconAINetworks由 GitHub 帳號 SiliconAINetworks 發布v0.1.2更新於 Oct 24, 2026
FTP/SFTP/FTPS MCP server with transfer proofs - every upload returns a checksum verdict.
概覽
支援 FTP、FTPS 與 SFTP 的 MCP 伺服器,每次上傳與下載都會回傳 SHA-256 校驗結論。
- 可以做什麼
- 連線、中斷連線並檢視 FTP/FTPS/SFTP 伺服器資訊與狀態
- 上傳、下載與檢視單一檔案,可選雜湊、大小或不校驗
- 列出、建立與重新命名遠端目錄
- 上傳或下載整個目錄樹,並逐檔提供校驗結果
- 刪除遠端檔案與目錄
- 以串流 SHA-256 計算遠端檔案指紋,不必先下載
- 適用情境
- 適合讓助理透過 FTP、FTPS 或 SFTP 在遠端伺服器之間搬移檔案,並需要可驗證的傳輸證明,而不是只回一句「完成」。也適合核對遠端檔案指紋,或將本機目錄與遠端目錄做比對。
- 執行需求
- 以本機 Node.js 程序執行,可從 npm 全域安裝或以 npx 啟動。主機、使用者名稱與憑證(密碼或 SSH 金鑰路徑)在執行時透過連線工具傳入,設定檔中不保存憑證。
安裝
在 SourceWeft 中
- 開啟 儀表板中的 Silicon Transfer Mcp Server,將其新增到工作區。
- 為需要使用其工具的對話啟用該服務。
Desktop only,透過 STDIO。 STDIO 服務會啟動本機處理程序,因此需要 SourceWeft 桌面主機。
其他 MCP 客戶端
參照 儲存庫 中的啟動說明。
README
Silicon Transfer MCP Server
[npm version] [npm downloads] [license] [node]
FTP / FTPS / SFTP for Claude and other MCP clients - with built-in transfer proofs.
Every upload and download returns a verdict: PROVEN only when the SHA-256 of the
remote file matches your local file. No more "transfer complete" on blind trust.
Philosophy: prove it, then claim it. Built from scratch by Silicon Networks - the makers of AEGIS Shield.
The complete kit: pair it with Silicon Skills - nine working rules for coding agents. The
safe-deployskill tells your agent how to deploy (local first, pull live state, stage, verify); this server gives it the tools and the proof.
Why this one?
Tools (13)
Connection: silicon_connect, silicon_disconnect, silicon_status, silicon_server_info
Files: silicon_upload_file, silicon_download_file, silicon_delete_file, silicon_file_info
Directories: silicon_list_dir, silicon_make_dir, silicon_upload_dir, silicon_download_dir, silicon_rename
Transfers accept proof: "hash" | "size" | "none" - hash is the default for single
files, size for directory trees (switch to hash when it matters).
Install
That's it - live on npm. Or run it without installing via npx (see config below).
From source
Claude Desktop configuration
Add to your claude_desktop_config.json (no credentials in the config - you pass
them at runtime through silicon_connect, for your own server):
Running from source instead
Usage example
Ask your AI assistant:
"Connect to my server via SFTP (host example.com, user deploy, key at ~/.ssh/id_ed25519) and upload dist/app.js to /var/www/app.js - with hash proof."
The assistant calls silicon_connect, then silicon_upload_file and answers with the
verdict:
If the hashes ever differ you get MISMATCH with both fingerprints - retry instead
of trusting a broken deploy.
Security notes
Built with the OWASP Top 10 for Agentic Applications (2026) in mind - specifically ASI02 (Tool Misuse) and ASI04 (Agentic Supply Chain).
What this server does not do
- No stored credentials. They are runtime-only tool parameters for your own server - no defaults, no config files with secrets, no server addresses shipped.
- No dynamic tool definitions. Every tool is fixed in the source you can read; nothing is fetched from a remote registry at runtime, so no third party can rewrite what your assistant thinks a tool does.
- No telemetry, no phone-home, no analytics.
Sharp edges - operate accordingly
silicon_delete_file, silicon_delete_directory and silicon_sync_deploy
(with deleteExtras) can destroy remote data. An assistant reading untrusted
content - a web page, a PDF, an email - can be steered by instructions hidden
inside it (indirect prompt injection). Treat these tools like rm -rf:
- Connect with an account scoped to the directory you intend to touch, never root.
- Prefer SSH keys over passwords; give the key its own restricted account.
- Run
silicon_list_dirbefore any delete, and read the plan before approving. - Keep
deleteExtrasoff unless you are deliberately mirroring.
Verifying what you installed
Package name is exactly silicon-transfer-mcp-server, published by
aegisshield888. Similar names on npm are placeholders we registered to prevent
typosquatting - they contain no code. Source: the GitHub repository linked above.
Reporting
Found a hole? Open an issue on GitHub, or write to [email protected].
License
MIT (c) 2026 Silicon Networks. Built from scratch - single-author codebase.
來源:README.md,提交 6ddd78a
工具
0版本歷史
1- v0.1.2最新Sep 16, 2026
評分
已滿足適用檢查項的 50%
該評分衡量此收錄條目的完整程度,依據註冊中心條目、端點與公開來源計算得出。它不是對伺服器本身的評價,也不表示伺服器安全或目前可用:可連通性是帶日期的檢查結果,評分也不包含安裝量或使用者評價。
- 近 30 天內可連通25 分
請保持端點能夠回應 MCP 握手;SourceWeft 每 30 天探測一次。
- 已宣告認證方式10 分
請在註冊中心條目中宣告憑證請求標頭,或保持端點能夠回應探測,以便判定其認證方式。
- 已列出工具15 分
請讓伺服器在無憑證時回應 tools/list,或發布可在沙箱中無憑證啟動的軟體包。
- 描述必需15 分
- 圖示10 分
- 文件15 分
- 授權條款10 分