{"id":"serversideup-docker-ssh","name":"docker-ssh","homepage":"https://hub.docker.com/r/serversideup/docker-ssh","repo_url":"https://hub.docker.com/r/serversideup/docker-ssh","category":"infrastructure","subcategories":[],"tags":["docker","ssh","remote-access","devops","containers"],"what_it_does":"docker-ssh provides a containerized SSH service that allows SSH access into a Docker environment (typically for debugging/administration), likely by wrapping/adding SSH server configuration in a Docker image/container.","use_cases":["Remote shell access into a containerized environment for debugging","Lightweight admin access for self-hosted deployments","Ephemeral environments where you want SSH instead of interactive exec","Legacy workflows/tools that assume SSH connectivity"],"not_for":["Production-grade remote access without strong hardening and audit controls","Multi-tenant environments where SSH access needs strict isolation","Replacing proper configuration management/CI access patterns","Any use case requiring fine-grained API-level controls or RBAC"],"best_when":"You control the host/network, can restrict inbound SSH, and only need temporary/admin access to containers with appropriate key-based auth and hardening.","avoid_when":"You cannot restrict network access to SSH, cannot manage secrets/keys securely, or require strong operational guarantees (auditability, access control) beyond basic SSH.","alternatives":["docker exec / docker compose exec (when interactive access is sufficient)","Kubernetes exec (in k8s)","A bastion + SSH into hosts and then use docker exec","Managed remote access solutions (e.g., SSM Session Manager)","Web-based terminals (e.g., sshd + reverse proxy with MFA, or dedicated terminal gateways)"],"af_score":20.0,"security_score":26.0,"reliability_score":25.0,"package_type":"mcp_server","discovery_source":["docker_mcp"],"priority":"low","status":"evaluated","version_evaluated":null,"last_evaluated":"2026-04-04T21:36:25.636199+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":["SSH key authentication (presumed typical for sshd images)","SSH password authentication (possible but typically discouraged)"],"oauth":false,"scopes":false,"notes":"No API auth model (no OAuth/scopes). Access is governed by SSH authentication and container/network permissions."},"pricing":{"model":null,"free_tier_exists":false,"free_tier_limits":null,"paid_tiers":[],"requires_credit_card":false,"estimated_workload_costs":null,"notes":"As a Docker image/tool, cost is primarily infrastructure-related rather than per-request pricing."},"requirements":{"requires_signup":false,"requires_credit_card":false,"domain_verification":false,"data_residency":[],"compliance":[],"min_contract":null},"agent_readiness":{"af_score":20.0,"security_score":26.0,"reliability_score":25.0,"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":10.0,"auth_strength":45.0,"scope_granularity":0.0,"dependency_hygiene":45.0,"secret_handling":30.0,"security_notes":"Security depends heavily on image/sshd configuration and deployment practices (key-only auth, disabling root/password login, limiting users, firewalling, and host/container filesystem hardening). No evidence of TLS enforcement beyond typical sshd encryption; there is no fine-grained access control beyond SSH-level auth and user permissions.","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 programmatic API/MCP surface: an agent generally can’t “call” this like a service; it would need to run/build the container and interact via SSH.","SSH interactions are stateful; retries may change sessions/containers if not carefully controlled.","Key/password provisioning and host/network firewall rules are the primary integration risks rather than API parameters."]}}