{"id":"erichough-nfs-server","name":"nfs-server","homepage":"https://hub.docker.com/r/erichough/nfs-server","repo_url":"https://hub.docker.com/r/erichough/nfs-server","category":"storage","subcategories":[],"tags":["storage","infrastructure","filesystems","nfs","self-hosted"],"what_it_does":"nfs-server is a software package intended to provide an NFS (Network File System) server for exporting files/directories to clients over the network.","use_cases":["Sharing filesystems between Linux hosts over a LAN","Centralized storage for development/test environments","Legacy or compatibility use cases requiring NFS rather than newer protocols"],"not_for":["Internet-facing or untrusted networks without strong network isolation and hardening","Multi-tenant SaaS storage where fine-grained authZ, audit, and tenant isolation are required","High-performance workloads that require low latency (NFS performance depends heavily on configuration)"],"best_when":"You have a trusted network (or VPN) and can harden/export carefully to specific clients or subnets.","avoid_when":"You cannot control network access, cannot secure NFS ports, or require strong identity-based access controls beyond typical NFS mechanisms.","alternatives":["Samba/CIFS for Windows interoperability","NFSv4 with Kerberos (when appropriate) for stronger auth","SMB over VPN","Object/block storage solutions (S3/NAS appliance) with application-level access control"],"af_score":14.8,"security_score":32.0,"reliability_score":10.0,"package_type":"mcp_server","discovery_source":["docker_mcp"],"priority":"high","status":"evaluated","version_evaluated":null,"last_evaluated":"2026-03-30T13:50:26.793498+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 for exports (e.g., client IP/subnet restrictions)","Typical NFS authentication/authorization via export settings and UID/GID mapping (exact mechanism depends on configuration)"],"oauth":false,"scopes":false,"notes":"The package is an NFS server; authentication/authorization is typically handled via NFS export configuration (client restrictions) and filesystem permissions/UID-GID mapping rather than an API auth scheme."},"pricing":{"model":null,"free_tier_exists":false,"free_tier_limits":null,"paid_tiers":[],"requires_credit_card":false,"estimated_workload_costs":null,"notes":"Open-source/self-hosted software; pricing not applicable from the provided information."},"requirements":{"requires_signup":false,"requires_credit_card":false,"domain_verification":false,"data_residency":[],"compliance":[],"min_contract":null},"agent_readiness":{"af_score":14.8,"security_score":32.0,"reliability_score":10.0,"mcp_server_quality":0.0,"documentation_accuracy":0.0,"error_message_quality":0.0,"error_message_notes":null,"auth_complexity":30.0,"rate_limit_clarity":0.0,"tls_enforcement":5.0,"auth_strength":20.0,"scope_granularity":20.0,"dependency_hygiene":40.0,"secret_handling":80.0,"security_notes":"Likely no built-in TLS for NFS data by default (NFS traditionally relies on network isolation; some environments use NFSv4 with Kerberos for stronger auth). Security largely depends on export configuration (client allowlists), UID/GID mapping/permissions, firewall rules restricting NFS-related ports, and whether stronger auth (e.g., Kerberos for NFSv4) is used. Dependency hygiene and exact configuration hardening cannot be verified from the provided information.","uptime_documented":0.0,"version_stability":0.0,"breaking_changes_history":0.0,"error_recovery":40.0,"idempotency_support":"false","idempotency_notes":null,"pagination_style":"none","retry_guidance_documented":false,"known_agent_gotchas":["NFS is typically configured via server-side config files/exports and system services; there may be no programmatic interface for agents.","Safety concerns: misconfigured exports can expose data broadly; ensure least-privilege client access and correct permissions.","NFS client behavior depends on network, protocol version (e.g., NFSv3 vs NFSv4), and server export options; retries/idempotency are not applicable at an API level."]}}