Google Tag Manager MCP Server

google-tag-manager-mcp-server npm v3.0.5

Published by an unidentified publisher — no publish provenance and no vendor-owned scope, so the publisher could not be verified. The repository link below is self-declared.

Trust grade
A
92/100
Last scanned
Trust
A · 92/100
How safe the published surface and source look. Deterministic; every point is auditable.
Capability
High
Blast radius if it went rogue — what the server’s tools could reach. Independent of trust.
Coverage
Source
How much the scan could actually inspect. Shallow coverage is stated, never hidden.
A Why this grade 100 − 8.4 = 92/100

Every server starts at 100. These are the exact deductions the deterministic engine applied — each one reproducible, none of it an opinion or an LLM's guess:

PointsWhat was foundCategory
−6.3 Package runs install-time scripts MTC-SUP-010 supply-chain
−2.1 Package has no source repository MTC-SUP-011 supply-chain

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 the deduction.

Findings 5

high Shell/command execution in server code (worker-configuration.d.ts)MTC-SRC-002

In the server's implementation (`worker-configuration.d.ts:2212`): 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: exec(

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 worker-configuration.d.ts

medium Hardcoded egress to an external endpoint (dist/utils/apisHandler.js)MTC-SRC-003

In the server's implementation (`dist/utils/apisHandler.js:83`): A hardcoded outbound call to a fixed external host inside server code is a classic exfiltration/telemetry channel — especially paired with reads of local data. This is read from the code itself — not from the tool description — so a poisoned server cannot hide it behind honest-looking metadata.

Evidence: fetch("https://www.googleapis.com/oauth2/v2/userinfo"

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/utils/apisHandler.js

medium Hardcoded egress to an external endpoint (src/utils/apisHandler.ts)MTC-SRC-003

In the server's implementation (`src/utils/apisHandler.ts:127`): A hardcoded outbound call to a fixed external host inside server code is a classic exfiltration/telemetry channel — especially paired with reads of local data. This is read from the code itself — not from the tool description — so a poisoned server cannot hide it behind honest-looking metadata.

Evidence: fetch( "https://www.googleapis.com/oauth2/v2/userinfo"

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/utils/apisHandler.ts

medium Package runs install-time scripts (postinstall)MTC-SUP-010

"google-tag-manager-mcp-server" executes postinstall script(s) at install time. The large majority of malicious packages abuse install hooks to run code before you ever import them.

Fix: Review the scripts; install with --ignore-scripts where possible and vet what they do.

Location: package google-tag-manager-mcp-server

low Package has no source repositoryMTC-SUP-011

"google-tag-manager-mcp-server" declares no repository URL, so its published artifact cannot be compared against reviewable source.

Fix: Prefer packages that link to public, reviewable source.

Location: package google-tag-manager-mcp-server

What this scan could not see

Versions

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.

VersionScoreFindingsEngineScanned
v3.0.5 latest A 92/100 5 1.5.0 2026-07-22

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.

MCP Trust Score: A · 92/100
Markdown (GitHub README)
[![MCP Trust Score](https://mcptrustchecker.com/registry/google-tag-manager-mcp-server/badge.svg)](https://mcptrustchecker.com/registry/google-tag-manager-mcp-server)
HTML
<a href="https://mcptrustchecker.com/registry/google-tag-manager-mcp-server"><img src="https://mcptrustchecker.com/registry/google-tag-manager-mcp-server/badge.svg" alt="MCP Trust Score" height="20"></a>
Prefer shields.io styling? Point it at https://mcptrustchecker.com/registry/google-tag-manager-mcp-server/badge.json via https://img.shields.io/endpoint?url=…

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-tag-manager-mcp-server --online

Use the free API → How scoring works

More in Marketing & Social