{"id":"ich777-stun-turn-server","name":"stun-turn-server","homepage":"https://hub.docker.com/r/ich777/stun-turn-server","repo_url":"https://hub.docker.com/r/ich777/stun-turn-server","category":"infrastructure","subcategories":[],"tags":["stun","turn","webrtc","nat-traversal","networking","relay","udp","real-time"],"what_it_does":"Stun/turn server component intended to facilitate NAT traversal for real-time networking (e.g., WebRTC) using STUN and TURN protocols.","use_cases":["NAT traversal for VoIP/video conferencing","WebRTC connectivity for peers behind NAT/firewalls","Relay media when direct UDP connectivity fails"],"not_for":["General HTTP API access","Credentialed business logic or data storage","Production signaling/identity services"],"best_when":"You need STUN/TURN functionality and can run/operate the server yourself in a controlled network environment.","avoid_when":"You cannot operate and harden network-facing UDP/TCP services or do not have control over firewall/ports and certificates/configuration.","alternatives":["Coturn (common TURN/STUN server)","Managed TURN/STUN services from WebRTC vendors","LiveKit/RTC provider TURN relays (hosted options)"],"af_score":18.2,"security_score":37.8,"reliability_score":21.2,"package_type":"mcp_server","discovery_source":["docker_mcp"],"priority":"low","status":"evaluated","version_evaluated":null,"last_evaluated":"2026-04-04T19:40:28.740153+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":["Static/shared credentials for TURN (commonly long-term credentials)"],"oauth":false,"scopes":false,"notes":"Auth mechanisms are not fully verifiable from the provided information; TURN deployments typically require credentials/configuration (e.g., users/passwords), but exact method(s) cannot be confirmed here."},"pricing":{"model":null,"free_tier_exists":false,"free_tier_limits":null,"paid_tiers":[],"requires_credit_card":false,"estimated_workload_costs":null,"notes":"Self-hosted; cost is primarily infrastructure/egress and operational effort (exacts not provided)."},"requirements":{"requires_signup":false,"requires_credit_card":false,"domain_verification":false,"data_residency":[],"compliance":[],"min_contract":null},"agent_readiness":{"af_score":18.2,"security_score":37.8,"reliability_score":21.2,"mcp_server_quality":0.0,"documentation_accuracy":20.0,"error_message_quality":0.0,"error_message_notes":null,"auth_complexity":45.0,"rate_limit_clarity":0.0,"tls_enforcement":40.0,"auth_strength":55.0,"scope_granularity":0.0,"dependency_hygiene":40.0,"secret_handling":50.0,"security_notes":"As a network-facing STUN/TURN component, it should be hardened with least-privilege network exposure and strong TURN credentials. Exact TLS/auth configuration, secret handling, and dependency hygiene cannot be confirmed from the provided information.","uptime_documented":0.0,"version_stability":30.0,"breaking_changes_history":30.0,"error_recovery":25.0,"idempotency_support":"false","idempotency_notes":null,"pagination_style":"none","retry_guidance_documented":false,"known_agent_gotchas":["No explicit programmatic interface was provided (this appears to be a network server rather than an API).","Operational dependencies (ports/UDP reachability, firewall rules, relay configuration) can cause failures that look like application errors.","TURN relay deployments can be sensitive to misconfiguration, leading to high bandwidth costs or connection failures."]}}