MCP Observatory
4m ago Tracked 39,555 Last 4m ago 24h 3,133
npm JavaScript analyzed 0.2.3

@google-cloud/observability-mcp

v0.2.3
npm

MCP Server for GCP environment for interacting with various Observability APIs.

maintainer
google-admin
license
Apache-2.0
first seen
2026-05-22
last seen
2026-08-14
releases · 30d
0
short id
risk 12/100 · heuristic grade
A minimal
  • capability exposure inferred + 12
  • tool safety inferred + 5
  • 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 6 movements
  • B · 16 → A · 12
  • A · 0 → B · 16
  • A · 10 → A · 0
  • A · 7 → A · 10
  • A · 12 → A · 7
  • A · 7 → A · 12
capability exposure grade factor +12
Inferred surface — each links to servers holding it:
vulnerabilities 0 CVEs

No known CVEs for this server.

tool safety 1 findings · grade factor +5
  1. medium dangerous code

    dynamic exec: new Function()

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

analyzed v0.2.3 · analyzer v32 · 6h ago

danger signals2

  • dynamic code execution new Function() package/dist/bundle.js :2942 const makeValidate = new Function(`${names_1.default.self}`, `${names_1.default.scope}`, sourceCode);
  • over-broad OAuth scope https://www.googleapis.com/auth/cloud-platform expected for this server's purpose package/dist/bundle.js :26580 scopes: "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/observability-mcp/badge.svg)](https://mcpobservatory.com/servers/npm:@google-cloud/observability-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.