{"id":"hauschi86-openttd-server","name":"openttd-server","homepage":"https://hub.docker.com/r/hauschi86/openttd-server","repo_url":"https://hub.docker.com/r/hauschi86/openttd-server","category":"infrastructure","subcategories":[],"tags":["games","open-source","game-server","multiplayer","openttd"],"what_it_does":"OpenTTD server software for hosting OpenTTD multiplayer games. Provides a headless game server process configurable via command-line and/or config files (typical for game-server deployments).","use_cases":["Host a multiplayer OpenTTD game for LAN/Internet friends","Run tournament/custom OpenTTD scenarios and game servers","Provide a dedicated server deployment for communities/communicators using OpenTTD gameplay"],"not_for":["Building a cloud-hosted API service for programmatic business workflows","Use cases requiring a web/API interface with structured request/response semantics","Applications needing first-class authentication/authorization for API consumers"],"best_when":"You want to host OpenTTD multiplayer sessions and can manage server lifecycle (ports, firewall/NAT, configs) yourself.","avoid_when":"You need REST/GraphQL/gRPC endpoints, managed auth, or documented API rate limits for client integrations.","alternatives":["Self-host OpenTTD multiplayer server via official/OpenTTD server packages","Community-managed Docker images for OpenTTD dedicated servers (where available)","Use P2P/LAN hosting mode (no dedicated server) if you don’t need centralized management"],"af_score":27.5,"security_score":21.5,"reliability_score":30.0,"package_type":"mcp_server","discovery_source":["docker_mcp"],"priority":"low","status":"evaluated","version_evaluated":null,"last_evaluated":"2026-04-04T19:39:58.133069+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":"No API-style auth described. Multiplayer access is typically controlled by server settings (e.g., allowed clients/passwords) rather than OAuth/API-key scopes."},"pricing":{"model":null,"free_tier_exists":false,"free_tier_limits":null,"paid_tiers":[],"requires_credit_card":false,"estimated_workload_costs":null,"notes":"Self-hosted software; costs are infrastructure-related (hosting/VPS, bandwidth). No pricing model indicated."},"requirements":{"requires_signup":false,"requires_credit_card":false,"domain_verification":false,"data_residency":[],"compliance":[],"min_contract":null},"agent_readiness":{"af_score":27.5,"security_score":21.5,"reliability_score":30.0,"mcp_server_quality":0.0,"documentation_accuracy":20.0,"error_message_quality":0.0,"error_message_notes":null,"auth_complexity":90.0,"rate_limit_clarity":0.0,"tls_enforcement":10.0,"auth_strength":25.0,"scope_granularity":0.0,"dependency_hygiene":35.0,"secret_handling":40.0,"security_notes":"Security properties are not documented in the provided context. As a self-hosted game server, transport security (TLS) is unlikely/unknown; rely on network controls (firewall/VPN) and keep server software updated. Auth appears to be non-API/player-access based rather than fine-grained scoped authorization.","uptime_documented":0.0,"version_stability":45.0,"breaking_changes_history":45.0,"error_recovery":30.0,"idempotency_support":"false","idempotency_notes":"Server operations are typically start/stop/config updates rather than idempotent HTTP actions; no idempotency guarantees are documented for agent-driven requests.","pagination_style":"none","retry_guidance_documented":false,"known_agent_gotchas":["Treat as a system service/CLI-driven game server rather than an API; an agent will likely need to manage process lifecycle and configs.","Networking (NAT/firewall/ports) is often the integration bottleneck, not HTTP request/response semantics.","Auth/account handling is game-level (server settings, player access), not OAuth/API-key flows."]}}