{"id":"viyh-chef-server","name":"chef-server","homepage":"https://hub.docker.com/r/viyh/chef-server","repo_url":"https://hub.docker.com/r/viyh/chef-server","category":"infrastructure","subcategories":[],"tags":["configuration-management","chef","infrastructure-automation","self-hosted","orchestration","devops","cm"],"what_it_does":"chef-server is the Chef Server component of the Chef Infra ecosystem, used to host and serve cookbooks, roles/environments, data bags, nodes, and API access for Chef clients and related tooling.","use_cases":["Centralized management and distribution of Chef infrastructure artifacts (cookbooks, roles, environments, data bags)","Running Chef Infra client workflows against a controlled server (nodes register, runlists/roles resolved)","Team-based infrastructure configuration management with versioned artifacts","Automation platforms that need to provision and maintain server configuration using Chef"],"not_for":["Use as a generic general-purpose database or artifact store unrelated to Chef","Workloads that require lightweight serverless/API-only usage without infrastructure management","Environments where configuration management must be performed with tools other than Chef (unless interoperating with existing Chef assets)"],"best_when":"You have an existing Chef Infra deployment or want to adopt Chef for infrastructure/configuration management with a dedicated central server.","avoid_when":"You need a modern SaaS-style API product with published REST/SDK contracts, OAuth scopes, and explicit rate-limit guidance; Chef Server is primarily an infrastructure product with its own operational concerns.","alternatives":["Chef Workstation + hosted Chef (if moving away from self-managed server)","Ansible Automation Platform / AWX (for similar configuration management use cases)","Puppet Enterprise","SaltStack (Salt)","Terraform Cloud/Enterprise + provisioners (for provisioning-centric workflows)"],"af_score":26.8,"security_score":45.5,"reliability_score":35.0,"package_type":"mcp_server","discovery_source":["docker_mcp"],"priority":"low","status":"evaluated","version_evaluated":null,"last_evaluated":"2026-04-04T21:32:28.396138+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":["Chef authentication mechanisms (e.g., validator/client keys and user/admin credentials depending on deployment)"],"oauth":false,"scopes":false,"notes":"This evaluation is based on package name/ecosystem knowledge; the provided prompt does not include concrete README/API documentation details for auth flows, scope granularity, or exact header/cert formats."},"pricing":{"model":null,"free_tier_exists":false,"free_tier_limits":null,"paid_tiers":[],"requires_credit_card":false,"estimated_workload_costs":null,"notes":"Pricing not determinable from the provided information. Chef Server is typically self-managed software (costs are infrastructure/ops or enterprise licensing depending on edition)."},"requirements":{"requires_signup":false,"requires_credit_card":false,"domain_verification":false,"data_residency":[],"compliance":[],"min_contract":null},"agent_readiness":{"af_score":26.8,"security_score":45.5,"reliability_score":35.0,"mcp_server_quality":0.0,"documentation_accuracy":30.0,"error_message_quality":0.0,"error_message_notes":null,"auth_complexity":35.0,"rate_limit_clarity":10.0,"tls_enforcement":60.0,"auth_strength":60.0,"scope_granularity":20.0,"dependency_hygiene":30.0,"secret_handling":50.0,"security_notes":"Assumes typical deployment can be configured for HTTPS and uses key-based authentication; however, the provided prompt contains no concrete security configuration details (TLS enforcement behavior, password/key storage, RBAC/scope model, dependency/Vuln posture), so scores reflect uncertainty rather than verified guarantees.","uptime_documented":20.0,"version_stability":55.0,"breaking_changes_history":40.0,"error_recovery":25.0,"idempotency_support":"false","idempotency_notes":null,"pagination_style":"unknown","retry_guidance_documented":false,"known_agent_gotchas":["Chef Server usage is primarily operational/infrastructure oriented; AI agents may need substantial domain knowledge (Chef concepts like cookbooks/roles/environments/runlists) rather than a straightforward CRUD API contract.","Without explicit API documentation/OpenAPI spec in the provided material, agents may struggle to reliably map desired actions to endpoints and request/response schemas.","Authentication and authorization in Chef commonly rely on keys/clients/roles; without clear docs, agents may misuse credentials or attempt unsupported flows."]}}