A

container.googleapis.com

https://container.googleapis.com/mcp
94/100 · MCP Trust Grade · checked 5h ago · MCP 2025-06-18
✓ Watched since 2026-06-03 — behavioral baseline locked. We re-check this server's tool surface on a schedule; if it adds, removes, or silently rewrites a tool (rug-pull), we record it.

What it offers — 23 tools · Cloud & DevOps

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 resources i

get_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/kubernetes-e

update_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.

+5 more tools

Spec conformance20%100
Security (OWASP MCP)30%100
Reliability / performance20%92
Tool hygiene15%100
Transparency / provenance15%70

Observed behavior

No proxied traffic observed for this host yet. Connect it at /connect and its grade gains a measured Reliability score + per-tool behavioral evidence — the half a static scan can't produce.

Findings

No blocking issues found in the static + spec checks.
Grade another server

We re-grade container.googleapis.com on a schedule and alert your Slack/webhook the moment its tools change or its grade drops — rug-pull insurance for the connection.

Share this report card

A 1200×630 card with the grade + audit — drop it in a post, Slack, or your repo.

MCP Trust report card — container.googleapis.com grade A
Share on X Open card image

Embed this grade

A live badge — it re-verifies itself and shows current stability. Static scorecards can't. Paste it in your README or site to show users you're independently audited.

MCP Trust Grade A · wmcp.sh
[![MCP Trust Grade A](https://wmcp.sh/mcp/grade/container.googleapis.com/badge.svg)](https://wmcp.sh/mcp/grade/container.googleapis.com)
<a href="https://wmcp.sh/mcp/grade/container.googleapis.com"><img src="https://wmcp.sh/mcp/grade/container.googleapis.com/badge.svg" alt="MCP Trust Grade A · wmcp.sh"></a>

Agents: check this before connecting

Add the wmcp.sh trust oracle as an MCP server and call grade_mcp_server / check_mcp_drift in your agent's pre-connection gate:

https://wmcp.sh/mcp/trust
How this grade is computed. An open, independent rubric — Spec conformance (20%), Security mapped to the OWASP MCP Top 10 (30%), Reliability (20%), Tool hygiene (15%), Transparency (15%) — run by connecting to the server and inspecting its real MCP surface. The grade is free and identical whether or not the operator pays. v1 uses static + spec signals from a single connection; continuous uptime, real latency, and annotation-truthing (declared readOnly vs observed behavior) layer on via the wmcp.sh proxy.