Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

io.github.SiliconAINetworks/silicon-transfer-mcp-server

NPM · SILICON-TRANSFER-MCP-SERVER · SCANNED SEP 22

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

0 this week 83 Trust /100
Trust breakdown (7 categories)

How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score → Why this is hard to score →

Supply Chain Security98
  • No malware found by supply-chain analysis.Pass
  • No known CVEs affecting this package version or its production dependencies.Pass
  • No install/post-install scripts declared.Pass
  • 44 of 115 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency45
Schema Quality & AI Usability74
  • AI-judged instruction clarity (good).Pass
  • Tool/resource definitions use about 866 tokens (~66/item across 13 items; 13 tools + 0 resources), lean.Pass
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management93
  • Stability observed for 28 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 100% of tool parameters carry a description.Pass
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • All 1 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation.Pass
  • An AI judge read all 13 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
  • Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Install

How do I install the io.github.SiliconAINetworks/silicon-transfer-mcp-server server?

io.github.SiliconAINetworks/silicon-transfer-mcp-server runs locally as an npm package, launched with npx -y silicon-transfer-mcp-server. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

npm · silicon-transfer-mcp-server

# add to Claude Code
claude mcp add siliconainetworks-silicon-transfer-mcp-server -- npx -y silicon-transfer-mcp-server
// .cursor/mcp.json
{
  "mcpServers": {
    "siliconainetworks-silicon-transfer-mcp-server": {
      "command": "npx",
      "args": [
        "-y",
        "silicon-transfer-mcp-server"
      ]
    }
  }
}
// .vscode/mcp.json
{
  "servers": {
    "siliconainetworks-silicon-transfer-mcp-server": {
      "command": "npx",
      "args": [
        "-y",
        "silicon-transfer-mcp-server"
      ]
    }
  }
}
# add to Codex CLI
codex mcp add siliconainetworks-silicon-transfer-mcp-server -- npx -y silicon-transfer-mcp-server
// opencode.json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "siliconainetworks-silicon-transfer-mcp-server": {
      "type": "local",
      "command": [
        "npx",
        "-y",
        "silicon-transfer-mcp-server"
      ],
      "enabled": true
    }
  }
}
# add to OpenClaw
openclaw mcp add siliconainetworks-silicon-transfer-mcp-server --command npx --arg -y --arg silicon-transfer-mcp-server
# ~/.hermes/config.yaml
mcp_servers:
  siliconainetworks-silicon-transfer-mcp-server:
    command: "npx"
    args: ["-y", "silicon-transfer-mcp-server"]
// ~/.netclaw/config/netclaw.json
{
  "McpServers": {
    "siliconainetworks-silicon-transfer-mcp-server": {
      "Transport": "stdio",
      "Command": "npx",
      "Arguments": [
        "-y",
        "silicon-transfer-mcp-server"
      ]
    }
  }
}
# add to Vellum
assistant mcp add siliconainetworks-silicon-transfer-mcp-server -t stdio -c npx -a -y silicon-transfer-mcp-server
// mcp.json
{
  "mcpServers": {
    "siliconainetworks-silicon-transfer-mcp-server": {
      "command": "npx",
      "args": [
        "-y",
        "silicon-transfer-mcp-server"
      ]
    }
  }
}
Changelog

Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.

  • 22 Sept 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 90 to 93. That category is still filling its 30-day observation window: 27 days of observed history at the previous scan, 28 at this one. The score rises as the window fills, whether or not the server changes.

  • 20 Sept 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 83 to 87. That category is still filling its 30-day observation window: 25 days of observed history at the previous scan, 26 at this one. The score rises as the window fills, whether or not the server changes.

  • 18 Sept 26 −3
    • Stability: pass → 0.80 functional
  • 17 Sept 26 +1
    • Stability: 0.97 → pass security
  • 15 Sept 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 90 to 93. That category is still filling its 30-day observation window: 27 days of observed history at the previous scan, 28 at this one. The score rises as the window fills, whether or not the server changes.

  • 13 Sept 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 83 to 87. That category is still filling its 30-day observation window: 25 days of observed history at the previous scan, 26 at this one. The score rises as the window fills, whether or not the server changes.

  • 10 Sept 26 −3
    • Stability: pass → 0.77 functional
  • 9 Sept 26 +1
    • Stability: 0.97 → pass security
Diagnostics

Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.

Captured 22 Sept 2026 · Analysed npm/silicon-transfer-mcp-server@0.1.2

Provenance No attestation

The registry publishes no build provenance for this version, so there is nothing to verify.

Result No attestation
Ecosystem npm

Background: How many MCP packages publish verified provenance →

Dependencies 115 packages
Packages resolved 115
Stale 44
Tree resolution Complete

Background: SBOMs and build attestations, explained →

MCP tools · 13 exposed · ~866 tokens

The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →

Tool Tokens
silicon_connect ~150

Verbindet zu einem FTP-, FTPS- oder SFTP-Server. SFTP unterstuetzt Passwort oder SSH-Key (privateKeyPath).

