{"id":"eipwork-metrics-server","name":"metrics-server","homepage":"https://hub.docker.com/r/eipwork/metrics-server","repo_url":"https://hub.docker.com/r/eipwork/metrics-server","category":"monitoring","subcategories":[],"tags":["kubernetes","metrics","observability","autoscaling","hpa","infrastructure"],"what_it_does":"metrics-server is a Kubernetes add-on that aggregates resource usage metrics (CPU/memory) from kubelets and makes them available to the Kubernetes Metrics API (used by Horizontal Pod Autoscaler and kubectl top).","use_cases":["Enable kubectl top for pods/nodes in a cluster","Support HPA (autoscaling) based on resource utilization","Provide cluster resource utilization visibility for dashboards/automation"],"not_for":["Collecting application-level metrics (logs/traces, business KPIs)","Replacing full observability stacks (Prometheus/Grafana/OpenTelemetry)","Long-term metrics storage/analytics"],"best_when":"You need Kubernetes resource metrics via the Metrics API and have a standard Kubernetes environment where kubelet endpoints are reachable.","avoid_when":"Your environment cannot reach kubelets/metrics endpoints due to network policies/firewalls, or you require only application-level metrics.","alternatives":["Prometheus + adapter (e.g., prometheus-adapter)","Kube-state-metrics (for object/state metrics, not resource usage)","Cloud provider metrics services (when Kubernetes-native Metrics API isn’t suitable)"],"af_score":29.2,"security_score":54.2,"reliability_score":37.5,"package_type":"mcp_server","discovery_source":["docker_mcp"],"priority":"low","status":"evaluated","version_evaluated":null,"last_evaluated":"2026-04-04T19:56:25.928075+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":["Kubernetes RBAC (service account permissions to access metrics endpoints and register APIService)"],"oauth":false,"scopes":false,"notes":"This is typically operated in-cluster; access control is governed by Kubernetes RBAC and TLS/authorization between components rather than external API auth."},"pricing":{"model":null,"free_tier_exists":false,"free_tier_limits":null,"paid_tiers":[],"requires_credit_card":false,"estimated_workload_costs":null,"notes":"Open-source/community software; no vendor pricing information provided in the supplied data."},"requirements":{"requires_signup":false,"requires_credit_card":false,"domain_verification":false,"data_residency":[],"compliance":[],"min_contract":null},"agent_readiness":{"af_score":29.2,"security_score":54.2,"reliability_score":37.5,"mcp_server_quality":0.0,"documentation_accuracy":30.0,"error_message_quality":0.0,"error_message_notes":null,"auth_complexity":45.0,"rate_limit_clarity":10.0,"tls_enforcement":60.0,"auth_strength":55.0,"scope_granularity":45.0,"dependency_hygiene":50.0,"secret_handling":60.0,"security_notes":"Security largely depends on in-cluster TLS, RBAC, and network reachability to kubelets. As an in-cluster component, it generally avoids external secret distribution, but improper RBAC or overly permissive kubelet access can increase risk. No evidence of fine-grained OAuth scopes or external API rate-limit headers from the provided data.","uptime_documented":0.0,"version_stability":55.0,"breaking_changes_history":50.0,"error_recovery":45.0,"idempotency_support":"false","idempotency_notes":null,"pagination_style":"none","retry_guidance_documented":false,"known_agent_gotchas":["metrics-server is deployed in Kubernetes; agent automation must handle manifests/Helm and cluster-specific RBAC/networking","metrics collection can fail due to kubelet auth/TLS/network-policy issues; those failures may not be exposed via a simple external API","behavior varies by Kubernetes version; compatibility issues can appear during upgrades"]}}