simple-ftp-server

simple-ftp-server is an FTP server implementation intended to provide basic FTP functionality (server-side) for file transfer over the FTP protocol.

Evaluated Apr 04, 2026 (27d ago)
Homepage ↗ Repo ↗ Infrastructure ftp file-transfer server self-hosted devops networking
⚙ Agent Friendliness
33
/ 100
Can an agent use this?
🔒 Security
26
/ 100
Is it safe for agents?
⚡ Reliability
31
/ 100
Does it work consistently?

Score Breakdown

⚙ Agent Friendliness

MCP Quality
0
Documentation
30
Error Messages
0
Auth Simplicity
70
Rate Limits
5

🔒 Security

TLS Enforcement
5
Auth Strength
40
Scope Granularity
10
Dep. Hygiene
30
Secret Handling
40

FTP commonly transmits credentials and data in plaintext unless TLS is configured (FTPS). Security depends heavily on whether TLS/FTPS is supported/enforced, how authentication is configured, and how the server is deployed (firewalling, access controls, logging).

⚡ Reliability

Uptime/SLA
0
Version Stability
50
Breaking Changes
50
Error Recovery
25
AF Security Reliability

Best When

You need a lightweight FTP server for development or controlled environments and can manage security at the network and configuration layers.

Avoid When

You need confidentiality/integrity guarantees, modern auth controls, or you want a well-documented agent-friendly API surface.

Use Cases

  • Local or development/test environments needing an FTP endpoint
  • Legacy system integration where FTP is required
  • Simple file drop/download workflows for non-sensitive data
  • Educational/demo purposes around FTP server behavior

Not For

  • Production use without additional hardening (network, auth, TLS, auditing)
  • Transferring sensitive data (FTP is not secure by default)
  • Workloads requiring modern secure file transfer features (e.g., SFTP/FTPS with strong authentication)
  • Agent-to-agent automated workflows that rely on REST/SDK interfaces

Interface

REST API
No
GraphQL
No
gRPC
No
MCP Server
No
SDK
No
Webhooks
No

Authentication

Methods: FTP login (username/password)
OAuth: No Scopes: No

Authentication method is FTP-session based; no indication of OAuth/scopes. (Exact strength and configuration options depend on the project’s configuration.)

Pricing

Free tier: No
Requires CC: No

Open-source/server-style package; no hosted pricing model indicated.

Agent Metadata

Pagination
none
Idempotent
False
Retry Guidance
Not documented

Known Gotchas

  • FTP is stateful; agent automation must manage sessions/connection lifecycle.
  • FTP lacks modern security features by default; transfers may be unencrypted and susceptible to interception unless FTPS/TLS is explicitly used (if supported).
  • FTP commands and server responses are less standardized than REST/JSON APIs; robust parsing may be needed.
  • Transfer operations are often not naturally idempotent (retries can duplicate/overwrite depending on server config).

Alternatives

Full Evaluation Report

Comprehensive deep-dive: security analysis, reliability audit, agent experience review, cost modeling, competitive positioning, and improvement roadmap for simple-ftp-server.

AI-powered analysis · PDF + markdown · Delivered within 30 minutes

$99

Package Brief

Quick verdict, integration guide, cost projections, gotchas with workarounds, and alternatives comparison.

Delivered within 10 minutes

$3

Score Monitoring

Get alerted when this package's AF, security, or reliability scores change significantly. Stay ahead of regressions.

Continuous monitoring

$3/mo

Scores are editorial opinions as of 2026-04-04.

8642
Packages Evaluated
17761
Need Evaluation
586
Need Re-evaluation
Community Powered