{"id":"lizhenliang-metrics-server","name":"metrics-server","homepage":"https://hub.docker.com/r/lizhenliang/metrics-server","repo_url":"https://hub.docker.com/r/lizhenliang/metrics-server","category":"monitoring","subcategories":[],"tags":["kubernetes","monitoring","autoscaling","metrics-api","hpa","cluster-observability"],"what_it_does":"metrics-server is a Kubernetes add-on that aggregates resource metrics (such as CPU and memory) from kubelets and exposes them to the Kubernetes API (commonly used by HPA/VPA and kubectl top).","use_cases":["Autoscaling with Kubernetes HPA based on CPU/memory utilization","Viewing live cluster resource utilization via kubectl top","Providing metrics to controllers/ops tooling that require Kubernetes Metrics API"],"not_for":["Long-term metrics storage/observability (Prometheus/Grafana are better fits)","Highly specialized telemetry pipelines","External/Internet-facing metrics exposure without network controls"],"best_when":"Used inside a Kubernetes cluster where kubelet access to the aggregator can be secured, and where you need the Kubernetes Metrics API for autoscaling and troubleshooting.","avoid_when":"You cannot securely grant the metrics-server access to kubelet stats endpoints, or when you require a full metrics/alerting stack rather than the Kubernetes Metrics API.","alternatives":["Prometheus + kube-state-metrics/node-exporter (for comprehensive observability)","KEDA (for event-driven autoscaling, though it still may rely on metrics sources)","cAdvisor/metrics pipelines depending on needs"],"af_score":46.5,"security_score":64.8,"reliability_score":36.2,"package_type":"mcp_server","discovery_source":["docker_mcp"],"priority":"low","status":"evaluated","version_evaluated":null,"last_evaluated":"2026-04-04T19:54:08.448659+00:00","interface":{"has_rest_api":true,"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 read metrics/metrics.k8s.io API)","Kubelet authentication/authorization as configured for metrics-server to scrape node stats (commonly via TLS and kubelet endpoints)"],"oauth":false,"scopes":false,"notes":"metrics-server itself is deployed as a Kubernetes component. Access to the exposed metrics API is typically controlled via Kubernetes RBAC rather than OAuth scopes."},"pricing":{"model":null,"free_tier_exists":false,"free_tier_limits":null,"paid_tiers":[],"requires_credit_card":false,"estimated_workload_costs":null,"notes":"Open-source component; cost is operational (cluster resources)."},"requirements":{"requires_signup":false,"requires_credit_card":false,"domain_verification":false,"data_residency":[],"compliance":[],"min_contract":null},"agent_readiness":{"af_score":46.5,"security_score":64.8,"reliability_score":36.2,"mcp_server_quality":0.0,"documentation_accuracy":40.0,"error_message_quality":0.0,"error_message_notes":null,"auth_complexity":55.0,"rate_limit_clarity":20.0,"tls_enforcement":85.0,"auth_strength":65.0,"scope_granularity":50.0,"dependency_hygiene":50.0,"secret_handling":70.0,"security_notes":"Security posture is largely determined by Kubernetes RBAC and the network/TLS configuration used for metrics-server to scrape kubelets. There is no evidence here of app-level secret leakage handling; assume best practices for cluster secrets and TLS validation, and avoid exposing metrics-server externally.","uptime_documented":0.0,"version_stability":55.0,"breaking_changes_history":50.0,"error_recovery":40.0,"idempotency_support":"false","idempotency_notes":null,"pagination_style":"none","retry_guidance_documented":false,"known_agent_gotchas":["metrics-server depends on kubelet access; common failures are TLS/auth/connectivity issues to kubelets","Kubernetes version/metrics.k8s.io API compatibility can affect behavior across clusters","If metrics are missing/empty, downstream autoscaling may not work; agents may need to check logs and APIService conditions rather than only request failures"]}}