{"id":"yarmak-socks5-server","name":"socks5-server","homepage":"https://hub.docker.com/r/yarmak/socks5-server","repo_url":"https://hub.docker.com/r/yarmak/socks5-server","category":"infrastructure","subcategories":[],"tags":["networking","proxy","socks5","tcp-relay","infrastructure"],"what_it_does":"socks5-server is a SOCKS5 proxy server implementation that accepts client connections and relays traffic to requested destinations using the SOCKS5 protocol.","use_cases":["Run a local or network-facing SOCKS5 proxy for routing client traffic","Provide a simple proxy layer for tools that support SOCKS5","Testing/debugging of proxy/network behavior using the SOCKS5 protocol"],"not_for":["Production use without careful security hardening and access controls","Use as a general-purpose internet gateway for untrusted networks","Use cases requiring strong, standardized API integrations (it is a network proxy, not an application API)"],"best_when":"You control the network environment (firewalling, allowlists) and need a SOCKS5 relay for compatibility/testing.","avoid_when":"You need an API/SDK-first service, or you cannot restrict who can connect to the proxy.","alternatives":["OpenSSH dynamic port forwarding (SOCKS proxy via ssh -D)","danted (Dante SOCKS server)","3proxy (lightweight proxy)","mitmproxy/similar tools for debugging (not strictly SOCKS5-only)"],"af_score":22.2,"security_score":31.2,"reliability_score":26.2,"package_type":"mcp_server","discovery_source":["docker_mcp"],"priority":"low","status":"evaluated","version_evaluated":null,"last_evaluated":"2026-04-04T19:37:44.444961+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 (if supported by configuration)","IP allowlisting / firewalling (deployment-level)"],"oauth":false,"scopes":false,"notes":"This is a network service rather than an API product. Authentication, if any, is typically SOCKS5-level (username/password) and/or enforced via network controls; exact support is not provided in the prompt content."},"pricing":{"model":null,"free_tier_exists":false,"free_tier_limits":null,"paid_tiers":[],"requires_credit_card":false,"estimated_workload_costs":null,"notes":"Not applicable; open-source/network software pattern (pricing unknown from provided info)."},"requirements":{"requires_signup":false,"requires_credit_card":false,"domain_verification":false,"data_residency":[],"compliance":[],"min_contract":null},"agent_readiness":{"af_score":22.2,"security_score":31.2,"reliability_score":26.2,"mcp_server_quality":0.0,"documentation_accuracy":20.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":40.0,"scope_granularity":20.0,"dependency_hygiene":35.0,"secret_handling":50.0,"security_notes":"As a proxy relay, it can be abused for unauthorized egress if left open. Security largely depends on deployment: network-level access restriction, optional SOCKS5 authentication, logging/monitoring, and TLS/integrity of any client connections (TLS is not implied by SOCKS5 itself—often SOCKS5 is TCP plaintext unless wrapped/proxied elsewhere). Dependency hygiene and exact auth mechanisms are not verifiable from the provided prompt content.","uptime_documented":0.0,"version_stability":40.0,"breaking_changes_history":30.0,"error_recovery":35.0,"idempotency_support":"false","idempotency_notes":null,"pagination_style":"none","retry_guidance_documented":false,"known_agent_gotchas":["This is not an HTTP/SDK-based interface; agents must work at the network/protocol level (establish TCP connection, speak SOCKS5).","Security and access control (firewalls/allowlists, auth configuration) are critical and are typically not guaranteed by the agent framework.","If SOCKS5 auth is used, agents must manage credentials securely and handle protocol-level failures/rejections."]}}