# io.github.anivdel/coolftp (npm · coolftp)

Deploy a site to its SFTP/FTP host from a coding agent. Changed files only, undo, live checks.

- Trust score: 73/100 (medium)
- Change this week: +3
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-09-25

## Components

- npm · `coolftp`: 73/100 (this document), [markdown](https://verifymcp.io/servers/anivdel-coolftp/coolftp.md), [page](https://verifymcp.io/servers/anivdel-coolftp/coolftp)

## Channel facts

- Registry: `npm`
- Package: `coolftp`
- Version: `0.1.2`
- Transport: `stdio`

## Trust breakdown

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. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-09-25.

- **Supply Chain Security**: 100/100
  - No malware found by supply-chain analysis.
  - No known CVEs affecting this package version or its production dependencies.
  - No install/post-install scripts declared.
  - No production dependencies, so there is no dependency health to assess.
- **Provenance & Transparency**: 45/100
  - Source repository is publicly reachable at the declared URL.
  - Provenance check failed: no build-provenance attestation is published.
  - Clear OSI-approved license (MIT).
  - Actively maintained (last published 14 days ago).
  - Disclosure check failed: no security disclosure policy was found in the source repository.
- **Schema Quality & AI Usability**: 65/100
  - AI-judged instruction clarity (good).
  - Context-footprint check failed: tool/resource definitions use about 2382 tokens (~132/item across 18 items; 18 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 47/100
  - Stability observed for 14 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 93/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 79% of tool parameters carry a description.
- **Tool Safety**: 75/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - 0 of 2 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation; "coolftp_deploy" implies "deploy" and declares no destructiveHint at all, which the MCP spec reads as destructive by default.
  - An AI judge read all 18 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

## Install

### How do I install the io.github.anivdel/coolftp MCP server?

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

### Claude

```bash
claude mcp add anivdel-coolftp -- npx -y coolftp
```

### Cursor

```json
{
  "mcpServers": {
    "anivdel-coolftp": {
      "command": "npx",
      "args": [
        "-y",
        "coolftp"
      ]
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "anivdel-coolftp": {
      "command": "npx",
      "args": [
        "-y",
        "coolftp"
      ]
    }
  }
}
```

### Codex

```bash
codex mcp add anivdel-coolftp -- npx -y coolftp
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "anivdel-coolftp": {
      "type": "local",
      "command": [
        "npx",
        "-y",
        "coolftp"
      ],
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add anivdel-coolftp --command npx --arg -y --arg coolftp
```

### Hermes

```yaml
mcp_servers:
  anivdel-coolftp:
    command: "npx"
    args: ["-y", "coolftp"]
```

### Netclaw

```json
{
  "McpServers": {
    "anivdel-coolftp": {
      "Transport": "stdio",
      "Command": "npx",
      "Arguments": [
        "-y",
        "coolftp"
      ]
    }
  }
}
```

### Vellum

```bash
assistant mcp add anivdel-coolftp -t stdio -c npx -a -y coolftp
```

### Other

```json
{
  "mcpServers": {
    "anivdel-coolftp": {
      "command": "npx",
      "args": [
        "-y",
        "coolftp"
      ]
    }
  }
}
```

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-09-25 (score 73, 0)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-09-24 (score 73, +1)

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

### 2026-09-22 (score 72, +1)

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

### 2026-09-20 (score 71, +1)

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

### 2026-09-18 (score 70, +3)

- [functional improvement] Stability: unverified → 0.23

### 2026-09-12 (score 67, +15)

- [security improvement] Malware scan: unverified → pass

### 2026-09-11 (score 52)

First indexed and scored.

## MCP tools (18)

### `coolftp_sites` (~31 tokens)

List the servers saved in coolFTP (name, host, protocol, remote root). Secrets are never returned.

### `coolftp_status` (~64 tokens)

Show which site the current project deploys to, whether the coolFTP desktop app is running (calls route through it when it is), and live connections.

Input parameters:

- `cwd` (string): Project directory. Defaults to the COOLFTP_PROJECT setting, else the MCP server working directory.

### `coolftp_init` (~204 tokens)

Link a project directory to a site by writing .coolftp.json. Do this once so later deploys need no site argument.

Input parameters:

- `build` (string): Command to run before each deploy, e.g. "npm run build"
- `cwd` (string): Project directory. Defaults to the COOLFTP_PROJECT setting, else the MCP server working directory.
- `ignore` (array): Extra gitignore-style patterns
- `keepBackups` (integer): Deploys whose previous versions stay on the server for undo (default 5, 0 disables)
- `localDir` (string): Sub-directory to deploy, e.g. "dist"
- `remoteRoot` (string): Remote directory for this project, if different from the site root
- `site` (string, required): Site name to deploy this project to
- `url` (string): Public URL that remote directory is served at, e.g. https://example.com. Enables post-deploy verification with correct URLs.

### `coolftp_diff` (~104 tokens)

Preview a deploy: which files would be added, changed or are stale on the server. Uploads nothing. Long lists are summarised by folder.

Input parameters:

- `cwd` (string): Project directory. Defaults to the COOLFTP_PROJECT setting, else the MCP server working directory.
- `force` (boolean): Compare as if nothing had been deployed
- `site` (string): Site name. Defaults to the site in the nearest .coolftp.json, or the only saved site.

### `coolftp_deploy` (~248 tokens)

Upload the project's changed files to its web server. Runs the configured build first. Use dryRun to preview, delete to remove stale remote files, commit to git-commit before deploying. The result says whether the site verified as live; only call it live when verify.ok is true. Previous versions of changed files stay on the server so coolftp_undo can revert.

Input parameters:

- `commit` (boolean): git add -A && git commit before deploying
- `cwd` (string): Project directory. Defaults to the COOLFTP_PROJECT setting, else the MCP server working directory.
- `delete` (boolean): Delete remote files that no longer exist locally
- `deleteUntracked` (boolean): Only with delete on a first deploy: also remove remote files coolFTP never uploaded. Ask the user before setting this.
- `dryRun` (boolean)
- `force` (boolean): Re-upload every file
- `message` (string): Short note stored with the deploy (and used as the commit message with commit=true)
- `site` (string): Site name. Defaults to the site in the nearest .coolftp.json, or the only saved site.
- `skipBuild` (boolean)

### `coolftp_undo` (~174 tokens)

Put back the previous versions the last deploy set aside on the server: overwritten files are restored, files it added are removed, files it deleted come back. Needs no git. Use dryRun to see what it would do. The coolFTP app asks the user to approve when it is open.

Input parameters:

- `cwd` (string): Project directory. Defaults to the COOLFTP_PROJECT setting, else the MCP server working directory.
- `dryRun` (boolean): Report what would be restored and removed without changing the server
- `message` (string)
- `site` (string): Site name. Defaults to the site in the nearest .coolftp.json, or the only saved site.
- `to` (string): Deploy id from coolftp_history to undo instead of the latest (only if no later deploy touched its files)

### `coolftp_verify` (~122 tokens)

Fetch the project's public URL and the files of the last deploy (or the given paths) and report status codes, plus whether static files are being served with the local bytes. Deploys nothing.

Input parameters:

- `cwd` (string): Project directory. Defaults to the COOLFTP_PROJECT setting, else the MCP server working directory.
- `paths` (array): Paths relative to the project's remote directory to check instead of the last deploy's files
- `site` (string): Site name. Defaults to the site in the nearest .coolftp.json, or the only saved site.

### `coolftp_rollback` (~167 tokens)

Put the server back to an earlier deploy's git commit. With no target, restores the previous commit that was live for this project. Requires git; for a quick revert of the last deploy without git use coolftp_undo. The coolFTP app asks the user to approve when it is open.

Input parameters:

- `build` (boolean): Run the project build command inside the checkout before deploying
- `cwd` (string): Project directory. Defaults to the COOLFTP_PROJECT setting, else the MCP server working directory.
- `message` (string)
- `site` (string): Site name. Defaults to the site in the nearest .coolftp.json, or the only saved site.
- `to` (string): Commit hash, branch, tag, or a deploy id from coolftp_history

### `coolftp_history` (~75 tokens)

Recent deploys for a site, newest first, with git commit, which agent did it, whether the live checks passed, and whether it can be undone.

Input parameters:

- `limit` (integer)
- `site` (string): Site name. Defaults to the site in the nearest .coolftp.json, or the only saved site.

### `coolftp_ls` (~123 tokens)

List a remote directory. Relative paths are relative to the project's remote directory from .coolftp.json (the same place deploy writes to), or the site root when the project has none. Paths starting with / are absolute on the server.

Input parameters:

- `cwd` (string): Project directory. Defaults to the COOLFTP_PROJECT setting, else the MCP server working directory.
- `path` (string): Remote directory; defaults to the project's remote directory
- `site` (string): Site name. Defaults to the site in the nearest .coolftp.json, or the only saved site.

### `coolftp_stat` (~128 tokens)

Check whether a remote path exists and get its type, size and date, without downloading it. Relative paths are relative to the project's remote directory from .coolftp.json (the same place deploy writes to), or the site root when the project has none. Paths starting with / are absolute on the server.

Input parameters:

- `cwd` (string): Project directory. Defaults to the COOLFTP_PROJECT setting, else the MCP server working directory.
- `path` (string, required)
- `site` (string): Site name. Defaults to the site in the nearest .coolftp.json, or the only saved site.

### `coolftp_read` (~123 tokens)

Read a text file from the server (up to 512 KB). Relative paths are relative to the project's remote directory from .coolftp.json (the same place deploy writes to), or the site root when the project has none. Paths starting with / are absolute on the server.

Input parameters:

- `cwd` (string): Project directory. Defaults to the COOLFTP_PROJECT setting, else the MCP server working directory.
- `path` (string, required)
- `site` (string): Site name. Defaults to the site in the nearest .coolftp.json, or the only saved site.

### `coolftp_write` (~130 tokens)

Write text content to a file on the server, creating parent directories. Relative paths are relative to the project's remote directory from .coolftp.json (the same place deploy writes to), or the site root when the project has none. Paths starting with / are absolute on the server.

Input parameters:

- `content` (string, required)
- `cwd` (string): Project directory. Defaults to the COOLFTP_PROJECT setting, else the MCP server working directory.
- `path` (string, required)
- `site` (string): Site name. Defaults to the site in the nearest .coolftp.json, or the only saved site.

### `coolftp_upload` (~174 tokens)

Upload a local file or directory to a remote path. The server confirms each file's size afterwards, and files inside the project's remote directory are recorded in the deploy manifest so the next deploy does not send them again. Relative paths are relative to the project's remote directory from .coolftp.json (the same place deploy writes to), or the site root when the project has none. Paths starting with / are absolute on the server.

Input parameters:

- `cwd` (string): Project directory. Defaults to the COOLFTP_PROJECT setting, else the MCP server working directory.
- `local` (string, required): Absolute or cwd-relative local path
- `remote` (string): Remote path; defaults to the project's remote directory
- `site` (string): Site name. Defaults to the site in the nearest .coolftp.json, or the only saved site.

### `coolftp_download` (~135 tokens)

Download a remote file or directory to a local path. Relative paths are relative to the project's remote directory from .coolftp.json (the same place deploy writes to), or the site root when the project has none. Paths starting with / are absolute on the server.

Input parameters:

- `cwd` (string): Project directory. Defaults to the COOLFTP_PROJECT setting, else the MCP server working directory.
- `local` (string, required): Local destination; defaults to the current directory
- `remote` (string, required)
- `site` (string): Site name. Defaults to the site in the nearest .coolftp.json, or the only saved site.

### `coolftp_mkdir` (~118 tokens)

Create a remote directory (and parents). Relative paths are relative to the project's remote directory from .coolftp.json (the same place deploy writes to), or the site root when the project has none. Paths starting with / are absolute on the server.

Input parameters:

- `cwd` (string): Project directory. Defaults to the COOLFTP_PROJECT setting, else the MCP server working directory.
- `path` (string, required)
- `site` (string): Site name. Defaults to the site in the nearest .coolftp.json, or the only saved site.

### `coolftp_delete` (~138 tokens)

Delete a remote file or directory. Refuses to delete the site root. The coolFTP app asks the user to approve when it is open. Relative paths are relative to the project's remote directory from .coolftp.json (the same place deploy writes to), or the site root when the project has none. Paths starting with / are absolute on the server.

Input parameters:

- `cwd` (string): Project directory. Defaults to the COOLFTP_PROJECT setting, else the MCP server working directory.
- `path` (string, required)
- `site` (string): Site name. Defaults to the site in the nearest .coolftp.json, or the only saved site.

### `coolftp_rename` (~124 tokens)

Rename or move a remote path. Relative paths are relative to the project's remote directory from .coolftp.json (the same place deploy writes to), or the site root when the project has none. Paths starting with / are absolute on the server.

Input parameters:

- `cwd` (string): Project directory. Defaults to the COOLFTP_PROJECT setting, else the MCP server working directory.
- `from` (string, required)
- `site` (string): Site name. Defaults to the site in the nearest .coolftp.json, or the only saved site.
- `to` (string, required)

## Diagnostics

Captured diagnostic sections: Provenance, Dependencies. The full working is on the page: https://verifymcp.io/servers/anivdel-coolftp/coolftp#diagnostics

## Score history

- 2026-09-25: 73
- 2026-09-24: 73
- 2026-09-23: 72
- 2026-09-22: 72
- 2026-09-21: 71
- 2026-09-20: 71
- 2026-09-19: 70
- 2026-09-18: 70
- 2026-09-17: 67
- 2026-09-16: 67
- 2026-09-15: 67
- 2026-09-14: 67
- 2026-09-13: 67
- 2026-09-12: 67
- 2026-09-11: 52

## Common questions

### What is the io.github.anivdel/coolftp MCP server?

io.github.anivdel/coolftp is an MCP server listed in the public MCP registry as io.github.anivdel/coolftp. Deploy a site to its SFTP/FTP host from a coding agent. Changed files only, undo, live checks. This page covers its npm package (coolftp).

### Is the io.github.anivdel/coolftp MCP server safe to use?

io.github.anivdel/coolftp scores 73 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 25 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.anivdel/coolftp MCP server expose?

io.github.anivdel/coolftp exposes 18 tools: coolftp_sites, coolftp_status, coolftp_init, coolftp_diff, coolftp_deploy, and 13 more. Their descriptions and schemas cost roughly 2,382 tokens of context every time the server is loaded.

### Is the io.github.anivdel/coolftp MCP server still maintained?

io.github.anivdel/coolftp is still listed as active in the MCP registry. We last reached this channel on 25 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.anivdel/coolftp MCP server under?

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

## Links

- npm package: https://www.npmjs.com/package/coolftp
- Socket report: https://socket.dev/npm/package/coolftp
- Repository: https://github.com/anivdel/coolFTP
- Website: https://coolftp.com/
- Changelog RSS feed: https://verifymcp.io/servers/anivdel-coolftp/coolftp.xml
- Changelog JSON feed: https://verifymcp.io/servers/anivdel-coolftp/coolftp.json
- HTML version of this page: https://verifymcp.io/servers/anivdel-coolftp/coolftp