Name: FTP Deploy
Author: alebgl77

FTP Deploy MCP

FTP/FTPS/SFTP deployment · Déploiement FTP/FTPS/SFTP. Local confinement / Confinement local.

Grade A Local · stdio No auth needed 14 tools v0.3.2

No reviews yet by alebgl77npm 585 Runs on your machine, nothing hosted

94/100

trust score

downloads a day

local

runs on your machine

585

downloads in 30d

What it does

FTP/FTPS/SFTP deployment · Déploiement FTP/FTPS/SFTP. Local confinement / Confinement local.

Quickstart

# 1 — add it to Claude Code
claude mcp add --scope user ftp-deploy-mcp '--' npx -y ftp-deploy-mcp

# 2 — ask your agent for something these tools do
#   ftp_list_servers, ftp_test, ftp_list and 11 more

FTP Deploy costs nothing on mcprush: there is no plan to choose here, no cap to set and nothing mcprush can bill you for.

Publishernot claimed

alebgl771 server

1 category

All 1 server

Collected from a public index. Nobody has claimed this account, so nothing here was written by its author — claim it if it is yours.

Installation

Where are you running it?

Every route below installs the same thing and ends at the same approval screen. This one runs on your machine: your client starts FTP Deploy as a process under your own user, with your files and your network, so the tool surface below is what it can do to your computer rather than to a server somewhere else. Its scan result is on the Security tab — read the surface before you approve it.

Claude Codedeclared by this listing

This is a public server: you run it yourself and this marketplace is not in the path. You need Node.js — the current LTS (24) is the safe choice; npx comes with it. Claude Code registers it in one command; --scope user makes it available in every project. The '--' is in quotes so that PowerShell passes it on.

claude mcp add --scope user ftp-deploy-mcp '--' npx -y ftp-deploy-mcp

Reconnect, or start a new session, and the tools appear in the model’s tool list.

Free on mcprush, and it runs from its publisher’s own package: this marketplace is not in the path, so there is no key of ours to hold and no card to add.

What it asks of you

Nothing is required, but it can take FTP_MCP_CONFIG (Explicit config path; missing or invalid paths fail closed. / Chemin explicite de configuration ; tout chemin absent ou invalide est refusé.), FTP_MCP_LANG (Human text language: en (default) or fr. / Langue du texte : en (défaut) ou fr.) if you want to set them.

What it writes

One config entry your client uses to start the process locally. A local server runs with your file system and your network, which is why it is priced without metering.

What you approve

14 tools, with what each one reads, writes and reaches shown before you agree — the same list on every route above. Read the tool surface.

Tool surface

What the model actually sees. Descriptions are diffed on every release — see version history.

Only tools that write or reach the network

List all configured FTP/FTPS/SFTP servers (name, protocol, host, port, root, read-only, auth kind) and which is default. Never reveals passwords or keys.

No parameter schema on file.

Connect to a server, list its root directory, and report success.

Parameter	Type	Required	Notes
server	string	no	Name of the configured server. Defaults to the configured default, or the sole server.

List the contents of a remote directory (relative to the server root). Directories are listed first.

Parameter	Type	Required	Notes
server	string	no	Name of the configured server. Defaults to the configured default, or the sole server.
path	string	no	Remote directory, relative to the server root. Defaults to the root.
limit	integer	no	Maximum entries to return (default 50, maximum 200).
offset	integer	no	Zero-based entry offset (default 0).

Read a remote text file and return its content. Binary files are refused (use ftp_download instead).

Parameter	Type	Required	Notes
server	string	no	Name of the configured server. Defaults to the configured default, or the sole server.
path	string	yes	Remote file path, relative to the server root.
max_bytes	integer	no	Maximum bytes to read (default …, hard max …).

Upload one local file to the server, auto-creating parent directories. Remote path defaults to the file basename at the root.

Parameter	Type	Required	Notes
server	string	no	Name of the configured server. Defaults to the configured default, or the sole server.
local_path	string	yes	Local file path, absolute or relative to the server's configured localRoot.
remote_path	string	no	Destination remote path, relative to the server root. Defaults to the local basename at the root.

Recursively upload a local directory to the server over a single connection, applying default and custom exclude globs (and optional include globs). Supports dry_run.

Parameter	Type	Required	Notes
server	string	no	Name of the configured server. Defaults to the configured default, or the sole server.
local_dir	string	yes	Local directory to deploy, absolute or relative to the server's configured localRoot.
remote_dir	string	no	Destination remote directory, relative to the server root. Defaults to the root.
include	array	no	Glob patterns; when given, a file must match at least one to be uploaded.
exclude	array	no	Extra glob patterns to exclude, added to the built-in defaults.
dry_run	boolean	no	If true, list what would be uploaded without connecting.

