{"id":"mnagy-nfs-server","name":"nfs-server","homepage":"https://hub.docker.com/r/mnagy/nfs-server","repo_url":"https://hub.docker.com/r/mnagy/nfs-server","category":"storage","subcategories":[],"tags":["infrastructure","storage","nfs","self-hosted","file-sharing"],"what_it_does":"nfs-server is a self-hostable NFS (Network File System) server package that exports local filesystem directories over the network using the NFS protocol so clients can mount and read/write files.","use_cases":["Shared network storage for Linux/Unix clients (dev/test clusters, on-prem deployments)","Homogeneous file sharing across multiple machines without object storage semantics","Legacy workloads that require NFS over newer storage APIs","Mounting shared directories for containers/VMs in private networks"],"not_for":["Public internet exposure without a hardened network and access controls","High-performance low-latency workloads requiring modern distributed storage features","Workloads needing fine-grained access control at the application layer (NFS ACLs are coarse compared to many authz systems)","Multi-tenant environments without strong isolation guarantees"],"best_when":null,"avoid_when":null,"alternatives":["SMB/CIFS server (e.g., Samba) for Windows-centric environments","Distributed filesystems (e.g., CephFS, GlusterFS) for multi-node storage","Object storage with gateways (S3 + NFS/SMB gateways) when file semantics are less strict","NFSv4 with Kerberos (when security requirements demand stronger auth)"],"af_score":8.5,"security_score":21.5,"reliability_score":22.5,"package_type":"mcp_server","discovery_source":["docker_mcp"],"priority":"low","status":"evaluated","version_evaluated":null,"last_evaluated":"2026-04-04T19:54:05.098391+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":["Network-level access control (firewall/subnet restriction; typical NFS export restrictions)"],"oauth":false,"scopes":false,"notes":"NFS security typically depends on network exposure, export configuration, and optional mechanisms such as Kerberos (NFSv4). This evaluation cannot confirm which mode the package supports without additional metadata."},"pricing":{"model":null,"free_tier_exists":false,"free_tier_limits":null,"paid_tiers":[],"requires_credit_card":false,"estimated_workload_costs":null,"notes":"Self-hosted infrastructure component; costs are operational (compute/network/storage) rather than a SaaS pricing model."},"requirements":{"requires_signup":false,"requires_credit_card":false,"domain_verification":false,"data_residency":[],"compliance":[],"min_contract":null},"agent_readiness":{"af_score":8.5,"security_score":21.5,"reliability_score":22.5,"mcp_server_quality":0.0,"documentation_accuracy":0.0,"error_message_quality":0.0,"error_message_notes":null,"auth_complexity":25.0,"rate_limit_clarity":0.0,"tls_enforcement":10.0,"auth_strength":20.0,"scope_granularity":10.0,"dependency_hygiene":30.0,"secret_handling":40.0,"security_notes":"NFS commonly relies on network isolation and UID/GID-based permissions; without explicit TLS and strong auth (e.g., Kerberos for NFSv4), confidentiality/integrity and access control can be weak. This evaluation cannot verify the package's exact security features (export controls, Kerberos support, RPC protection, logging) from the provided information.","uptime_documented":0.0,"version_stability":30.0,"breaking_changes_history":30.0,"error_recovery":30.0,"idempotency_support":"false","idempotency_notes":null,"pagination_style":"none","retry_guidance_documented":false,"known_agent_gotchas":["NFS is stateful from a systems perspective (mounts, file locking, permissions, caching); agent-driven automation must account for idempotent infrastructure changes and safe remounting.","Misconfigured exports/permissions can cause either data exposure or service disruption; ensure least-privilege export rules and network restrictions.","NFS versions/protocol settings (v3 vs v4, portmap/rpcbind behavior) can affect client compatibility and firewall requirements."]}}