Observability (google-cloud) MCP Server
@google-cloud/observability-mcp
npm
v0.2.3
Official
Published by Google Cloud — an official vendor package. A brand name in a package name proves nothing; this one is verified by npm scope ownership or publish provenance.
MCP Server for GCP environment for interacting with various Observability APIs.
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 − 6 = 94. 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 |
|---|---|
| −6 | capability blast radius (high) — client exposure if the model is manipulated |
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 3
high Dynamic code execution in server code (dist/bundle.js)MTC-SRC-001
In the server's implementation (`dist/bundle.js:2942`): Evaluating strings as code is the most direct RCE primitive; if any tool input reaches it, the server executes attacker-chosen code. This is read from the code itself — not from the tool description — so a poisoned server cannot hide it behind honest-looking metadata.
Evidence: const makeValidate = new Function(`${names_1.default.self}`, `${names_1.default.scope}`, sourceCode); const v
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 dist/bundle.js
high Shell/command execution in server code (dist/bundle.js)MTC-SRC-002
In the server's implementation (`dist/bundle.js:28139`): Spawning a shell/process is command-execution capability; with unsanitized tool input it is command injection / RCE. This is read from the code itself — not from the tool description — so a poisoned server cannot hide it behind honest-looking metadata.
Evidence: lit("\n").map((line) => exec(line, columns, options)).join("\n"); } // ../../node_modules/cliui/index.mjs function ui(o
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 dist/bundle.js
medium Dynamic module load from a non-literal (dist/bundle.js)MTC-SRC-005
In the server's implementation (`dist/bundle.js:28768`): Loading a module chosen at runtime (from a variable) can pull in and run attacker-influenced code paths. This is read from the code itself — not from the tool description — so a poisoned server cannot hide it behind honest-looking metadata.
Evidence: config2 = mixin2.require(resolvedConfigPath); } setConfigObject(config2); } cat
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 dist/bundle.js
What this scan could not see
- No tools were enumerated, so prompt-injection, capability and toxic-flow analysis had no tool surface to inspect. To grade a package’s real runtime tools, 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.2.3 latest |
A 94/100 | 3 | 1.13.0 | 2026-08-30 |
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 @google-cloud/observability-mcp --onlineOther implementations of Observability 4
Independent packages implementing the same tool, scanned with the same engine. Compare all 5 side by side →
OpenTelemetry adapter for Stipend. Subscribes to observability hooks on @stipend-mcp/proxy and @stipend-mcp/api and emits spans, metrics, and structured logs.
Lightweight telemetry SDK for MCP servers and web applications. Captures HTTP requests, MCP tool invocations, business events, and UI interactions with built-in payload sanitization.
Observability for incident-response agents — query Loki logs (LogQL), Prometheus metrics (PromQL), and Elasticsearch. MCP server.
Unified observability gateway for AI agents — one MCP server for Prometheus, Loki, and any backend
More in Analytics & Monitoring
Public-safe MCP admin discovery contract descriptors and response builders.
Pokemon Champions battle advisor MCP server
Airflow MCP server — DAG list, runs, task instances, log tails, trigger and clear over the Airflow REST API
MCP analytics wrapper SDK that instruments MCP tool declarations with telemetry.
AI-ready GIS, geofencing, DataSynch, CRM, inventory, routing, APIs, telemetry and workflows.
AI-native social listening. Monitor buying signals and run GTM workflows via natural language.