{"id":"vlakam-socks5-server","name":"socks5-server","homepage":"https://hub.docker.com/r/vlakam/socks5-server","repo_url":"https://hub.docker.com/r/vlakam/socks5-server","category":"infrastructure","subcategories":[],"tags":["networking","proxy","socks5","tcp","relay"],"what_it_does":"socks5-server is a network service that implements the SOCKS5 protocol to relay client traffic through the server (functionally similar to a SOCKS5 proxy).","use_cases":["Route application traffic through a proxy for connectivity control","Proxying non-HTTP protocols over a SOCKS5-capable tunnel","Local/edge networking test environments requiring a SOCKS5 endpoint","Securely funnel egress traffic from a host/process through a controlled proxy"],"not_for":["Internet-facing deployment without careful hardening","Environments requiring HTTP REST/GraphQL semantics","Use as a general-purpose authentication/authorization gateway","Compliance-critical deployments without documented security controls"],"best_when":null,"avoid_when":null,"alternatives":["ssh -D (SOCKS proxy over SSH)","Tor (SOCKS interface)","nginx/stream with TCP proxying (not SOCKS5-specific)","commercial SOCKS5 proxy services","privoxy (HTTP-focused)","mitmproxy/similar tools (typically not SOCKS5 server-first)"],"af_score":18.8,"security_score":25.8,"reliability_score":5.0,"package_type":"mcp_server","discovery_source":["docker_mcp"],"priority":"low","status":"evaluated","version_evaluated":null,"last_evaluated":"2026-04-04T21:32:03.346681+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":["SOCKS5 username/password authentication (common for SOCKS5 implementations; exact method not verifiable from provided data)","IP allowlist / network-based access (possible; not verifiable from provided data)"],"oauth":false,"scopes":false,"notes":"No repository manifest/README content was provided here to verify supported authentication modes, configuration flags, or scope granularity."},"pricing":{"model":null,"free_tier_exists":false,"free_tier_limits":null,"paid_tiers":[],"requires_credit_card":false,"estimated_workload_costs":null,"notes":"Open-source/service pricing not provided in the supplied input; treated as unknown."},"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":25.8,"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":35.0,"scope_granularity":5.0,"dependency_hygiene":40.0,"secret_handling":40.0,"security_notes":"SOCKS5 proxy security depends heavily on server configuration (bind address, auth on/off, ACLs, logging hygiene, and transport security). TLS is not inherent to SOCKS5; if the service exposes SOCKS5 over plain TCP, confidentiality/integrity may be weak unless protected by an external tunnel (e.g., stunnel/SSH/VPN). No concrete implementation/configuration details were provided here to confirm these controls.","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":["This is a network proxy (SOCKS5), not a structured API; an agent cannot 'call endpoints'—it must establish TCP connections and speak the SOCKS5 protocol.","If authentication is enabled, agents must correctly implement the SOCKS5 auth handshake; otherwise connections will fail.","Proxying arbitrary traffic complicates logging, auditing, and safe retries; naive retries can cause duplicated side effects for stateful protocols."]}}