Ftp (Kynlos) MCP Server

ftp-mcp npm v1.5.3

Published by kynlos — no publish provenance, so origin is unverified, but the source is public: the repository link below is self-declared yet readable, so you can inspect the code before adopting it.

Enterprise-grade MCP server providing heavily optimized FTP/SFTP operations with smart sync, patch/chunk streaming, caching, and explicit read-only security mappings for AI code assistants.

Trust grade
A
96/100
Last scanned get badge →
Trust
A · 96/100
Adoption risk for you: the threat score, then adjusted down for blast radius, publisher verification and how much the scan could see. Deterministic; every point is auditable.
Capability
Moderate
Blast radius if it went rogue — what the server’s tools could reach. Independent of trust.
Coverage
Source
How much the scan could actually inspect. Shallow coverage is stated, never hidden.
Share this Trust Score
𝕏 Share LinkedIn Reddit
A Why this grade threat 100 − adoption risk = 96/100

The grade answers one question — how safe is this server for you to adopt — so it is computed in two auditable stages. Nothing below is an opinion or an LLM's guess; every line is a real term the deterministic engine applied, and the same input always yields the same number.

1. Threat score — 100 − 0 = 100. What the published surface and source actually contain:

The deterministic scan raised no scored threat in the surface it inspected — the threat score stayed at 100. Capability observations and advisory notes are recorded but never lower it.

2. Client adoption risk — 100 − 4 = 96. Three small, subtract-only factors that reflect your risk in adopting it — a clean scan proves less on a powerful, unverified or barely-inspectable package, so the grade says so plainly:

PointsAdoption-risk factor
−3 capability blast radius (moderate) — client exposure if the model is manipulated
−1 publisher verification (public source) — no provenance, but the source is public and inspectable

Capability observations and info notes are shown under Findings but never scored. Open any row's finding below for the file, line and evidence behind a deduction.

Findings 5

high Reads a sensitive credential path or dumps the environment (index.js)MTC-SRC-006

In the server's implementation (`index.js:143`): Reading private keys / cloud credentials, or serializing the whole environment, is a sensitive-data source that becomes exfiltration when combined with any egress. This is read from the code itself — not from the tool description — so a poisoned server cannot hide it behind honest-looking metadata.

Evidence: rivate key (e.g. ~/.ssh/id_rsa). This path must be accessible from the environment where the MCP server is running.'

Fix: Review this call path: confirm it never receives unsanitized tool input, constrain it, or remove it. Treat a server whose code reaches these sinks as high-capability regardless of what its tools claim.

Location: server index.js

medium Tool "ftp_rmdir" can modify the filesystemMTC-CAP-002

Tool "ftp_rmdir" can write, overwrite or delete files (keyword "rmdir" in tool name). Verify it is scoped to a safe directory.

Fix: Constrain file operations to an explicit, non-sensitive root; reject path traversal.

Location: tool ftp_rmdir

low Mutating tool "ftp_rmdir" declares no destructiveHintMTC-CAP-005

Tool "ftp_rmdir" can mutate/egress but declares no destructiveHint. Clients that don't default to spec-safe behavior may not prompt before running it.

Fix: Declare accurate annotations, and gate destructive tools on user confirmation regardless.

Location: tool ftp_rmdir

low Unconstrained path parameter "path" on "ftp_list"MTC-CAP-008

Tool "ftp_list" takes a path parameter "path" with no constraint. Without a canonicalize-and-contain check (not visible statically), this permits ../ traversal outside the intended root.

Fix: Resolve and verify the path stays within an allowed root; reject traversal sequences.

Location: tool ftp_list · inputSchema.properties.path

low Unconstrained path parameter "path" on "ftp_rmdir"MTC-CAP-008

Tool "ftp_rmdir" takes a path parameter "path" with no constraint. Without a canonicalize-and-contain check (not visible statically), this permits ../ traversal outside the intended root.

Fix: Resolve and verify the path stays within an allowed root; reject traversal sequences.

Location: tool ftp_rmdir · inputSchema.properties.path

Tools 33

Each tool and what it can reach — statically extracted from the published source.

  • ftp_batch_downloadingests untrusted input
  • ftp_downloadingests untrusted input
  • ftp_listreads sensitive data
  • ftp_rmdirwrites files
  • audit-projectno sensitive capability
  • deploy-checklistno sensitive capability
  • deploymentno sensitive capability
  • ftp_analyze_workspaceno sensitive capability
  • ftp_batch_uploadno sensitive capability
  • ftp_chmodno sensitive capability
Show 23 more tools ↓
  • ftp_connectno sensitive capability
  • ftp_copyno sensitive capability
  • ftp_deleteno sensitive capability
  • ftp_deployno sensitive capability
  • ftp_disk_spaceno sensitive capability
  • ftp_existsno sensitive capability
  • ftp_get_contentsno sensitive capability
  • ftp_list_deploymentsno sensitive capability
  • ftp_list_transactionsno sensitive capability
  • ftp_mkdirno sensitive capability
  • ftp_patch_fileno sensitive capability
  • ftp_probe_capabilitiesno sensitive capability
  • ftp_put_contentsno sensitive capability
  • ftp_renameno sensitive capability
  • ftp_rollbackno sensitive capability
  • ftp_searchno sensitive capability
  • ftp_statno sensitive capability
  • ftp_syncno sensitive capability
  • ftp_telemetryno sensitive capability
  • ftp_treeno sensitive capability
  • ftp_uploadno sensitive capability
  • pathno sensitive capability
  • Remote File Contentno sensitive capability

What this scan could not see

Versions 1

Scan history per published version. The engine is deterministic — the same version always yields the same score, so a changed score means the package itself changed.

VersionScoreFindingsEngineScanned
v1.5.3 latest A 96/100 5 1.13.0 2026-09-07

Embed this score

Show this server's live Trust Score in your README, docs or website. The badge is served straight from the registry and updates automatically after every rescan — no API key needed. It links back to this page, so anyone who sees the grade can also read the findings behind it instead of taking a number on faith.

MCP Trust Score: A · 96/100
Markdown (GitHub README)
[![MCP Trust Score](https://mcptrustchecker.com/registry/ftp-mcp/badge.svg)](https://mcptrustchecker.com/registry/ftp-mcp)
HTML
<a href="https://mcptrustchecker.com/registry/ftp-mcp"><img src="https://mcptrustchecker.com/registry/ftp-mcp/badge.svg" alt="MCP Trust Score" height="20"></a>
Prefer shields.io styling? Point it at https://mcptrustchecker.com/registry/ftp-mcp/badge.json via https://img.shields.io/endpoint?url=…

Verify this score yourself

The score above is reproducible: the same package version always yields the same result. Run it locally or over the free API — no account, no LLM, fully deterministic.

npx mcptrustchecker scan ftp-mcp --online

Use the free API → How scoring works

Other implementations of Ftp 1

Independent packages implementing the same tool, scanned with the same engine. Compare all 2 side by side →

More in AI & Agents