io.github.anivdel/coolftp
NPM · COOLFTP · SCANNED SEP 25
Deploy a site to its SFTP/FTP host from a coding agent. Changed files only, undo, live checks.
Available components
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 Security100
- 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
- No production dependencies, so there is no dependency health to assess. View diagnostics → Pass
Provenance & Transparency45
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Provenance check failed: no build-provenance attestation is published. See how to fix → View diagnostics → Fail
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 14 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability65
- AI-judged instruction clarity (good).Pass
- 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. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management47
- Stability observed for 14 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage93
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 79% of tool parameters carry a description.Partial
Tool Safety75
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- 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. See how to fix → Fail
- An AI judge read all 18 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
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.
npm · coolftp
claude mcp add anivdel-coolftp -- npx -y coolftp
{
"mcpServers": {
"anivdel-coolftp": {
"command": "npx",
"args": [
"-y",
"coolftp"
]
}
}
} {
"servers": {
"anivdel-coolftp": {
"command": "npx",
"args": [
"-y",
"coolftp"
]
}
}
} codex mcp add anivdel-coolftp -- npx -y coolftp
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"anivdel-coolftp": {
"type": "local",
"command": [
"npx",
"-y",
"coolftp"
],
"enabled": true
}
}
} openclaw mcp add anivdel-coolftp --command npx --arg -y --arg coolftp
mcp_servers:
anivdel-coolftp:
command: "npx"
args: ["-y", "coolftp"] {
"McpServers": {
"anivdel-coolftp": {
"Transport": "stdio",
"Command": "npx",
"Arguments": [
"-y",
"coolftp"
]
}
}
} assistant mcp add anivdel-coolftp -t stdio -c npx -a -y coolftp
{
"mcpServers": {
"anivdel-coolftp": {
"command": "npx",
"args": [
"-y",
"coolftp"
]
}
}
} 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.
- 25 Sept 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 24 Sept 26 +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.
- 22 Sept 26 +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.
- 20 Sept 26 +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.
- 18 Sept 26 +3
- Stability: unverified → 0.23 ▲ functional
- 12 Sept 26 +15
- Malware scan: unverified → pass ▲ security
- 11 Sept 26 52
First indexed and scored.
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 25 Sept 2026 · Analysed npm/coolftp@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 0 packages
| Packages resolved | 0 |
|---|---|
| Tree resolution | Complete |
Background: SBOMs and build attestations, explained →
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 →
coolftp_delete ~138
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.
| Name | Type | Req | Description |
|---|---|---|---|
| cwd | string | – | Project directory. Defaults to the COOLFTP_PROJECT setting, else the MCP server working directory. |
| path | string | yes | – |
| site | string | – | Site name. Defaults to the site in the nearest .coolftp.json, or the only saved site. |
No output schema declared.
No examples provided.
coolftp_deploy ~248
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.
| Name | Type | Req | Description |
|---|---|---|---|
| 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 | – | – |
No output schema declared.
No examples provided.
coolftp_diff ~104
Preview a deploy: which files would be added, changed or are stale on the server. Uploads nothing. Long lists are summarised by folder.
| Name | Type | Req | Description |
|---|---|---|---|
| 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. |
No output schema declared.
No examples provided.
coolftp_download ~135
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.
| Name | Type | Req | Description |
|---|---|---|---|
| cwd | string | – | Project directory. Defaults to the COOLFTP_PROJECT setting, else the MCP server working directory. |
| local | string | yes | Local destination; defaults to the current directory |
| remote | string | yes | – |
| site | string | – | Site name. Defaults to the site in the nearest .coolftp.json, or the only saved site. |
No output schema declared.
No examples provided.
coolftp_history ~75
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.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | – |
| site | string | – | Site name. Defaults to the site in the nearest .coolftp.json, or the only saved site. |
No output schema declared.
No examples provided.
coolftp_init ~204
Link a project directory to a site by writing .coolftp.json. Do this once so later deploys need no site argument.
| Name | Type | Req | Description |
|---|---|---|---|
| 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 | yes | 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. |
No output schema declared.
No examples provided.
coolftp_ls ~123
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.
| Name | Type | Req | Description |
|---|---|---|---|
| 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. |
No output schema declared.
No examples provided.
coolftp_mkdir ~118
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.
| Name | Type | Req | Description |
|---|---|---|---|
| cwd | string | – | Project directory. Defaults to the COOLFTP_PROJECT setting, else the MCP server working directory. |
| path | string | yes | – |
| site | string | – | Site name. Defaults to the site in the nearest .coolftp.json, or the only saved site. |
No output schema declared.
No examples provided.
coolftp_read ~123
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.
| Name | Type | Req | Description |
|---|---|---|---|
| cwd | string | – | Project directory. Defaults to the COOLFTP_PROJECT setting, else the MCP server working directory. |
| path | string | yes | – |
| site | string | – | Site name. Defaults to the site in the nearest .coolftp.json, or the only saved site. |
No output schema declared.
No examples provided.
coolftp_rename ~124
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.
| Name | Type | Req | Description |
|---|---|---|---|
| cwd | string | – | Project directory. Defaults to the COOLFTP_PROJECT setting, else the MCP server working directory. |
| from | string | yes | – |
| site | string | – | Site name. Defaults to the site in the nearest .coolftp.json, or the only saved site. |
| to | string | yes | – |
No output schema declared.
No examples provided.
coolftp_rollback ~167
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.
| Name | Type | Req | Description |
|---|---|---|---|
| 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 |
No output schema declared.
No examples provided.
coolftp_sites ~31
List the servers saved in coolFTP (name, host, protocol, remote root). Secrets are never returned.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
coolftp_stat ~128
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.
| Name | Type | Req | Description |
|---|---|---|---|
| cwd | string | – | Project directory. Defaults to the COOLFTP_PROJECT setting, else the MCP server working directory. |
| path | string | yes | – |
| site | string | – | Site name. Defaults to the site in the nearest .coolftp.json, or the only saved site. |
No output schema declared.
No examples provided.
coolftp_status ~64
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.
| Name | Type | Req | Description |
|---|---|---|---|
| cwd | string | – | Project directory. Defaults to the COOLFTP_PROJECT setting, else the MCP server working directory. |
No output schema declared.
No examples provided.
coolftp_undo ~174
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.
| Name | Type | Req | Description |
|---|---|---|---|
| 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) |
No output schema declared.
No examples provided.
coolftp_upload ~174
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.
| Name | Type | Req | Description |
|---|---|---|---|
| cwd | string | – | Project directory. Defaults to the COOLFTP_PROJECT setting, else the MCP server working directory. |
| local | string | yes | 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. |
No output schema declared.
No examples provided.
coolftp_verify ~122
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.
| Name | Type | Req | Description |
|---|---|---|---|
| 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. |
No output schema declared.
No examples provided.
coolftp_write ~130
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.
| Name | Type | Req | Description |
|---|---|---|---|
| content | string | yes | – |
| cwd | string | – | Project directory. Defaults to the COOLFTP_PROJECT setting, else the MCP server working directory. |
| path | string | yes | – |
| site | string | – | Site name. Defaults to the site in the nearest .coolftp.json, or the only saved site. |
No output schema declared.
No examples provided.
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.