{"id":"roemer-ut99-server","name":"ut99-server","homepage":"https://hub.docker.com/r/roemer/ut99-server","repo_url":"https://hub.docker.com/r/roemer/ut99-server","category":"infrastructure","subcategories":[],"tags":["game-server","self-hosted","unreal-tournament-99","udp","server-ops"],"what_it_does":"ut99-server is a package intended to run an Unreal Tournament 99 (UT99) dedicated server (game server software). It appears to be a self-hosted server component rather than a hosted API service.","use_cases":["Self-hosting a UT99 dedicated game server for LAN or public matches","Running automated/managed UT99 instances (e.g., containerized deployments)","Testing and development of UT99 server configuration/mods"],"not_for":["Providing a public REST/GraphQL/gRPC API for programmatic access","Handling user authentication/authorization for third-party apps","Use as a security/compliance managed cloud service"],"best_when":"You want to run a UT99 game server you control (typical server ops on your infrastructure).","avoid_when":"You need a documented web API/SDK, managed hosting, or built-in enterprise authentication and rate limiting.","alternatives":["Generic UT99 dedicated server distributions (official/community) run directly on your host","Community server management tools for UT99 (if you already use one, keep it consistent)","Alternative game server hosting/container images for other platforms depending on your requirements"],"af_score":18.0,"security_score":24.5,"reliability_score":25.0,"package_type":"mcp_server","discovery_source":["docker_mcp"],"priority":"low","status":"evaluated","version_evaluated":null,"last_evaluated":"2026-04-04T19:38:15.960974+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":"As a game server, authentication is typically handled via UT99/server-side mechanisms or network controls; there is no evidence of an application-level auth API contract."},"pricing":{"model":null,"free_tier_exists":false,"free_tier_limits":null,"paid_tiers":[],"requires_credit_card":false,"estimated_workload_costs":null,"notes":"No pricing/hosted-service information provided; expected self-hosting on your infrastructure."},"requirements":{"requires_signup":false,"requires_credit_card":false,"domain_verification":false,"data_residency":[],"compliance":[],"min_contract":null},"agent_readiness":{"af_score":18.0,"security_score":24.5,"reliability_score":25.0,"mcp_server_quality":0.0,"documentation_accuracy":30.0,"error_message_quality":0.0,"error_message_notes":null,"auth_complexity":50.0,"rate_limit_clarity":0.0,"tls_enforcement":10.0,"auth_strength":20.0,"scope_granularity":0.0,"dependency_hygiene":50.0,"secret_handling":50.0,"security_notes":"No observable documentation of transport security, auth, or secrets handling. For a game server, network exposure (open ports), patching, and configuration hardening are typically the main security responsibilities of the operator.","uptime_documented":0.0,"version_stability":40.0,"breaking_changes_history":40.0,"error_recovery":20.0,"idempotency_support":"false","idempotency_notes":null,"pagination_style":"none","retry_guidance_documented":false,"known_agent_gotchas":["No documented API contract (no REST/GraphQL/gRPC/MCP), so an agent cannot reliably integrate without reverse-engineering server configuration/CLI/logs.","Game servers often use UDP and long-running processes; automation may need careful handling of process lifecycle and ports."]}}