{"id":"goodservers-docker-doctor","name":"docker-doctor","homepage":"https://hub.docker.com/r/goodservers/docker-doctor","repo_url":"https://hub.docker.com/r/goodservers/docker-doctor","category":"infrastructure","subcategories":[],"tags":["docker","diagnostics","troubleshooting","cli","container-tools"],"what_it_does":"docker-doctor is a containerized CLI-style utility intended to inspect a Docker environment and provide diagnostic output to help identify common Docker/daemon/container issues and misconfiguration.","use_cases":["Debugging Docker daemon/host configuration issues","Diagnosing common container/runtime problems","Validating that a Docker setup is healthy before running workloads"],"not_for":["Production-grade automated remediation without human review","Handling sensitive data extraction/forensics","Replacing Docker’s official troubleshooting tooling for complex incidents"],"best_when":"You need quick, local diagnostics of a Docker environment (CI runners, developer laptops, or staging hosts).","avoid_when":"You cannot safely run host-level inspection commands or prefer tools with strict audit/logging guarantees for regulated environments.","alternatives":["docker system info","docker info","docker events/logs (via daemon/client)","container runtimes diagnostics from vendors","Dive/Trivy for image-focused checks (if your goal is image security rather than Docker runtime health)"],"af_score":33.0,"security_score":55.8,"reliability_score":27.5,"package_type":"mcp_server","discovery_source":["docker_mcp"],"priority":"low","status":"evaluated","version_evaluated":null,"last_evaluated":"2026-04-04T21:33:16.536429+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":["None (local/interactive use typical for Docker tooling)"],"oauth":false,"scopes":false,"notes":"As a Docker diagnostic tool, it typically relies on local Docker permissions (e.g., access to the Docker socket) rather than a remote auth scheme. No OAuth/scopes documented from the provided data."},"pricing":{"model":null,"free_tier_exists":false,"free_tier_limits":null,"paid_tiers":[],"requires_credit_card":false,"estimated_workload_costs":null,"notes":"No SaaS pricing information provided; presumed open-source/self-hosted tooling."},"requirements":{"requires_signup":false,"requires_credit_card":false,"domain_verification":false,"data_residency":[],"compliance":[],"min_contract":null},"agent_readiness":{"af_score":33.0,"security_score":55.8,"reliability_score":27.5,"mcp_server_quality":0.0,"documentation_accuracy":35.0,"error_message_quality":0.0,"error_message_notes":null,"auth_complexity":90.0,"rate_limit_clarity":0.0,"tls_enforcement":100.0,"auth_strength":60.0,"scope_granularity":20.0,"dependency_hygiene":45.0,"secret_handling":50.0,"security_notes":"Primary risk is operational: tools that query the Docker daemon/host can expose metadata. Ensure the agent/container running docker-doctor has least-privilege access to the Docker socket and does not log sensitive environment variables or daemon connection details. No additional security mechanisms (scopes, auth model, secret handling guarantees) are evidenced from the provided data.","uptime_documented":0.0,"version_stability":40.0,"breaking_changes_history":40.0,"error_recovery":30.0,"idempotency_support":"false","idempotency_notes":null,"pagination_style":"none","retry_guidance_documented":false,"known_agent_gotchas":["If the tool inspects the host/Docker socket, an agent must run with appropriate permissions; otherwise it may fail early and provide unclear permission-related errors.","Outputs are likely human-oriented; an agent should parse carefully if it needs structured results.","Running in different Docker contexts (rootless vs rootful, remote docker host, CI runners) may change behavior and findings."]}}