gtm-mcp@0.1.0
CAUTION· static onlyPublisher claims: "Enables auditing Google Tag Manager containers, checking GA4 ecommerce event coverage, previewing and applying workspace edits as dry-run diffs, and publishing versions with explicit confirmation. Runs locally over stdio with your own Google OAuth account, enforcing read-only or read/write/publish profiles and client-side rate limiting." Observed in sandbox: static analysis only — behavior not yet observed.
Coverage
Static only; nothing was run yet.The label rests on the code, the instruction files and the publisher. The honeypot run replaces this verdict when it completes.
Before you give it your token
- It will ask for
GOOGLE_CLIENT_SECRETor--client-secretConfiguration, not credentials: GOOGLE_CLIENT_ID- Where it talks to
- no vendor host named in the codeAlso google.com — not the publisher's domain; check what for before connecting.
- What the honeypot saw
- nothing has run yet
- What we could not test
- everything: the server has not run yet
Run it before you trust it. Nothing has run yet: the code was read, the server was not. `vet-skills try` runs this exact version in the honeypot in about a minute.
Never paste a credential into a chat, a ticket or a report, including ours. How the guard holds it.
Is [email protected] safe to install?
KillerSkills analysed it statically (a sandbox run is pending) on 2026-11-11 and scored it 64/100 (Caution). It is not known to be malicious, but it has behaviour or code a security policy should decide on before install. Notable findings: Access to sensitive file paths. Summary: static analysis only — behavior not yet observed.
Behavior trace
Queued for honeypot run · static analysis onlyThis version has not been detonated yet. The score above counts behavior as unknown (50/100), so it cannot read Verified until the honeypot run completes and replaces this verdict.
Static findings
"""Build the gtm-mcp MCPServer: wires auth → rate limiter → http → client → tools."""Fix: Namespace tool names and keep tool descriptions literal; no instructions to the agent inside them."""Static configuration for gtm-mcp (no secrets here — see .env.example)."""Fix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.MCP server Mezbaul-Hasan/GTM-MCP-Server on Glama, built from https://github.com/Mezbaul-Hasan/GTM-MCP-Server.Fix: Namespace tool names and keep tool descriptions literal; no instructions to the agent inside them.Cost to the agent
Tokens estimated at four characters each. Skills load their instruction text when triggered; the figure is what that costs.
Known vulnerabilities
Vulnerability advisories (OSV) cover npm and PyPI packages; this registry has no advisory database.
What would make this Verified
16 points to 80 · weights: behavior 45%, static 25%, prompt 15%, publisher 15%- Unclaimed publisher≈ +8 on the totalClaim mezbaul-hasan: a verified publisher gets +50 on publisher trust. It is free and usually instant with GitHub sign-in.
- Access to sensitive file paths≈ +4 on the totalStop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.
- MCP server using network transport (SSE/HTTP)≈ +2 on the totalNamespace tool names and keep tool descriptions literal; no instructions to the agent inside them.