Silicon Transfer MCP Server
OfficialIt gives an MCP client proven file transfer over FTP, FTPS and SFTP — every upload/download can return a PROVEN/MISMATCH verdict backed by SHA-256.
Connection management:
silicon_connect(protocol, host, port, username, password or SSH private key + passphrase),silicon_disconnect,silicon_status,silicon_server_info.Single-file transfer with proof:
silicon_upload_file/silicon_download_filewithproof: hash(default, SHA-256 of both sides),size, ornone.Recursive directory transfer with per-file proof walk:
silicon_upload_dir/silicon_download_dir(proof defaults tosizefor speed).Remote inspection:
silicon_list_dir(type, size, modified date) andsilicon_file_info(size + streamed SHA-256 fingerprint without downloading to disk).Remote filesystem changes:
silicon_make_dir(recursive),silicon_rename(rename/move), andsilicon_delete_file(permanent — verify withsilicon_list_dirfirst).Credential hygiene: credentials are runtime-only tool parameters — nothing stored in config, no telemetry, fixed tool set.
Click on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@Silicon Transfer MCP Server Connect to SFTP example.com and upload app.js with hash proof."
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
Silicon Transfer MCP Server
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?
Typical FTP tools | Silicon Transfer | |
Upload result | "done" | verdict + SHA-256 of both sides |
Directory sync check | manual | per-file proof walk with mismatch list |
Remote file fingerprint | download first | streamed SHA-256, no disk contact |
Protocols | often FTP only | FTP, FTPS, SFTP (password or SSH key) |
Related MCP server: Orphograph
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
npm install -g silicon-transfer-mcp-serverThat's it - live on npm. Or run it without installing via npx (see config below).
git clone https://github.com/SiliconAINetworks/silicon-transfer-mcp-server.git
cd silicon-transfer-mcp-server
npm install
npm run buildClaude 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):
{
"mcpServers": {
"silicon-transfer": {
"command": "npx",
"args": ["-y", "silicon-transfer-mcp-server"]
}
}
}{
"mcpServers": {
"silicon-transfer": {
"command": "node",
"args": ["C:/path/to/silicon-transfer-mcp-server/dist/index.js"]
}
}
}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:
{
"proof": {
"verdict": "PROVEN",
"detail": "SHA-256 identisch - Transfer bewiesen.",
"local_sha256": "9f2a...",
"remote_sha256": "9f2a..."
}
}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 security@siliconnetworks.ch.
License
MIT (c) 2026 Silicon Networks. Built from scratch - single-author codebase.
Available Tools
13 toolssilicon_connectVerbindung aufbauenAIdempotent
Verbindet zu einem FTP-, FTPS- oder SFTP-Server. SFTP unterstuetzt Passwort oder SSH-Key (privateKeyPath).
Inputs: host (required), protocol (required), username (required), port, +3 more.
silicon_delete_fileRemote-Datei loeschenADestructive
Loescht eine Datei auf dem Server. Endgueltig - vorher mit silicon_list_dir pruefen.
Inputs: remotePath (required).
silicon_disconnectVerbindung trennenBIdempotent
Trennt die aktive Verbindung sauber.
Inputs: no named parameters.
silicon_download_dirVerzeichnis herunterladen (mit Beweis-Wanderung)BRead-onlyIdempotent
Laedt ein Remote-Verzeichnis rekursiv herunter. Danach wird jede lokale Datei gegen die Remote-Quelle verglichen (hash/size/none, Standard size).
Inputs: localDir (required), remoteDir (required), proof.
silicon_download_fileDatei herunterladen (mit Beweis)ARead-onlyIdempotent
Laedt eine Remote-Datei herunter und liefert das Transfer-Urteil mit: PROVEN nur bei identischem SHA-256 zwischen Remote-Quelle und lokaler Kopie.
Inputs: localPath (required), remotePath (required), proof.
silicon_file_infoDatei-SteckbriefARead-onlyIdempotent
Groesse und SHA-256 einer Remote-Datei - der Fingerabdruck ohne Download auf Platte.
Inputs: remotePath (required).
silicon_list_dirVerzeichnis auflistenARead-onlyIdempotent
Listet ein Remote-Verzeichnis mit Typ, Groesse und Aenderungsdatum.
Inputs: path (required).
silicon_make_dirRemote-Verzeichnis anlegenAIdempotent
Legt ein Verzeichnis auf dem Server an (rekursiv moeglich).
Inputs: remotePath (required), recursive.
silicon_renameUmbenennen / VerschiebenB
Benennt eine Remote-Datei oder ein Verzeichnis um bzw. verschiebt es.
Inputs: toPath (required), fromPath (required).
silicon_server_infoServer InfoARead-onlyIdempotent
Name, Version und Philosophie dieses MCP-Servers. Lebenszeichen-Check.
Inputs: no named parameters.
silicon_statusVerbindungsstatusARead-onlyIdempotent
Zeigt, ob und wohin aktuell eine Verbindung besteht.
Inputs: no named parameters.
silicon_upload_dirVerzeichnis hochladen (mit Beweis-Wanderung)AIdempotent
Laedt ein lokales Verzeichnis rekursiv hoch. Danach wird jede Datei einzeln verglichen: proof=hash prueft SHA-256 pro Datei (gruendlich, langsamer), proof=size vergleicht Groessen (schnell), none ueberspringt.
Inputs: localDir (required), remoteDir (required), proof.
silicon_upload_fileDatei hochladen (mit Beweis)AIdempotent
Laedt eine lokale Datei hoch und liefert das Transfer-Urteil mit: PROVEN nur, wenn der SHA-256 der Remote-Datei nach dem Upload dem lokalen entspricht.
Inputs: localPath (required), remotePath (required), proof.
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
TDQS
Scored across 13 tools
Each tool has a distinct purpose: connection management, file/directory operations, uploads/downloads, and server info. No overlapping functions.
All tools follow the 'silver_verb_noun' pattern with snake_case, providing a clear and predictable naming convention.
13 tools is within the ideal range, covering core file transfer operations without being excessive or insufficient.
Covers essential operations for file transfer (connect, disconnect, list, upload, download), but lacks a dedicated directory deletion tool.
Maintenance
Related MCP Connectors
Protect and verify digital content with cryptographic signing and proof of ownership.
Privacy-preserving file proofs on Solana. Files are hashed locally. Currently free, no API key.
Tamper-evident SHA-256 hash-chained decision notary for EU AI Act, NIST AI RMF & SOC2.
Proof of existence for files: anchor a SHA-256 hash on Base, look up proofs. Paid with x402.
Related MCP Servers
- -licenseNot gradedqualityNot gradedmaintenanceEnables secure file transfer operations with remote Linux and Windows systems via SCP/SFTP protocols. Supports uploading, downloading, listing, and managing files on remote servers through SSH authentication.-

Orphographofficial
AlicenseNot gradedqualityBmaintenanceEnables AI agents and MCP hosts to anchor file hashes to Bitcoin via OpenTimestamps and verify proofs, ensuring files existed before a given time with privacy-preserving local hashing.MIT- AlicenseNot gradedqualityCmaintenanceSecure file exchange MCP server enabling AI agents to upload, share, fetch, and revoke files with SHA-256 verification, malware scanning, expiry, access restrictions, and human approval workflows.47 npmMIT
- AlicenseBqualityDmaintenanceProvides an FTP-like shared virtual filesystem for AI agents with SHA-256 integrity verification, metadata extraction, and access-hash based channels.31MIT