{"id":"ftpserver-ftpserver","name":"ftpserver","homepage":"https://hub.docker.com/r/ftpserver/ftpserver","repo_url":"https://hub.docker.com/r/ftpserver/ftpserver","category":"infrastructure","subcategories":[],"tags":["ftp","file-transfer","self-hosted","legacy","networking"],"what_it_does":"ftpserver appears to be a software package related to running an FTP server, enabling file transfer via the FTP protocol (typically including connection handling, authentication, and basic filesystem-backed operations).","use_cases":["Self-hosted FTP access to a server’s files","Legacy system integration that requires FTP (not SFTP/HTTPS)","Internal file transfer automation in controlled networks","Migrating or interfacing with older clients that only support FTP"],"not_for":["Sensitive data transfer over untrusted networks (FTP lacks transport security by default)","Modern secure file transfer requirements (prefer SFTP/FTPS)","Internet-facing file transfer without strong network controls and hardening","Use as an agent-accessible API for programmatic workflows (unless wrapped with a proper control plane)"],"best_when":"You need legacy FTP compatibility inside a trusted network and can harden access (firewall/VPN) and configure secure credentials and permissions.","avoid_when":"You need confidentiality/integrity over the public internet or cannot guarantee transport-layer protection and strong access control.","alternatives":["SFTP (SSH File Transfer Protocol)","FTPS (FTP over TLS)","HTTPS-based file upload/download (with signed URLs)","WebDAV over TLS","Object storage (S3-compatible) with presigned URLs"],"af_score":17.5,"security_score":24.5,"reliability_score":5.0,"package_type":"mcp_server","discovery_source":["docker_mcp"],"priority":"low","status":"evaluated","version_evaluated":null,"last_evaluated":"2026-04-04T19:38:57.267292+00:00","interface":{"has_rest_api":false,"has_graphql":false,"has_grpc":false,"has_mcp_server":false,"mcp_server_url":null,"has_sdk":false,"sdk_languages":[],"openapi_spec_url":null,"webhooks":false},"auth":{"methods":["FTP username/password (typical)"],"oauth":false,"scopes":false,"notes":"No package manifest/README content was provided here, so authentication mechanisms and scope granularity can’t be confirmed. Standard FTP setups often use plaintext credentials unless secured via FTPS or an external tunnel."},"pricing":{"model":null,"free_tier_exists":false,"free_tier_limits":null,"paid_tiers":[],"requires_credit_card":false,"estimated_workload_costs":null,"notes":"Assessed as a software package; pricing not applicable based on provided information."},"requirements":{"requires_signup":false,"requires_credit_card":false,"domain_verification":false,"data_residency":[],"compliance":[],"min_contract":null},"agent_readiness":{"af_score":17.5,"security_score":24.5,"reliability_score":5.0,"mcp_server_quality":0.0,"documentation_accuracy":0.0,"error_message_quality":0.0,"error_message_notes":null,"auth_complexity":40.0,"rate_limit_clarity":0.0,"tls_enforcement":10.0,"auth_strength":40.0,"scope_granularity":10.0,"dependency_hygiene":30.0,"secret_handling":30.0,"security_notes":"FTP commonly uses plaintext control and data channels unless configured for TLS (FTPS) or used behind a secure tunnel/VPN. Without verified docs/config, assume security must be handled via network segmentation, strong credentials, least-privilege filesystem permissions, and (ideally) FTPS/SFTP equivalents.","uptime_documented":0.0,"version_stability":0.0,"breaking_changes_history":0.0,"error_recovery":20.0,"idempotency_support":"false","idempotency_notes":null,"pagination_style":"none","retry_guidance_documented":false,"known_agent_gotchas":["FTP is stateful and command/protocol driven; LLM agents may struggle without a higher-level API wrapper.","FTP’s security model is often weak by default (credentials and data can be unencrypted).","File transfer side effects (uploads/downloads) are not inherently idempotent unless the design includes safe overwrite semantics."]}}