container.googleapis.com
https://container.googleapis.com/mcp
active Production-safe Score 100/100 http no auth
At a glance
| Endpoint | https://container.googleapis.com/mcp |
|---|---|
| Source | https://raw.githubusercontent.com/zchee/agent/main/gemini/settings.json |
| Transport | http |
| Tools | 27 |
| Auth | none |
| First seen | 2026-05-24 03:43:22 |
| Last checked | 2026-11-17 21:43:50 |
Observed reliability
| 7-day uptime | 100% |
|---|---|
| 24-hour uptime | 100% |
| Handshake success | 100% |
| Latency p50 / p95 | 89 / 308 ms |
| Last successful check | 2026-11-17 21:43:50 |
Measured by Arclan's validator via repeated live MCP handshakes. How this is computed →
Tools (27)
list_k8s_api_resources— Retrieves the available API groups and resources from a Kubernetes cluster. This is similar to running `kubectl api-resources`.check_k8s_auth— Checks whether an action is allowed on a Kubernetes resource. This is similar to running `kubectl auth can-i`.describe_k8s_resource— Shows the details of a specific Kubernetes resource. This is similar to running `kubectl describe`.list_k8s_events— Retrieves events from a Kubernetes cluster. This is similar to running `kubectl events`.get_k8s_resource— Gets one or more Kubernetes resources from a cluster. Resources can be filtered by type, name, namespace, and label selectors. Returns the rget_k8s_cluster_info— Gets cluster endpoint information. This is similar to running `kubectl cluster-info`.get_k8s_version— Retrieves Kubernetes client and server versions for a given cluster. This is similar to running `kubectl version`.get_k8s_rollout_status— Checks the current rollout status of a Kubernetes resource. This is similar to running `kubectl rollout status`.list_clusters— Lists GKE clusters in a given project and location. Location can be a region, zone, or '-' for all locations.create_cluster— Creates a new GKE cluster in a given project and location. It's recommended to read the [GKE documentation](https://docs.cloud.google.com/kuupdate_cluster— Updates a specific GKE cluster.get_cluster— Gets the details of a specific GKE cluster.list_operations— Lists GKE operations in a given project and location. Location can be a region, zone, or '-' for all locations.get_operation— Gets the details of a specific GKE operation.cancel_operation— Cancels a specific GKE operation.create_node_pool— Creates a node pool for a specific GKE cluster.list_node_pools— Lists the node pools for a specific GKE cluster.get_node_pool— Gets the details of a specific node pool within a GKE cluster.update_node_pool— Updates a specific node pool within a GKE cluster.get_k8s_logs— Gets logs from a Kubernetes container in a pod. This is similar to running `kubectl logs`.apply_k8s_manifest— Applies a Kubernetes manifest to a cluster using server-side apply. This is similar to running `kubectl apply --server-side`.delete_k8s_resource— Deletes a Kubernetes resource from a cluster. This is similar to running `kubectl delete`.patch_k8s_resource— Patches a Kubernetes resource. This is similar to running `kubectl patch`.diagnose_k8s_workload— Collects a correlated incident snapshot for a Kubernetes workload (Deployment, StatefulSet, DaemonSet), verifying referenced ConfigMaps, Secget_k8s_cluster_health— Computes a high-level health scorecard across nodes, workloads, system pods, and control-plane components (GKE cluster state, admission webhget_k8s_log_summary— Fetches and deduplicates container logs using pattern fingerprinting to reduce token usage. Prefer this over get_k8s_logs when triaging craslist_k8s_cluster_issues— Scans a cluster or namespace for abnormal pods (CrashLoopBackOff, OOMKilled, ImagePullBackOff), node pressure, stalled rollouts, quota exhau
Validation history
| Checked | Reachable | Handshake | Latency | Score | State |
|---|---|---|---|---|---|
| 2026-11-17 21:43:50 | ✓ | ✓ | 71 ms | 99 | active |
| 2026-11-17 21:28:44 | ✓ | ✓ | 325 ms | 92 | active |
| 2026-11-17 21:13:40 | ✓ | ✓ | 80 ms | 99 | active |
| 2026-11-17 20:58:39 | ✓ | ✓ | 85 ms | 99 | active |
| 2026-11-17 20:43:38 | ✓ | ✓ | 230 ms | 96 | active |
| 2026-11-17 20:28:36 | ✓ | ✓ | 87 ms | 99 | active |
| 2026-11-17 20:13:34 | ✓ | ✓ | 223 ms | 96 | active |
| 2026-11-17 19:58:34 | ✓ | ✓ | 358 ms | 92 | active |
| 2026-11-17 19:43:32 | ✓ | ✓ | 230 ms | 96 | active |
| 2026-11-17 19:28:31 | ✓ | ✓ | 69 ms | 99 | active |
| 2026-11-17 19:13:28 | ✓ | ✓ | 80 ms | 99 | active |
| 2026-11-17 18:58:27 | ✓ | ✓ | 240 ms | 96 | active |
| 2026-11-17 18:43:24 | ✓ | ✓ | 179 ms | 96 | active |
| 2026-11-17 18:28:22 | ✓ | ✓ | 83 ms | 99 | active |
| 2026-11-17 18:13:21 | ✓ | ✓ | 64 ms | 99 | active |
Query this programmatically
Agents can pull this record live over the MCP protocol or REST:
get_server("https://container.googleapis.com/mcp") # via the Arclan MCP endpoint https://arclan.ai/mcp
GET https://arclan.ai/api/registry/container-googleapis-com-mcp # JSON