{"id":"halverneus-static-file-server","name":"static-file-server","homepage":"https://hub.docker.com/r/halverneus/static-file-server","repo_url":"https://hub.docker.com/r/halverneus/static-file-server","category":"infrastructure","subcategories":[],"tags":["static","http","server","assets","development","self-hosted"],"what_it_does":"A static-file-server that serves files from a local directory over HTTP (optionally with configuration such as port/bind address, directory indexing, caching, and/or SPA fallback—exact features not provided here).","use_cases":["Serving a frontend build (HTML/CSS/JS)","Hosting documentation/static assets for development","Lightweight local file hosting for demos/test environments","Creating a simple HTTP mirror of a directory"],"not_for":["Production-grade multi-tenant hosting without a reverse proxy/web application firewall","Applications requiring authentication/authorization at the application layer","Large-scale high-traffic static hosting without performance tuning/CDN"],"best_when":"You control the environment (dev/staging, single-tenant) and want a simple way to expose a directory over HTTP.","avoid_when":"You need strong access control, auditing, or advanced security headers/policies out of the box, or you cannot run behind HTTPS/reverse proxy.","alternatives":["nginx","Caddy","Apache httpd","S3/Cloud Storage + CDN","express static (Node) / serve-static middleware","GitHub Pages/Netlify/Vercel static hosting"],"af_score":18.8,"security_score":28.5,"reliability_score":32.5,"package_type":"mcp_server","discovery_source":["docker_mcp"],"priority":"high","status":"evaluated","version_evaluated":null,"last_evaluated":"2026-03-30T13:55:35.018582+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":[],"oauth":false,"scopes":false,"notes":"Static file servers commonly expose files without app-layer auth; no auth details were provided in the prompt, so authentication cannot be confirmed."},"pricing":{"model":null,"free_tier_exists":false,"free_tier_limits":null,"paid_tiers":[],"requires_credit_card":false,"estimated_workload_costs":null,"notes":"No pricing information provided; typical static file servers are self-hosted software."},"requirements":{"requires_signup":false,"requires_credit_card":false,"domain_verification":false,"data_residency":[],"compliance":[],"min_contract":null},"agent_readiness":{"af_score":18.8,"security_score":28.5,"reliability_score":32.5,"mcp_server_quality":0.0,"documentation_accuracy":0.0,"error_message_quality":0.0,"error_message_notes":null,"auth_complexity":10.0,"rate_limit_clarity":0.0,"tls_enforcement":20.0,"auth_strength":10.0,"scope_granularity":10.0,"dependency_hygiene":40.0,"secret_handling":70.0,"security_notes":"TLS/auth/scopes/rate limits are not confirmed from provided data. A static file server should typically be run behind HTTPS (reverse proxy) and with safe path handling to prevent traversal. Secret handling is likely minimal because it usually has no credentials, but exact dependency/security posture cannot be assessed without the repo manifest/README.","uptime_documented":0.0,"version_stability":50.0,"breaking_changes_history":40.0,"error_recovery":40.0,"idempotency_support":"false","idempotency_notes":null,"pagination_style":"none","retry_guidance_documented":false,"known_agent_gotchas":["Static file servers often return HTML error pages or generic 404s rather than machine-friendly JSON; an agent may need to treat responses as opaque content.","Directory traversal protections depend on the implementation and configuration; ensure safe path handling.","If SPA fallback or caching is enabled, agents expecting strict 404s may receive index.html or cached content instead."]}}