Download a remote file to a local path, auto-creating local parent directories. Refuses to overwrite unless overwrite:true.

Parameter	Type	Required	Notes
server	string	no	Name of the configured server. Defaults to the configured default, or the sole server.
remote_path	string	yes	Remote file path, relative to the server root.
local_path	string	yes	Local destination path, absolute or relative to the server's configured localRoot.
overwrite	boolean	no	Allow overwriting an existing local file.

Recursively create a remote directory (relative to the server root).

Parameter	Type	Required	Notes
server	string	no	Name of the configured server. Defaults to the configured default, or the sole server.
path	string	yes	Remote directory to create, relative to the server root.

Rename or move a remote file or directory (both paths relative to the server root).

Parameter	Type	Required	Notes
server	string	no	Name of the configured server. Defaults to the configured default, or the sole server.
from_path	string	yes	Existing remote path, relative to the server root.
to_path	string	yes	New remote path, relative to the server root.

Delete a remote file, or a directory when recursive:true. Never deletes the server root.

Parameter	Type	Required	Notes
server	string	no	Name of the configured server. Defaults to the configured default, or the sole server.
path	string	yes	Remote path to delete, relative to the server root.
recursive	boolean	no	Required to delete a directory and its contents.

No parameter schema on file.

Free

$0 forever

Every tool, no call limit
No card, and mcprush charges nothing for it
Source published under MIT
Runs on your machine — nothing of it reaches our gateway
Nothing to cap, because mcprush bills nothing

Nothing here is billable: mcprush charges nothing to install FTP Deploy or to call it, at any volume.

ATrust score 94 / 100

Release 0.3.2 · scanned 18 Oct 2026

Two independent axes, because powerful and malicious are different questions. The grade is threat only. The capability level is blast radius, and it is never a penalty on the grade — it is priced as one subtract-only term in the score, where you can see it.

Threat score100

Client score94

Findings3 threat · 0 capability

Capabilityhigh

Coveragesource

Verificationsource

Surface digeste6636c312134f4f88abeb7fc553907936aa1bc1cf3ba54581bc18f73c90b505e

Score vectorthreat 100 → client 94

Term	Level	What it prices	Points
capability-exposure	high	capability blast radius (high) — client exposure if the model is manipulated	−6
verification-discount	source	publisher verification (provenance) — cryptographic build provenance ties the artifact to its source	−0
coverage-honesty	source	inspection depth (source) — how much of the target the scan could see	−0

score = clamp(round(threatScore − E_cap − E_ver − E_cov), 0, 100). No model, no opinion, no network call at scoring time: the same methodology version against the same bytes always produces this number, and every line above is a field of the report rather than a summary of it.

What the scan could actually read

A grade is only as meaningful as its coverage, so the scanner publishes its own depth before it publishes its result.

Tool surfaceread

Implementation sourceread

Package metadataread

Live transportnot available

Tools were statically extracted from the published source (14 recovered), not enumerated from a running server. Tool-poisoning, Unicode-smuggling, capability and toxic-flow analysis ran on this inferred surface, but a mis-parsed registration could be missed or mis-attributed, so tool-derived findings are capped below “confirmed”. To grade the real runtime surface, scan the running server: --command "npx -y <package>".

Capability — what it could do if the model were manipulated

Tags derived from each tool’s schema and the implementation, not from what the tool calls itself. high is the level these add up to.

Tool	Capability tags	Why the tag was assigned
ftp_plan_deploy	no tags
ftp_apply_deploy	no tags
ftp_deploy_status	no tags
ftp_rollback_deploy	no tags
ftp_list_servers	no tags
ftp_test	no tags
ftp_list	no tags
ftp_read	no tags
ftp_upload	no tags
ftp_deploy	no tags
ftp_download	untrusted-input	untrusted-input: keyword "download"
ftp_mkdir	no tags
ftp_rename	no tags
ftp_delete	no tags

Toxic-flow graph

The lethal trifecta, checked as a graph rather than as a checklist: untrusted input, a sensitive source and an external sink have to meet before there is a path worth worrying about.

The public result for this release does not print the flow graph, so there is nothing to show here. That is not the same as "no paths were found": what the scan did read is above, under coverage.

Supply chain and provenance

Integrityfirst-seen

Surface digeste6636c312134f4f8

Scanned2026-10-18

This is the first scan of this surface here, so there is nothing yet to compare it against.

Every result on this tab comes from one deterministic pass over the published package — offline, rule by rule, and auditable line by line above. Same methodology version, same bytes, same score.