GCP Platform Engineer
PYPI · PLATFORM-MCP · SCANNED SEP 20
Read-only GCP tools for debugging incidents and finding cost savings
Available components
How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score → Why this is hard to score →
Supply Chain Security50
- Malware scan not yet available for this package.Unverified
- No known CVEs affecting this package version or its production dependencies.Pass
- Runs setuptools.build_meta at install time, a recognised native-build step with no shell scripting around it. View diagnostics → Pass
- 1 of 63 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency32
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Provenance check failed: no build-provenance attestation is published. See how to fix → View diagnostics → Fail
- License check failed: no license is declared. See how to fix → Fail
- Actively maintained (last published 18 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability70
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 2337 tokens (~146/item across 16 items; 16 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management70
- Stability observed for 21 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage67
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 0% of tool parameters carry a description.Fail
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 16 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 17 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
How do I install the GCP Platform Engineer MCP server?
GCP Platform Engineer runs locally as a PyPI package, launched with uvx platform-mcp. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
pypi · platform-mcp
claude mcp add debilla-platform-mcp -- uvx platform-mcp
{
"mcpServers": {
"debilla-platform-mcp": {
"command": "uvx",
"args": [
"platform-mcp"
]
}
}
} {
"servers": {
"debilla-platform-mcp": {
"command": "uvx",
"args": [
"platform-mcp"
]
}
}
} codex mcp add debilla-platform-mcp -- uvx platform-mcp
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"debilla-platform-mcp": {
"type": "local",
"command": [
"uvx",
"platform-mcp"
],
"enabled": true
}
}
} openclaw mcp add debilla-platform-mcp --command uvx --arg platform-mcp
mcp_servers:
debilla-platform-mcp:
command: "uvx"
args: ["platform-mcp"] {
"McpServers": {
"debilla-platform-mcp": {
"Transport": "stdio",
"Command": "uvx",
"Arguments": [
"platform-mcp"
]
}
}
} assistant mcp add debilla-platform-mcp -t stdio -c uvx -a platform-mcp
{
"mcpServers": {
"debilla-platform-mcp": {
"command": "uvx",
"args": [
"platform-mcp"
]
}
}
} Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 19 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 63 to 67. That category is still filling its 30-day observation window: 19 days of observed history at the previous scan, 20 at this one. The score rises as the window fills, whether or not the server changes.
- 17 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 57 to 60. That category is still filling its 30-day observation window: 17 days of observed history at the previous scan, 18 at this one. The score rises as the window fills, whether or not the server changes.
- 15 Sept 26 +1
- Security disclosure: unverified → fail ▼ functional
- 14 Sept 26 0
- Security disclosure: fail → unverified ▼ functional
- 13 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 43 to 47. That category is still filling its 30-day observation window: 13 days of observed history at the previous scan, 14 at this one. The score rises as the window fills, whether or not the server changes.
- 10 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 33 to 37. That category is still filling its 30-day observation window: 10 days of observed history at the previous scan, 11 at this one. The score rises as the window fills, whether or not the server changes.
- 8 Sept 26 −14
- Malware scan: pass → unverified ▼ security
- 6 Sept 26 +16
- Malware scan: unverified → pass ▲ security
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 20 Sept 2026 · Analysed pypi/platform-mcp@0.4.0
Provenance No attestation
The registry publishes no build provenance for this version, so there is nothing to verify.
| Result | No attestation |
|---|---|
| Ecosystem | pypi |
Background: How many MCP packages publish verified provenance →
Install scripts 1 script
| Hook | Tier | Command |
|---|---|---|
| build_backend | allowlisted | setuptools.build_meta |
Background: Why install scripts are a supply-chain risk →
Dependencies 63 packages
| Packages resolved | 63 |
|---|---|
| Stale | 1 |
| Tree resolution | Complete |
Background: SBOMs and build attestations, explained →
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
get_billing_info ~62
Return the billing account linked to the project and its status. Args: environment: Which configured GCP environment to inspect, e.g. 'staging' or 'production'. Omit to use the default environment.
| Name | Type | Req | Description |
|---|---|---|---|
| environment | string | – | – |
No output schema declared.
No examples provided.
get_cost_breakdown ~289
Summarize recent spend from the BigQuery billing export. By default this reports spend for the selected environment's project only. A billing export table covers every project on the billing account, and several environments commonly share one table, so an unfiltered query would return identical account-wide totals for staging and production. Only the environment holding the export needs 'billing_export_table' set: one billing account exports to one project, and that export already covers every project on the account. Asking any other environment for costs returns an error naming the one that has it. Args: group_by: One of 'service', 'sku', 'project', 'region'. Default 'service'. days: Lookback window in days over usage_start_time. Default 30. limit: Max rows returned (highest net cost first). all_projects: Report the whole billing account instead of just this environment's project. Pair with group_by='project' to compare projects; the totals then are not specific to this environment. environment: Which configured GCP environment to bill against, e.g. 'staging' or 'production'. Omit to use the default environment.
| Name | Type | Req | Description |
|---|---|---|---|
| all_projects | boolean | – | – |
| days | integer | – | – |
| environment | string | – | – |
| group_by | string | – | – |
| limit | integer | – | – |
No output schema declared.
No examples provided.
get_recent_errors ~130
Return recent log entries at severity ERROR or higher. Args: service: Optional service name to narrow to (matched against resource.labels.service_name and logName). hours: How many hours back to search. Default 1. limit: Maximum number of entries to return (newest first). environment: Which configured GCP environment to query, e.g. 'staging' or 'production'. Omit to use the default environment.
| Name | Type | Req | Description |
|---|---|---|---|
| environment | string | – | – |
| hours | integer | – | – |
| limit | integer | – | – |
| service | string | – | – |
No output schema declared.
No examples provided.
list_alert_policies ~78
List Cloud Monitoring alert policies and whether they are enabled. Args: limit: Maximum number of policies to return. environment: Which configured GCP environment to query, e.g. 'staging' or 'production'. Omit to use the default environment.
| Name | Type | Req | Description |
|---|---|---|---|
| environment | string | – | – |
| limit | integer | – | – |
No output schema declared.
No examples provided.
list_cloud_run_services ~72
List Cloud Run services. Args: limit: Maximum number of services to return. environment: Which configured GCP environment to query, e.g. 'staging' or 'production'. Omit to use the default environment.
| Name | Type | Req | Description |
|---|---|---|---|
| environment | string | – | – |
| limit | integer | – | – |
No output schema declared.
No examples provided.
list_compute_instances ~76
List Compute Engine VM instances with location and status. Args: limit: Maximum number of instances to return. environment: Which configured GCP environment to query, e.g. 'staging' or 'production'. Omit to use the default environment.
| Name | Type | Req | Description |
|---|---|---|---|
| environment | string | – | – |
| limit | integer | – | – |
No output schema declared.
No examples provided.
list_cost_recommendations ~170
Aggregate GCP cost-optimization recommendations (idle/rightsizing/etc). Fans out the cost recommenders across the locations where the project has resources. Recommenders/locations that are empty or not enabled are skipped. Args: locations: Optional comma-separated zones/regions to scan (e.g. 'us-central1,us-central1-a'). If empty, auto-discovers from Asset Inventory (requires the Cloud Asset API). limit_per_call: Max recommendations to pull per recommender+location. environment: Which configured GCP environment to query, e.g. 'staging' or 'production'. Omit to use the default environment.
| Name | Type | Req | Description |
|---|---|---|---|
| environment | string | – | – |
| limit_per_call | integer | – | – |
| locations | string | – | – |
No output schema declared.
No examples provided.
list_environments ~90
List the GCP environments this server can query and which is the default. Pass one of the returned names as the `environment` argument of any other tool to target that project (e.g. environment='production'). Omitting the argument uses the default environment shown here. Common shorthands such as 'prod' and 'stg' are accepted, as is a bare project id.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
list_error_groups ~149
List grouped application errors from Error Reporting with counts. Args: hours: Lookback window; snapped to the nearest supported period (1h, 6h, 1d, 1w, 30d). Default 24. service: Optional service name filter (Error Reporting "service" label). limit: Maximum number of error groups to return (most frequent first). environment: Which configured GCP environment to query, e.g. 'staging' or 'production'. Omit to use the default environment.
| Name | Type | Req | Description |
|---|---|---|---|
| environment | string | – | – |
| hours | integer | – | – |
| limit | integer | – | – |
| service | string | – | – |
No output schema declared.
No examples provided.
list_gke_clusters ~77
List GKE (Kubernetes Engine) clusters. Args: limit: Maximum number of clusters to return. environment: Which configured GCP environment to query, e.g. 'staging' or 'production'. Omit to use the default environment.
| Name | Type | Req | Description |
|---|---|---|---|
| environment | string | – | – |
| limit | integer | – | – |
No output schema declared.
No examples provided.
list_recommendations ~172
List recommendations from a specific recommender at a specific location. Args: recommender_id: Recommender id, e.g. 'google.compute.instance.MachineTypeRecommender' or 'google.iam.policy.Recommender'. location: Zone (e.g. 'us-central1-a'), region (e.g. 'us-central1'), or 'global' depending on the recommender. Default 'global'. limit: Maximum number of recommendations to return. environment: Which configured GCP environment to query, e.g. 'staging' or 'production'. Omit to use the default environment.
| Name | Type | Req | Description |
|---|---|---|---|
| environment | string | – | – |
| limit | integer | – | – |
| location | string | – | – |
| recommender_id | string | yes | – |
No output schema declared.
No examples provided.
list_sql_instances ~71
List Cloud SQL instances. Args: limit: Maximum number of instances to return. environment: Which configured GCP environment to query, e.g. 'staging' or 'production'. Omit to use the default environment.
| Name | Type | Req | Description |
|---|---|---|---|
| environment | string | – | – |
| limit | integer | – | – |
No output schema declared.
No examples provided.
list_uptime_checks ~75
List Cloud Monitoring uptime check configurations. Args: limit: Maximum number of uptime checks to return. environment: Which configured GCP environment to query, e.g. 'staging' or 'production'. Omit to use the default environment.
| Name | Type | Req | Description |
|---|---|---|---|
| environment | string | – | – |
| limit | integer | – | – |
No output schema declared.
No examples provided.
query_logs ~166
Query Cloud Logging with an advanced-filter expression. Args: filter: Cloud Logging advanced filter (e.g. 'severity>=WARNING AND resource.type="cloud_run_revision"'). Leave empty to match all logs. freshness: How far back to look, e.g. '30m', '1h', '2d'. Default '1h'. limit: Maximum number of entries to return (newest first). environment: Which configured GCP environment to query, e.g. 'staging' or 'production'. Omit to use the default environment. Call list_environments to see what is configured.
| Name | Type | Req | Description |
|---|---|---|---|
| environment | string | – | – |
| filter | string | – | – |
| freshness | string | – | – |
| limit | integer | – | – |
No output schema declared.
No examples provided.
query_metric ~243
Query a Cloud Monitoring metric time series. Args: metric_type: Metric type, e.g. 'compute.googleapis.com/instance/cpu/utilization'. resource_filter: Optional extra filter, e.g. 'resource.labels.instance_id="123"'. window: How far back to query, e.g. '1h', '6h', '1d'. Default '1h'. aligner: Aggregation across the alignment period: MEAN, MAX, MIN, SUM, COUNT, RATE, PERCENTILE_99. Default MEAN. alignment_period: Bucket size for aggregation, e.g. '1m', '5m'. Default '5m'. limit: Maximum number of time series to return. environment: Which configured GCP environment to query, e.g. 'staging' or 'production'. Omit to use the default environment.
| Name | Type | Req | Description |
|---|---|---|---|
| aligner | string | – | – |
| alignment_period | string | – | – |
| environment | string | – | – |
| limit | integer | – | – |
| metric_type | string | yes | – |
| resource_filter | string | – | – |
| window | string | – | – |
No output schema declared.
No examples provided.
search_assets ~229
Search all cloud resources in the project via Cloud Asset Inventory. Args: asset_types: Optional comma-separated asset types to filter, e.g. 'compute.googleapis.com/Instance,run.googleapis.com/Service'. query: Optional free-text/structured query, e.g. 'state:RUNNING' or 'location:us-central1'. limit: Maximum number of resources to return. Default 50; raise it when you know you need a full inventory, since each resource costs context. include_labels: Include resource labels. Off by default because deployment labels are usually the largest part of the response and rarely answer the question being asked. environment: Which configured GCP environment to search, e.g. 'staging' or 'production'. Omit to use the default environment. Call list_environments to see what is configured.
| Name | Type | Req | Description |
|---|---|---|---|
| asset_types | string | – | – |
| environment | string | – | – |
| include_labels | boolean | – | – |
| limit | integer | – | – |
| query | string | – | – |
No output schema declared.
No examples provided.
What is the GCP Platform Engineer MCP server?
GCP Platform Engineer is an MCP server listed in the public MCP registry as io.github.deBilla/platform-mcp. Read-only GCP tools for debugging incidents and finding cost savings. This page covers its PyPI package (platform-mcp).
Is the GCP Platform Engineer MCP server safe to use?
GCP Platform Engineer scores 59 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 20 September 2026. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the GCP Platform Engineer MCP server expose?
GCP Platform Engineer exposes 16 tools: list_environments, query_logs, get_recent_errors, list_error_groups, query_metric, and 11 more. Their descriptions and schemas cost roughly 2,149 tokens of context every time the server is loaded.
Is the GCP Platform Engineer MCP server still maintained?
GCP Platform Engineer is still listed as active in the MCP registry. We last reached this channel on 20 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.