Loading the registry…
Google Tag Manager and Google Ads MCP server — manage GTM containers, Google Ads campaigns, budgets, conversions, negative placements, geo targeting, and auto-apply recommendations from AI agents
The publisher performed an authenticated act of publication — proving control of a namespace in the official MCP registry, or appearing in a first-party catalogue an operator curates. That establishes WHO published it. It is not a security finding, and attested artifacts carry Flagged verdicts too.
npm: @ainative/gtm-mcp @ 0.4.2, 0 findings
Choose your runtime: the CLI writes the mcpServers config entry for that target.
nerlo install --target claude-code -- @ainative/gtm-mcp
Install respects the composite badge: Clean proceeds, Caution prompts for confirmation, and Flagged is refused. Write operations require an API token.
8 of 11 scanners examined this package. The rest do not apply to it — language, ecosystem and packaging decide which analyzers can say anything, and a scanner that cannot examine an artifact reports nothing rather than passing it.
v1.4.0
0 findings · 0.6s
v2.0.11
3 findings · 6.6s
v0.3.74
7 findings · 1.3s
v0.2.0
0 findings · 4.0s
v0.2.0
0 findings · 4.0s
v0.1.0
0 findings · 9.8s
v0.71.0
20 findings · 0.2s
v2.3.8
21 findings · 6.6s
vv0.3.2
No Go packages were found in this artifact. What each scanner covers
0 findings · 0.1s
v0.71.0
No container image was published for this artifact. What each scanner covers
0 findings · 0.0s
vv1.6.0
No Go modules were found in this artifact. What each scanner covers
0 findings · 0.1s
2 scans on record. Every scan's full results are retained immutably for 24 months.
| Completed | Composite | Change | Scanners | Status |
|---|---|---|---|---|
| Sep 11, 2026 | Flagged45 | — | agentshield: completecisco-skill-scanner: completeagent-audit-kit: completenerlo-behavioral: completenerlo-install-instruction: completecapslock ·n/a: not applicablenerlo-multi-source: completetrivy: completeosv-scanner: completetrivy_image ·n/a: not applicablegovulncheck ·n/a: not applicable | completed |
| Aug 1, 2026 | Flagged82 | — | agentshield: completecisco-skill-scanner: completeagent-audit-kit: completenerlo-behavioral: completenerlo-install-instruction: completenerlo-multi-source: completetrivy: completeosv-scanner: complete | completed |
Findings in files this artifact installs stand as reported; a model re-read the rest and said which ones it believes are false positives. This is a second opinion published beside the evidence, not a correction to it: the per-scanner reports above are unchanged, every dismissed finding is still listed there at its original severity, and the score and the Flagged badge are computed from those raw severities alone. Nothing below moved them.
Out of 51 findings across every scanner that examined this package.
These findings are in files this artifact installs and are not placeholder values. No false-positive basis can be corroborated for such a finding, so this review never dismisses one; they were not sent to the model and stand at their scanner's severity.
2 AAK-SECRET-004
Files: src/lib/gtm-client.ts · reported by agent-audit-kit
1 AAK-ANTHROPIC-SDK-001
Files: src/index.ts · reported by agent-audit-kit
1 AAK-MCP-018
Files: src/index.ts · reported by agent-audit-kit
1 AAK-OAUTH-3P-001
Files: package.json · reported by agent-audit-kit
1 AAK-SEC-MD-001
Files: SECURITY.md · reported by agent-audit-kit
1 AAK-SUPPLY-005
Files: package-lock.json · reported by agent-audit-kit
1 CVE-2026-18446
Files: package-lock.json · reported by trivy
1 CVE-2026-41907
Files: package-lock.json · reported by trivy
1 CVE-2026-54272
Files: package-lock.json · reported by trivy
1 CVE-2026-69152
Files: package-lock.json · reported by trivy
1 CVE-2026-69192
Files: package-lock.json · reported by trivy
1 CVE-2026-69198
Files: package-lock.json · reported by trivy
1 CVE-2026-69207
Files: package-lock.json · reported by trivy
1 CVE-2026-71429
Files: package-lock.json · reported by trivy
1 CVE-2026-71848
Files: package-lock.json · reported by trivy
1 CVE-2026-71849
Files: package-lock.json · reported by trivy
1 CVE-2026-71850
Files: package-lock.json · reported by trivy
1 CVE-2026-75899
Files: package-lock.json · reported by trivy
1 CVE-2026-75931
Files: package-lock.json · reported by trivy
1 CVE-2026-76172
Files: package-lock.json · reported by trivy
1 CVE-2026-82417
Files: package-lock.json · reported by trivy
1 CVE-2026-82562
Files: package-lock.json · reported by trivy
1 CVE-2026-84363
Files: package-lock.json · reported by trivy
1 CVE-2026-84364
Files: package-lock.json · reported by trivy
1 CVE-2026-84365
Files: package-lock.json · reported by trivy
1 GHSA-22jq-vg5j-6vgg
Files: /repo/package-lock.json · reported by osv-scanner
1 GHSA-4mjr-xmp4-gh2g
Files: /repo/package-lock.json · reported by osv-scanner
1 GHSA-4xrf-jv44-h6hh
Files: /repo/package-lock.json · reported by osv-scanner
1 GHSA-528h-pc64-c93x
Files: /repo/package-lock.json · reported by osv-scanner
1 GHSA-54fx-42gc-7vw4
Files: /repo/package-lock.json · reported by osv-scanner
1 GHSA-5jgf-p345-68v8
Files: /repo/package-lock.json · reported by osv-scanner
1 GHSA-79qm-7rj5-m7r9
Files: /repo/package-lock.json · reported by osv-scanner
1 GHSA-7p8r-x3mc-p8w7
Files: /repo/package-lock.json · reported by osv-scanner
1 GHSA-8j4g-w8fx-2239
Files: /repo/package-lock.json · reported by osv-scanner
1 GHSA-crvj-82cr-hjcx
Files: /repo/package-lock.json · reported by osv-scanner
1 GHSA-f23p-vx2j-j53r
Files: /repo/package-lock.json · reported by osv-scanner
1 GHSA-f65p-4m7j-42xc
Files: /repo/package-lock.json · reported by osv-scanner
1 GHSA-fph4-wmhf-6fwf
Files: /repo/package-lock.json · reported by osv-scanner
1 GHSA-g6gw-c38x-mqfc
Files: /repo/package-lock.json · reported by osv-scanner
1 GHSA-g7r4-m6w7-qqqr
Files: /repo/package-lock.json · reported by osv-scanner
1 GHSA-gqvv-2mrq-wpjv
Files: /repo/package-lock.json · reported by osv-scanner
1 GHSA-jqff-g426-hqxp
Files: /repo/package-lock.json · reported by osv-scanner
1 GHSA-mwp4-54f8-5fhr
Files: /repo/package-lock.json · reported by osv-scanner
1 GHSA-rgw5-rvv9-x895
Files: /repo/package-lock.json · reported by osv-scanner
1 GHSA-w5hq-g745-h8pq
Files: /repo/package-lock.json · reported by osv-scanner
1 GHSA-x5fp-wj9c-mxmx
Files: /repo/package-lock.json · reported by osv-scanner
1 LOW_ANALYZABILITY
Files: /repo · reported by cisco-skill-scanner
1 MANIFEST_MISSING_LICENSE
Files: /repo/SKILL.md · reported by cisco-skill-scanner
1 SOCIAL_ENG_VAGUE_DESCRIPTION
Files: /repo/SKILL.md · reported by cisco-skill-scanner
The model could have called any of these a false positive and did not.
1 CVE-2026-75975
Files: package-lock.json · reported by trivy
Potential credential exposure and numerous supply chain vulnerabilities
The artifact may expose credentials in `src/lib/gtm-client.ts` and utilizes the Anthropic SDK in `src/index.ts`, indicating network egress to an external AI service. Additionally, multiple high-severity vulnerabilities are present in dependencies listed in `package-lock.json`. These findings warrant attention due to the potential for sensitive data exposure and compromise through vulnerable components.
Concern level assessed by the review: High. This is the review's scale, not the registry badge.
Reviewed by gemini-2.5-flash. The model sees the findings, not your code, and cannot change a score.