{"id":"cirocosta-gitserver-http","name":"gitserver-http","homepage":"https://hub.docker.com/r/cirocosta/gitserver-http","repo_url":"https://hub.docker.com/r/cirocosta/gitserver-http","category":"infrastructure","subcategories":[],"tags":["git","version-control","http","self-hosted","reverse-proxy"],"what_it_does":"gitserver-http is an HTTP-oriented service for accessing a Git repository over HTTP. It typically exposes Git transport operations (e.g., smart HTTP endpoints) so clients can clone/fetch/pull without running a separate SSH git daemon.","use_cases":["Provide Git access to clients that only have HTTP/HTTPS connectivity","Self-hosted Git endpoints for CI systems and automation","Use behind a reverse proxy or within environments where SSH is restricted"],"not_for":["High-security environments that require strong user-level authorization beyond a network boundary (unless additional access controls are configured externally)","Workloads needing fine-grained per-repo or per-operation authz without external middleware","Use as a general-purpose Git hosting platform (issues, PRs, web UI, etc.)"],"best_when":null,"avoid_when":null,"alternatives":["nginx/git-http backend deployments","Git hosting platforms (GitHub/GitLab/Gitea)","git-daemon (git://) combined with network controls","SSH-based Git with hardened sshd"],"af_score":30.8,"security_score":44.8,"reliability_score":32.5,"package_type":"mcp_server","discovery_source":["docker_mcp"],"priority":"low","status":"evaluated","version_evaluated":null,"last_evaluated":"2026-04-04T19:43:27.371039+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":["HTTP basic auth / reverse-proxy auth (if configured externally)","Network-based access control (IP allowlist / auth at gateway)","Potential support for generic HTTP auth depending on configuration"],"oauth":false,"scopes":false,"notes":"No explicit auth model (scopes/OAuth) is evident from the package name/description alone; security typically relies on server/reverse-proxy configuration."},"pricing":{"model":null,"free_tier_exists":false,"free_tier_limits":null,"paid_tiers":[],"requires_credit_card":false,"estimated_workload_costs":null,"notes":null},"requirements":{"requires_signup":false,"requires_credit_card":false,"domain_verification":false,"data_residency":[],"compliance":[],"min_contract":null},"agent_readiness":{"af_score":30.8,"security_score":44.8,"reliability_score":32.5,"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":20.0,"tls_enforcement":70.0,"auth_strength":35.0,"scope_granularity":20.0,"dependency_hygiene":40.0,"secret_handling":60.0,"security_notes":"Security depends heavily on deployment configuration (TLS termination, access control, auth at proxy, and repository permissions). Without explicit evidence of fine-grained auth and documented security controls, treat it as primarily a network/proxy-controlled service.","uptime_documented":0.0,"version_stability":50.0,"breaking_changes_history":50.0,"error_recovery":30.0,"idempotency_support":"false","idempotency_notes":null,"pagination_style":"none","retry_guidance_documented":false,"known_agent_gotchas":["Git-over-HTTP has protocol-specific endpoints and status behaviors; generic HTTP retry logic may not be appropriate for failed smart HTTP operations.","Authentication/authorization behavior may depend on external reverse-proxy configuration rather than the application itself.","Without a documented contract (e.g., OpenAPI), agents may need protocol knowledge to form correct requests."]}}