NameTypeReqDescription
hoststringyesHostname oder IP
passphrasestringPassphrase des SSH-Keys, falls verschluesselt
passwordstringPasswort (bei SSH-Key optional)
portintegerPort (Standard: 21 fuer ftp/ftps, 22 fuer sftp)
privateKeyPathstringPfad zu einem privaten SSH-Key (nur sftp)
protocolstringyesUebertragungsprotokoll
usernamestringyesBenutzername

No output schema declared.

No examples provided.

silicon_delete_file ~48

Loescht eine Datei auf dem Server. Endgueltig - vorher mit silicon_list_dir pruefen.

NameTypeReqDescription
remotePathstringyesRemote-Pfad der zu loeschenden Datei

No output schema declared.

No examples provided.

silicon_disconnect ~15

Trennt die aktive Verbindung sauber.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

silicon_download_dir ~86

Laedt ein Remote-Verzeichnis rekursiv herunter. Danach wird jede lokale Datei gegen die Remote-Quelle verglichen (hash/size/none, Standard size).

NameTypeReqDescription
localDirstringyesLokales Zielverzeichnis
proofstringBeweisstufe pro Datei (Standard: size)
remoteDirstringyesRemote-Quellverzeichnis

No output schema declared.

No examples provided.

silicon_download_file ~109

Laedt eine Remote-Datei herunter und liefert das Transfer-Urteil mit: PROVEN nur bei identischem SHA-256 zwischen Remote-Quelle und lokaler Kopie.

NameTypeReqDescription
localPathstringyesLokaler Zielpfad inkl. Dateiname
proofstringBeweisstufe: hash = SHA-256-Rueckvergleich (Standard), size = nur Groesse, none = ohne Urteil
remotePathstringyesRemote-Quellpfad

No output schema declared.

No examples provided.

silicon_file_info ~42

Groesse und SHA-256 einer Remote-Datei - der Fingerabdruck ohne Download auf Platte.

NameTypeReqDescription
remotePathstringyesRemote-Pfad der Datei

No output schema declared.

No examples provided.

silicon_list_dir ~44

Listet ein Remote-Verzeichnis mit Typ, Groesse und Aenderungsdatum.

NameTypeReqDescription
pathstringyesRemote-Pfad, z.B. /home/user/www

No output schema declared.

No examples provided.

silicon_make_dir ~55

Legt ein Verzeichnis auf dem Server an (rekursiv moeglich).

NameTypeReqDescription
recursivebooleanElternverzeichnisse mit anlegen
remotePathstringyesAnzulegender Remote-Pfad

No output schema declared.

No examples provided.

silicon_rename ~53

Benennt eine Remote-Datei oder ein Verzeichnis um bzw. verschiebt es.

NameTypeReqDescription
fromPathstringyesAktueller Remote-Pfad
toPathstringyesNeuer Remote-Pfad

No output schema declared.

No examples provided.

silicon_server_info ~25

Name, Version und Philosophie dieses MCP-Servers. Lebenszeichen-Check.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

silicon_status ~20

Zeigt, ob und wohin aktuell eine Verbindung besteht.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

silicon_upload_dir ~110

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.

NameTypeReqDescription
localDirstringyesLokales Quellverzeichnis
proofstringBeweisstufe pro Datei (Standard: size)
remoteDirstringyesRemote-Zielverzeichnis

No output schema declared.

No examples provided.

silicon_upload_file ~109

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.

NameTypeReqDescription
localPathstringyesLokaler Quellpfad
proofstringBeweisstufe: hash = SHA-256-Rueckvergleich (Standard), size = nur Groesse, none = ohne Urteil
remotePathstringyesRemote-Zielpfad inkl. Dateiname

No output schema declared.

No examples provided.

Common questions

What is the io.github.SiliconAINetworks/silicon-transfer-mcp-server server?

io.github.SiliconAINetworks/silicon-transfer-mcp-server is listed in the public MCP registry as io.github.SiliconAINetworks/silicon-transfer-mcp-server. FTP/SFTP/FTPS MCP server with transfer proofs - every upload returns a checksum verdict. This page covers its npm package (silicon-transfer-mcp-server).

Is the io.github.SiliconAINetworks/silicon-transfer-mcp-server server safe to use?

io.github.SiliconAINetworks/silicon-transfer-mcp-server scores 83 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 22 September 2026. It declares no install or post-install scripts. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

What tools does the io.github.SiliconAINetworks/silicon-transfer-mcp-server server expose?

io.github.SiliconAINetworks/silicon-transfer-mcp-server exposes 13 tools: silicon_server_info, silicon_connect, silicon_disconnect, silicon_status, silicon_list_dir, and 8 more. Their descriptions and schemas cost roughly 866 tokens of context every time the server is loaded.

Is the io.github.SiliconAINetworks/silicon-transfer-mcp-server server still maintained?

io.github.SiliconAINetworks/silicon-transfer-mcp-server is still listed as active in the MCP registry. We last reached this channel on 22 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

What licence is the io.github.SiliconAINetworks/silicon-transfer-mcp-server server under?

io.github.SiliconAINetworks/silicon-transfer-mcp-server declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.