Gcp (PyPI) MCP Server
gcp-mcp
PyPI
v0.1.0
Published by an unidentified publisher — no publish provenance and no public repository, so the publisher could not be verified and the source cannot be independently located.
MCP interface for Google Cloud Platform
The grade answers one question — how safe is this server for you to adopt — so it is computed in two auditable stages. Nothing below is an opinion or an LLM's guess; every line is a real term the deterministic engine applied, and the same input always yields the same number.
1. Threat score — 100 − 0 = 100. What the published surface and source actually contain:
The deterministic scan raised no scored threat in the surface it inspected — the threat score stayed at 100. Capability observations and advisory notes are recorded but never lower it.
2. Client adoption risk — 100 − 5 = 95. Three small, subtract-only factors that reflect your risk in adopting it — a clean scan proves less on a powerful, unverified or barely-inspectable package, so the grade says so plainly:
| Points | Adoption-risk factor |
|---|---|
| −3 | capability blast radius (moderate) — client exposure if the model is manipulated |
| −2 | publisher verification (unlinked) — no provenance/repo link, but the shipped source was fully read |
Capability observations and info notes are shown under Findings but never scored.
Open any row's finding below for the file, line and evidence behind a deduction.
Findings 1
high Reads a sensitive credential path or dumps the environment (src/gcp_mcp/gcp_modules/auth/tools.py)MTC-SRC-006
In the server's implementation (`src/gcp_mcp/gcp_modules/auth/tools.py:192`): Reading private keys / cloud credentials, or serializing the whole environment, is a sensitive-data source that becomes exfiltration when combined with any egress. This is read from the code itself — not from the tool description — so a poisoned server cannot hide it behind honest-looking metadata.
Evidence: = os.path.expanduser("~/.config/gcloud/credentials") if os.path.isdir(credentials_dir):
Fix: Review this call path: confirm it never receives unsanitized tool input, constrain it, or remove it. Treat a server whose code reaches these sinks as high-capability regardless of what its tools claim.
Location: server src/gcp_mcp/gcp_modules/auth/tools.py
Tools 56
Each tool and what it can reach — statically extracted from the published source.
download_objectingests untrusted inputadd_iam_policy_bindingno sensitive capabilityauth_listno sensitive capabilityauth_loginno sensitive capabilityauth_revokeno sensitive capabilitycheck_iam_permissionsno sensitive capabilityconfig_listno sensitive capabilityconfig_set_projectno sensitive capabilitycreate_alert_policyno sensitive capabilitycreate_backupno sensitive capability
Show 46 more tools ↓
create_firewall_ruleno sensitive capabilitycreate_instanceno sensitive capabilitycreate_service_accountno sensitive capabilitycreate_snapshotno sensitive capabilitydelete_instanceno sensitive capabilitydelete_objectno sensitive capabilityget_billing_infono sensitive capabilityget_bucket_detailsno sensitive capabilityget_cluster_detailsno sensitive capabilityget_deployment_detailsno sensitive capabilityget_gcp_project_detailsno sensitive capabilityget_instance_detailsno sensitive capabilityget_monitoring_alertsno sensitive capabilityget_role_permissionsno sensitive capabilityget_sql_instance_detailsno sensitive capabilityget_vpc_detailsno sensitive capabilitylist_assetsno sensitive capabilitylist_cloud_build_triggersno sensitive capabilitylist_cloud_sql_instancesno sensitive capabilitylist_compute_instancesno sensitive capabilitylist_databasesno sensitive capabilitylist_deployment_manager_deploymentsno sensitive capabilitylist_disksno sensitive capabilitylist_firestore_collectionsno sensitive capabilitylist_firestore_databasesno sensitive capabilitylist_firewall_rulesno sensitive capabilitylist_gcp_projectsno sensitive capabilitylist_gcp_servicesno sensitive capabilitylist_gke_clustersno sensitive capabilitylist_machine_typesno sensitive capabilitylist_monitoring_metricsno sensitive capabilitylist_node_poolsno sensitive capabilitylist_objectsno sensitive capabilitylist_rolesno sensitive capabilitylist_service_accountsno sensitive capabilitylist_snapshotsno sensitive capabilitylist_storage_bucketsno sensitive capabilitylist_subnetsno sensitive capabilitylist_uptime_checksno sensitive capabilitylist_vpc_networksno sensitive capabilityresize_node_poolno sensitive capabilitysay_hellono sensitive capabilityset_quota_projectno sensitive capabilitystart_instanceno sensitive capabilitystop_instanceno sensitive capabilityupload_objectno sensitive capability
What this scan could not see
- Tools were statically extracted from the published source (56 recovered), not enumerated from a running server. Tool-poisoning, Unicode-smuggling, capability and toxic-flow analysis ran on this inferred surface, but a mis-parsed registration could be missed or mis-attributed, so tool-derived findings are capped below “confirmed”. To grade the real runtime surface, scan the running server: --command "npx -y <package>".
Versions 1
Scan history per published version. The engine is deterministic — the same version always yields the same score, so a changed score means the package itself changed.
| Version | Score | Findings | Engine | Scanned |
|---|---|---|---|---|
v0.1.0 latest |
A 95/100 | 1 | 1.13.0 | 2026-08-25 |
Embed this score
Show this server's live Trust Score in your README, docs or website. The badge is served straight from the registry and updates automatically after every rescan — no API key needed. It links back to this page, so anyone who sees the grade can also read the findings behind it instead of taking a number on faith.
Verify this score yourself
The score above is reproducible: the same package version always yields the same result. Run it locally or over the free API — no account, no LLM, fully deterministic.
npx mcptrustchecker scan gcp-mcp --online --registry pypiOther implementations of Gcp 5
Independent packages implementing the same tool, scanned with the same engine. Compare all 6 side by side →
Model Context Protocol (MCP) server for Google Cloud Platform - Talk to your GCP resources
MCP server package - managed by mcp-prep
An MCP server providing tools for GCP Cloud Functions logs
Server for Google Cloud Platform that lets you talk to your GCP resources.
MCP server package - managed by mcp-prep
More in Databases
Security scan results for the A5sql MCP server.
Expose AgentsKit tools as an MCP server — use them from Claude Desktop, Cursor, Windsurf, or any MCP host.
MCP server for Aiven cloud data platform - manage PostgreSQL, Kafka, and other services
MCP Server for All-Inkl.com hosting via KAS API
Structured aquarium, marine, terrarium and paludarium data for AI agents.
MCP server that gives your AI agent real vehicle data — specs, representative images, federal recalls, owner complaints, service bulletins, defect investigations, and OBD-II DTC reference — from the CarVector API.