MCP Observatory
4m ago Tracked 39,555 Last 4m ago 24h 3,133
npm JavaScript analyzed · update queued 1.10.0

@google-cloud/cloud-run-mcp

v1.10.0
npm

MCP server to deploy apps to Cloud Run

maintainer
google-admin
license
Apache-2.0
first seen
2026-05-22
last seen
2026-08-14
releases · 30d
0
short id
risk 30/100 · heuristic grade
B low
  • capability exposure inferred + 35
  • trust mitigators mixed − 5

inferred mixed

The A–E grade is our heuristic synthesis — a "review this" prompt, not a verdict. Each factor is tagged by what backs it: attested (a verifiable record), reported (a third party's claim), or inferred (our own heuristic, e.g. permissions). See methodology.

graded 3m ago · see ecosystem CVEs →

risk trajectory 1 movements
  • C · 45 → B · 30
capability exposure grade factor +35
Inferred surface — each links to servers holding it:
vulnerabilities 0 CVEs

No known CVEs for this server.

tool safety 2 findings · grade factor +0
  1. low dangerous code

    env-secret-flows-to-network-js: A process environment value (often a secret/token) flows into a network call — possible credential exfiltration. (package/mcp-server.js:186)

  2. low dangerous code

    env-secret-flows-to-network-js: A process environment value (often a secret/token) flows into a network call — possible credential exfiltration. (package/mcp-server.js:264)

skills & danger signals npm-tarball
prompt-surface shipped agent-instruction files + hidden-content / dangerous-code findings — quoted from the analyzed source

analyzed v1.10.0 · analyzer v31 · 2d ago

skills & prompt files 1

danger signals1

  • over-broad OAuth scope https://www.googleapis.com/auth/cloud-platform expected for this server's purpose package/constants.js :4 CLOUD_PLATFORM: 'https://www.googleapis.com/auth/cloud-platform',
embed badge readme-ready
live risk-grade badge preview [![MCP Observatory risk grade](https://mcpobservatory.com/servers/npm:@google-cloud/cloud-run-mcp/badge.svg)](https://mcpobservatory.com/servers/npm:@google-cloud/cloud-run-mcp/security)

Heuristic, inferred signals — false positives (legitimately powerful tools, forks, language ports) are expected. Treat each as "review this", not a verdict. See the ecosystem-wide picture on the security hub, or the fleet security of google-admin.