samarth-gtm-mcp (samarthanalytics-sj/samarth-analytics-mcp) is an MCP server listed on the M8ven Trust Index. It scores 74 out of 100, grade C. It declares 91 tools. No publisher has claimed this listing.

Emerging

74/100

23 days ago

samarth-gtm-mcp

Item: samarth-gtm-mcp
Rating: 74
Author: M8ven

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

→ samarthanalytics-sj/samarth-analytics-mcp· npm: samarth-gtm-mcp· listed on npm

Emerging. No concerning findings. Grades remain capped until the project builds reputation through adoption. Grades reflect the full trust pyramid: code, verification depth, and reputation. New projects cap at C until adoption is earned.

How we verified

Code Verified⚡ Live Monitored: not connected

Verified is a snapshot. Live keeps it current, and builds your track record.

⚡ Connect GitHub → continuous verification on every push why connect →

Who stands behind it

samarthanalytics-sj

Source: npm · also listed on Glama

Is this your MCP?

Claim it to get a verified publisher badge, a free copy of our full audit findings, and direct contact for any high-priority issues we find. Or connect your repo for our deepest verification, Live Monitored: read-only, revoke anytime. What we access →

⚡ Connect GitHub for Live Monitored

Install from

npmscored separately Glamanot scored here

The grade above is for the source repository. Registries can serve a different version, so we mark the ones we were not able to read.

// key findings

🚨

Secret credentials may flow to a network call

1 flow detected: STYTCH_SECRET. We can’t prove the destination matches the brand the credential belongs to.

🔐

You'll be asked for 6 credentials: GOOGLE_CLIENT_SECRET, GOOGLE_OAUTH_CLIENT_SECRET, GTM_MCP_HTTP_AUTH_TOKEN, SAMARTH_GOOGLE_OAUTH_CLIENT_SECRET, STYTCH_PUBLIC_TOKEN, STYTCH_SECRET

These are read from process.env at runtime. Make sure you trust where they’ll be sent.

// environment variables

To run this server yourself, you supply these values. They go in your own MCP client configuration and stay on your machine. The secret label means the value is sensitive, not that the server mishandles it.

configAUTHORIZE_UI_DIR

configDRY_RUNfalse Simulate all writes without calling the API

configGA4_MCP_ENABLE_DELETES

configGA4_MCP_ENABLE_WRITES

configGOOGLE_CLIENT_IDEdit .env — at minimum add and GOOGLE_CLIENT_SECRET

🔐 secretGOOGLE_CLIENT_SECRETEdit .env — at minimum add GOOGLE_CLIENT_ID and

configGOOGLE_OAUTH_CLIENT_ID... GOOGLE_OAUTH_CLIENT_SECRET=... npx -y -p samarth-gtm-mcp samarth-gtm-auth

🔐 secretGOOGLE_OAUTH_CLIENT_SECRETGOOGLE_OAUTH_CLIENT_ID=... =... npx -y -p samarth-gtm-mcp samarth-gtm-auth

configGOOGLE_OAUTH_REDIRECT_URI

configGOOGLE_REDIRECT_URIGOOGLE_OAUTH_REDIRECT_URI http://localhost:3001/oauth/callback OAuth redirect URI. Falls back to .

configGOOGLE_SERVICE_ACCOUNT_KEY_FILE4. Set =/path/to/key.json in .env

configGTM_MCP_ENABLE_DELETESfalse Allow delete operations

configGTM_MCP_ENABLE_PUBLISHfalse Allow publish operations

configGTM_MCP_ENABLE_WRITESfalse Allow create/update operations

🔐 secretGTM_MCP_HTTP_AUTH_TOKENBearer token gating /mcp (http transport). Required before exposing the server beyond localhost; unset = open + startup warning.

configGTM_MCP_HTTP_PORT3001 HTTP server port (http transport only; falls back to PORT)

configGTM_MCP_PUBLIC_URL

configGTM_MCP_TOKEN_FILEIt boots a local callback server, opens the consent screen, and writes tokens to ./.gtm-mcp-tokens.json (gitignored, 0600). The token file path is configurable via .

configGTM_MCP_TRANSPORTstdio Transport: stdio or http

configSAMARTH_GOOGLE_OAUTH_CLIENT_IDpublic-client-id

🔐 secretSAMARTH_GOOGLE_OAUTH_CLIENT_SECRETsecret-injected-from-secret-manager

configSTYTCH_API_BASE

configSTYTCH_DEBUG_CLAIMS

configSTYTCH_JWKS_URL

configSTYTCH_JWT_AUDIENCE

configSTYTCH_JWT_ISSUER

configSTYTCH_PROJECT_ID

🔐 secretSTYTCH_PUBLIC_TOKEN

configSTYTCH_REGISTRATION_ENDPOINT

🔐 secretSTYTCH_SECRET

configSTYTCH_TOKEN_ENDPOINT

Deployment configuration, supplied by whoever hosts the server. Users are not asked for these.

deployPORT

// quality suggestions

Tool annotations

No tools have read-only/destructive annotations

Add readOnlyHint or destructiveHint annotations to every tool so hosts can warn users before invoking.

All four hints declared on every tool

91/91 tools missing one or more hints — templates_import_from_gallery (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint); accounts_list (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint); accounts_get (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint), +88 more. OpenAI's directory rejects tools where any of the four hints are missing or non-boolean.

For every tool, set all four hints (readOnlyHint, destructiveHint, idempotentHint, openWorldHint) to explicit true/false values that match the handler’s actual behaviour.

License file

No license file

Add a LICENSE file (MIT, Apache-2.0, etc.).

Tool test coverage

38/91 tools referenced in tests (42%)

Write tests that reference each tool by name so every tool has at least one test.

Secrets not logged

3 secret values sent to console.log

Redact or omit secret values from log output.

Claim the listing to review these findings one by one and send us a correction where you disagree, straight to the team. Claiming also means we tell you when the grade moves, and reach you first if we find anything urgent.

// full audit trail

The findings above are the summary. The full trail, every check we ran, each deduction, the network hosts observed and the dependency advisories, goes to verified publishers, along with an alert whenever a new one lands. Verified publishers can also review each finding and dispute it in one click. Publisher corrections have sharpened several of our checks this month, because the maintainer knows the codebase better than any scanner.

// improvement guidance — verified publishers only

We have 5 concrete improvements we can share with the publisher of this MCP. Each comes with specific guidance to raise the trust score.

// embed badge in your README

[![M8ven Score](https://m8ven.ai/badge/mcp/samarthanalytics-sj/samarth-analytics-mcp)](https://m8ven.ai/mcp/samarthanalytics-sj/samarth-analytics-mcp)

Shows your grade and updates automatically. Prefer no grade? Append ?variant=verified to the badge URL.

commit: af416a86628e9671455678d12cb61046aaf2195e

code hash: b3a8fbc2ae98f7fbc6655561fc6b04db3f42afa8ba2792340b6f83b2394fd182

verified: 8/19/2026, 1:50:13 PM

view raw JSON →

Check MCPs from inside your assistant

Tool Check · MCP

Vetting this one by hand? Tool Check is an MCP that scores other MCPs. Add it once and ask Claude, ChatGPT, or any MCP client to grade a server, surface CVEs, check the publisher, and suggest safer alternatives — before you install.

https://m8ven.ai/api/mcp/tool-check

check_toolsearch_toolscompare_toolsrecommend_alternativescheck_publisherreport_concern

How to add it →Free · no account needed · works in any MCP client