Samarth Gtm MCP Server

samarth-gtm-mcp npm v1.490.0 Source verified

Published by samarthanalytics-sj — publish provenance cryptographically ties this package to that repository. That is proof of origin, not an official vendor package.

Production-ready MCP server for Google Tag Manager API v2 — Samarth Analytics

Trust grade
A
100/100
Last scanned get badge →
Trust
A · 100/100
Adoption risk for you: the threat score, then adjusted down for blast radius, publisher verification and how much the scan could see. Deterministic; every point is auditable.
Capability
Minimal
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.
Share this Trust Score
𝕏 Share LinkedIn Reddit
A Why this grade threat 100 − adoption risk = 100/100

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 − 0 = 100. 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:

✓ No adoption-risk deductions — minimal blast radius, verified enough, and fully inspected.

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 1

low Shell/command execution in packaging/dev tooling (dist/scripts/auth-google.js)MTC-SRC-002

In a packaging/dev/install script (shipped, but not the server runtime) (`dist/scripts/auth-google.js:26`): 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: ; import { exec } from 'child_process'; import { randomBytes } from 'crypto'; import { DEFAULT_REDIRECT_URI, buildOAuth2

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/scripts/auth-google.js

Tools 94

Each tool and what it can reach — statically extracted from the published source.

  • accounts_getno sensitive capability
  • accounts_listno sensitive capability
  • audit_containerno sensitive capability
  • built_in_variables_disableno sensitive capability
  • built_in_variables_enableno sensitive capability
  • built_in_variables_listno sensitive capability
  • built_in_variables_revertno sensitive capability
  • containers_combineno sensitive capability
  • containers_createno sensitive capability
  • containers_getno sensitive capability
Show 84 more tools ↓
  • containers_listno sensitive capability
  • containers_lookupno sensitive capability
  • containers_move_tag_idno sensitive capability
  • containers_set_tagging_server_urlsno sensitive capability
  • containers_snippetno sensitive capability
  • create_gtm_tracking_tagno sensitive capability
  • create_gtm_variable_typedno sensitive capability
  • destinations_getno sensitive capability
  • destinations_linkno sensitive capability
  • destinations_listno sensitive capability
  • environments_createno sensitive capability
  • environments_deleteno sensitive capability
  • environments_getno sensitive capability
  • environments_listno sensitive capability
  • environments_reauthorizeno sensitive capability
  • environments_updateno sensitive capability
  • export_containerno sensitive capability
  • folders_createno sensitive capability
  • folders_deleteno sensitive capability
  • folders_entitiesno sensitive capability
  • folders_getno sensitive capability
  • folders_listno sensitive capability
  • folders_move_entitiesno sensitive capability
  • folders_updateno sensitive capability
  • ga4_account_summaries_listno sensitive capability
  • ga4_acknowledge_user_data_collectionno sensitive capability
  • ga4_check_compatibilityno sensitive capability
  • ga4_create_propertyno sensitive capability
  • ga4_custom_dimensions_listno sensitive capability
  • ga4_custom_metrics_listno sensitive capability
  • ga4_data_retention_getno sensitive capability
  • ga4_data_streams_listno sensitive capability
  • ga4_delete_accountno sensitive capability
  • ga4_delete_propertyno sensitive capability
  • ga4_enhanced_measurement_getno sensitive capability
  • ga4_google_ads_links_listno sensitive capability
  • ga4_key_events_listno sensitive capability
  • ga4_properties_listno sensitive capability
  • ga4_property_getno sensitive capability
  • ga4_run_realtime_reportno sensitive capability
  • ga4_run_reportno sensitive capability
  • ga4_update_accountno sensitive capability
  • ga4_update_data_retentionno sensitive capability
  • ga4_update_propertyno sensitive capability
  • gtm_type_referenceno sensitive capability
  • tags_add_ga4_event_parametersno sensitive capability
  • tags_createno sensitive capability
  • tags_deleteno sensitive capability
  • tags_getno sensitive capability
  • tags_listno sensitive capability
  • tags_type_profileno sensitive capability
  • tags_updateno sensitive capability
  • templates_describe_fieldsno sensitive capability
  • templates_import_from_galleryno sensitive capability
  • triggers_createno sensitive capability
  • triggers_deleteno sensitive capability
  • triggers_getno sensitive capability
  • triggers_listno sensitive capability
  • triggers_updateno sensitive capability
  • user_permissions_createno sensitive capability
  • user_permissions_deleteno sensitive capability
  • user_permissions_getno sensitive capability
  • user_permissions_listno sensitive capability
  • user_permissions_updateno sensitive capability
  • variables_createno sensitive capability
  • variables_deleteno sensitive capability
  • variables_getno sensitive capability
  • variables_listno sensitive capability
  • variables_updateno sensitive capability
  • versions_createno sensitive capability
  • versions_deleteno sensitive capability
  • versions_getno sensitive capability
  • versions_listno sensitive capability
  • versions_publishno sensitive capability
  • versions_set_latestno sensitive capability
  • versions_undeleteno sensitive capability
  • workspace_create_version_and_publishno sensitive capability
  • workspace_get_statusno sensitive capability
  • workspace_quick_previewno sensitive capability
  • workspace_resolve_conflictno sensitive capability
  • workspace_syncno sensitive capability
  • workspaces_createno sensitive capability
  • workspaces_getno sensitive capability
  • workspaces_listno sensitive capability

What this scan could not see

Versions 10

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
v1.490.0 latest A 100/100 1 1.13.0 2026-09-05
v1.483.0 A 100/100 1 1.13.0 2026-09-01
v1.480.3 A 100/100 1 1.13.0 2026-08-30
v1.473.4 A 100/100 1 1.13.0 2026-08-29
v1.473.3 A 100/100 1 1.12.1 2026-08-12
Show 5 more versions ↓
v1.465.0 A 100/100 1 1.12.1 2026-08-09
v1.463.0 A 100/100 1 1.12.1 2026-08-07
v1.455.0 A 100/100 1 1.12.1 2026-08-06
v1.450.7 A 100/100 1 1.12.1 2026-08-05
v1.448.2 A 100/100 1 1.12.1 2026-08-04

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 · 100/100
Markdown (GitHub README)
[![MCP Trust Score](https://mcptrustchecker.com/registry/samarth-gtm-mcp/badge.svg)](https://mcptrustchecker.com/registry/samarth-gtm-mcp)
HTML
<a href="https://mcptrustchecker.com/registry/samarth-gtm-mcp"><img src="https://mcptrustchecker.com/registry/samarth-gtm-mcp/badge.svg" alt="MCP Trust Score" height="20"></a>
Prefer shields.io styling? Point it at https://mcptrustchecker.com/registry/samarth-gtm-mcp/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 samarth-gtm-mcp --online

Use the free API → How scoring works

More in Analytics & Monitoring