Silicon Transfer MCP server

by SiliconAINetworks·io.github.SiliconAINetworks/silicon-transfer-mcp-server·v0.1.2·1 stars

No reviews yet

FTP/SFTP/FTPS MCP server with transfer proofs - every upload returns a checksum verdict.

A85/100grade A

Write a review Install

What users say

No reviews yet

Be the first

Safety scan

A85/100

full report

Adoption

Growing

1 stars27 downloads/wk

Reviews

Write one

Nobody has reviewed Silicon Transfer yet.

If you have run it, two minutes of your experience saves the next person an afternoon.

Silicon Transfer tools (13, 3 write)

write = sends, deletes, buys or posts

Read from the package source without running it. The installed server may list more.

silicon_connect
Verbindet zu einem FTP-, FTPS- oder SFTP-Server. SFTP unterstuetzt Passwort oder SSH-Key (privateKeyPath).
silicon_delete_filewrite action
Loescht eine Datei auf dem Server. Endgueltig - vorher mit silicon_list_dir pruefen.
silicon_disconnect
Trennt die aktive Verbindung sauber.
silicon_download_dir
Laedt ein Remote-Verzeichnis rekursiv herunter. Danach wird jede lokale Datei gegen die Remote-Quelle verglichen (hash/size/none, Standard size).
silicon_download_file
Laedt eine Remote-Datei herunter und liefert das Transfer-Urteil mit: PROVEN nur bei identischem SHA-256 zwischen Remote-Quelle und lokaler Kopie.
silicon_file_info
Groesse und SHA-256 einer Remote-Datei - der Fingerabdruck ohne Download auf Platte.
silicon_list_dir
Listet ein Remote-Verzeichnis mit Typ, Groesse und Aenderungsdatum.
silicon_make_dir
Legt ein Verzeichnis auf dem Server an (rekursiv moeglich).
silicon_rename
Benennt eine Remote-Datei oder ein Verzeichnis um bzw. verschiebt es.
silicon_server_info
Name, Version und Philosophie dieses MCP-Servers. Lebenszeichen-Check.
silicon_status
Zeigt, ob und wohin aktuell eine Verbindung besteht.
silicon_upload_dirwrite action
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.
silicon_upload_filewrite action
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.

Public scan report

scanner v0.1.9 · 2026-09-23 · same rubric, same numbers if you re-run it

no findings

Code scan13 source files scanned25/25
–Live reliabilityno gateway calls yet and no remote to proben/a
–Tool poisoningtools not inspected (local package is not executed); not countedn/a
Auth qualitylocal package, no credentials required12/15
Maintenancelast push 64 days ago12/15
Maintainer identityregistry namespace matches repository owner6/10

Overall 85/100. Components that don't apply are left out of the denominator. Any critical finding is an F.Rubric Appeal a finding JSON

How Silicon Transfer compares

Against every graded MCP server, from our own scans and uptime checks. Updated after each scan run.

Safety score: 85/100; higher than 70% of 48,255 servers
Tools: 13; the typical server has 7
Tools that change things: 23%; typical: 0%. Fewer write tools means less an agent can break
GitHub stars: 1; more than 65% of 28,688 servers
Downloads a week: 27; more than 14% of 12,191 servers with a package

What its tools let an agent do: 10 read · 3 change

Install Silicon Transfer in Claude Code, Cursor or VS Code

Runs npx -y silicon-transfer-mcp-server on your machine. Read the scan report first; the gateway never runs local packages.

claude mcp add silicon-transfer-mcp-server -- npx -y silicon-transfer-mcp-server

Add to Cursor

What the publisher says

From the Silicon Transfer repository's README, as published. We do not edit it. Read it on GitHub

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.

Why this one?

Tools (13)

Connection: siliconconnect, silicondisconnect, siliconstatus, siliconserverinfo Files: siliconuploadfile, silicondownloadfile, silicondeletefile, siliconfileinfo Directories: siliconlistdir, siliconmakedir, siliconuploaddir, silicondownloaddir, siliconrename

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-server

That's it - live on npm. Or run it without installing via npx (see config below).

From source

git clone https://github.com/SiliconAINetworks/silicon-transfer-mcp-server.git
cd silicon-transfer-mcp-server
npm install
npm run build

Claude Desktop configuration

Add to your claudedesktopconfig.json (no credentials in the config - you pass them at runtime through siliconconnect, for your own server**):

{
  "mcpServers": {
    "silicon-transfer": {
      "command": "npx",
      "args": ["-y", "silicon-transfer-mcp-server"]
    }
  }
}

Running from source instead

{
  "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 siliconconnect, then siliconupload_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

server - no defaults, no config files with secrets, no server addresses shipped.

No stored credentials. They are runtime-only tool parameters for your own

nothing is fetched from a remote registry at runtime, so no third party can rewrite what your assistant thinks a tool does.

No dynamic tool definitions. Every tool is fixed in the source you can read;

No telemetry, no phone-home, no analytics.

Sharp edges - operate accordingly

Shortened. The full README is on GitHub.

Nothing above is checked by us. What we check is on the safety report.

Silicon Transfer: common questions

Is Silicon Transfer MCP server safe?: Yes, by our scan: it is graded A (85/100). Read the Silicon Transfer safety report
How do I install Silicon Transfer?: It runs on your machine. Copy the Claude Code, Cursor, VS Code or Claude Desktop config from the install section.
Does Silicon Transfer need an API key?: Not as far as the registry entry and our scan can tell: no credentials are declared or required.
Is Silicon Transfer maintained?: The last commit was 106 days ago (2026-07-21). The latest release is v0.1.2.
How does Silicon Transfer compare with other MCP servers?: safety score 85/100 (higher than 70% of 48,255 servers); tools 13 (the typical server has 7); tools that change things 23% (typical: 0%. Fewer write tools means less an agent can break). Full comparison.