nfs-server

nfs-server provides an NFS server to export filesystem paths over the network using the NFS protocol, so remote clients can mount and access shared directories.

Evaluated Apr 04, 2026 (25d ago)
Homepage ↗ Repo ↗ Storage storage nfs filesharing self-hosted linux
⚙ Agent Friendliness
10
/ 100
Can an agent use this?
🔒 Security
27
/ 100
Is it safe for agents?
⚡ Reliability
20
/ 100
Does it work consistently?

Score Breakdown

⚙ Agent Friendliness

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

🔒 Security

TLS Enforcement
10
Auth Strength
25
Scope Granularity
15
Dep. Hygiene
40
Secret Handling
50

NFS is commonly protected via network isolation and export restrictions rather than per-request TLS/auth. Unless explicitly configured for NFSv4 with Kerberos or equivalent, traffic confidentiality and strong authentication may be limited. Proper export configuration, least-privilege permissions, and firewalling are critical.

⚡ Reliability

Uptime/SLA
0
Version Stability
30
Breaking Changes
30
Error Recovery
20
AF Security Reliability

Best When

You control the network path (VPC/VLAN), can manage NFS exports safely, and accept NFS’s security/performance characteristics in exchange for simple POSIX-like shared files.

Avoid When

You cannot ensure network isolation and appropriate export/auth configuration, or you require modern encrypted/authenticated-by-default access controls per request.

Use Cases

  • On-premises shared storage for Linux fleets
  • Legacy application compatibility requiring NFS
  • Development/test environments needing networked filesystems
  • Centralized home directories or shared project directories
  • Cluster or VM environments that rely on NFS mounts

Not For

  • Untrusted multi-tenant environments without strong network isolation
  • Exposing raw file shares to the public internet
  • Use cases requiring strong application-level authz/audit for every file operation
  • Highly performance-sensitive workloads that are better served by object storage or specialized filesystems

Interface

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

Authentication

Methods: Network-based access control typical of NFS exports (client IP/CIDR) Host authentication via traditional NFS mechanisms (varies by configuration)
OAuth: No Scopes: No

From the provided package name/description alone, specific auth mechanisms (e.g., Kerberos for NFSv4) are not verifiable. NFS security typically depends heavily on server export settings and client mount options.

Pricing

Free tier: No
Requires CC: No

Assumed self-hosted/open-source package; no SaaS pricing information provided.

Agent Metadata

Pagination
none
Idempotent
False
Retry Guidance
Not documented

Known Gotchas

  • As an NFS server, operations are typically configuration- and network-dependent rather than request/response API calls, so agents may need careful handling of mounts, firewall rules, and export permissions.
  • NFS behavior can vary significantly by NFS version (e.g., v3 vs v4) and mount/export options; automated setups should explicitly pin versions and options.
  • Security and reliability depend on environment configuration (firewall, SELinux/AppArmor, kernel parameters), which may not be fully captured in repository metadata.

Alternatives

Full Evaluation Report

Comprehensive deep-dive: security analysis, reliability audit, agent experience review, cost modeling, competitive positioning, and improvement roadmap for nfs-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