Is Google Tag Manager safe and trustworthy?

tashan scores Google Tag Manager on public evidence — tashan score 51.0/100, it is currently active, note: a single primary maintainer (bus-factor risk), no known advisories against the current release, it runs a script at install time, its declared dependencies reach: cloud, credentials. Audit scope: OSV advisories, install-time scripts, build provenance and declared permission surface. We do not review source code or execute the capability.

How do I install Google Tag Manager?

In Claude Code: run `claude mcp add google-tag-manager-mcp-server -- npx -y google-tag-manager-mcp-server`. In Cursor / Claude Desktop, add it to mcp.json / claude_desktop_config.json.

Who maintains Google Tag Manager?

See the linked source repository..

‹ The Index

Google Tag Manager

npm

MCP server for Google Tag Manager

Works with: Claude Code, Cursor, Claude Desktop, Codex CLI, Gemini CLI, Cline, Windsurf, VS Code (installable)
installable: each client documents how to load an MCP server of this type — that is the client's promise, not a claim verified against this capability

Category: Files & Memory — see all ranked ›

Install (Claude Code):

claude mcp add google-tag-manager-mcp-server -- npx -y google-tag-manager-mcp-server

tashan score: 51.0
Adoption: 64/wk
Upkeep: 63.0
Freshness: 94.0
Evidence coverage: 100% of the inputs this score can use
Health: active
License: Apache-2.0

Security audit

Every finding is shown in full — which advisory, the version that fixes it, and the exact command run at install time. Nothing in this audit is behind a licence.

No known advisoriesclearchecked against OSV for 3.0.6 — this package, not its dependency tree

Runs a script at install timecodenpm run build

Talks to cloud provider APIs · Handles credentials or secretsfrom declared dependencies

No build provenanceno attestation — the published artifact cannot be traced to its source

What changed recently

2026-08-10 google-tag-manager-mcp-server now reaches cloud, credentials Its declared dependencies reach further into your machine than they did before.
2026-08-10 google-tag-manager-mcp-server now runs a script when it installs Install-time code executes on your machine before you have used the tool once, and it did not do this before.

You are reading this because you came looking. tashan Pro gives tashan doctor the history behind it, so a run over your own config says which of YOURS moved.

You searched for one. Check the rest of your stack:

npx tashan-cli doctor

Reads the config already on your machine and names what is dead, deprecated or running code at install time. No account, nothing uploaded.

tashan Pro$6/mo

We recorded 2 changes to Google Tag Manager in the last 45 days. Pro tells you on the day — for the servers in your own config, not the ones you thought to look up.

Every score since we started measuring, for any capability
The named replacement when something you run is dying — not just that it is
tashan doctor over the config you already have, on your machine

Start a 7-day trial › Everything measured on this page stays free.

Show your score

Measured this well? Put the live badge in your README — it updates as the score does.

[![tashan](https://tashan.sh/badge/pkg-google-tag-manager-mcp-server.svg)](https://tashan.sh/capability/pkg-google-tag-manager-mcp-server.html)

npm ↗ · pkg:google-tag-manager-mcp-server

Already running this? npx tashan-cli doctor checks your whole config against the Index — how it works ›

Measured 2026-08-15 · scorer s5 · how · something wrong here?