{"id":"yaleh-kcp-shadowsocks-server","name":"kcp-shadowsocks-server","homepage":"https://hub.docker.com/r/yaleh/kcp-shadowsocks-server","repo_url":"https://hub.docker.com/r/yaleh/kcp-shadowsocks-server","category":"infrastructure","subcategories":[],"tags":["networking","proxy","shadowsocks","kcp","udp","self-hosted","privacy","server"],"what_it_does":"kcp-shadowsocks-server is a server implementation that combines KCP (a UDP-based transport designed to provide reliable, low-latency delivery) with the Shadowsocks proxy protocol, enabling proxying over KCP streams. Typically used to improve throughput/latency versus plain TCP in constrained networks while maintaining the Shadowsocks encryption/proxying model.","use_cases":["Running a Shadowsocks proxy server over KCP to improve performance on high-latency or lossy networks","Building a self-hosted anonymizing/egress proxy for clients that support KCP+Shadowsocks","Circumventing network throttling/packet loss compared to conventional TCP-based approaches"],"not_for":["API/service integration in typical agent workflows (it is a network server, not a request/response API)","Environments requiring formal compliance guarantees without additional auditing/config hardening","Use cases needing fine-grained, documented admin/auth APIs (unless the project documentation provides them, which is not provided here)"],"best_when":null,"avoid_when":null,"alternatives":["Shadowsocks-libev/Go server over TCP","V2Ray/Xray with KCP transport","Trojan-go with suitable transports","WireGuard-based VPN solutions where appropriate","Other KCP-enabled proxy solutions (e.g., sing-box/v2ray plugins that support KCP)"],"af_score":15.0,"security_score":12.5,"reliability_score":0.0,"package_type":"mcp_server","discovery_source":["docker_mcp"],"priority":"low","status":"evaluated","version_evaluated":null,"last_evaluated":"2026-04-04T19:33:46.970313+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":["Shadowsocks password/secret-based configuration (commonly via a server-side config, e.g., method+password)"],"oauth":false,"scopes":false,"notes":"No explicit API-style auth documented in the provided prompt. Assumes standard Shadowsocks server shared-secret authentication configured on the server."},"pricing":{"model":null,"free_tier_exists":false,"free_tier_limits":null,"paid_tiers":[],"requires_credit_card":false,"estimated_workload_costs":null,"notes":"Self-hosted open-source/service pricing not determinable from provided information."},"requirements":{"requires_signup":false,"requires_credit_card":false,"domain_verification":false,"data_residency":[],"compliance":[],"min_contract":null},"agent_readiness":{"af_score":15.0,"security_score":12.5,"reliability_score":0.0,"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":0.0,"auth_strength":50.0,"scope_granularity":0.0,"dependency_hygiene":0.0,"secret_handling":0.0,"security_notes":"Security depends on Shadowsocks cryptographic configuration and server hardening (e.g., using strong ciphers/keys, secure config management, limiting exposure at the network layer). Because no repository code/config/log-handling details are provided here, concrete guarantees (TLS, scope controls, secret storage, dependency posture) cannot be verified.","uptime_documented":0.0,"version_stability":0.0,"breaking_changes_history":0.0,"error_recovery":0.0,"idempotency_support":"false","idempotency_notes":null,"pagination_style":"none","retry_guidance_documented":false,"known_agent_gotchas":["This is a network server (UDP-based) rather than an API; agents expecting HTTP/REST tooling will not be able to interact with it directly.","Correct operation depends heavily on network/firewall/UDP reachability and configuration parameters (ports, congestion control, keys).","Operational errors are typically surfaced in logs rather than structured API responses."]}}