Marketing MCP Server

marketing-mcp npm v1.1.21

Published by an unidentified publisher — no publish provenance and no public repository, so the publisher could not be verified and the source cannot be independently located.

Read-only agency Marketing MCP — Google Ads, GA4, GSC, Meta, Ahrefs

Trust grade
A
94/100
Last scanned get badge →
Trust
A · 94/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
Moderate
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 99 − adoption risk = 94/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 − 1.2 = 99. What the published surface and source actually contain:

PointsWhat was foundCategory
−1.2 Package runs install-time scripts MTC-SUP-010 supply-chain

2. Client adoption risk — 99 − 5 = 94. 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:

PointsAdoption-risk factor
−3 capability blast radius (moderate) — client exposure if the model is manipulated
−2 publisher verification (unlinked) — no provenance/repo link, but the shipped source was fully read

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 2

medium Hardcoded egress to an external endpoint (dist/lib/gemini-image.js)MTC-SRC-003

In the server's implementation (`dist/lib/gemini-image.js:51`): A hardcoded outbound call to a fixed external host inside server code is a classic exfiltration/telemetry channel — especially paired with reads of local data. This is read from the code itself — not from the tool description — so a poisoned server cannot hide it behind honest-looking metadata.

Evidence: { const res = await fetch("https://generativelanguage.googleapis.com/v1beta/interactions", { method: "POST",

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/lib/gemini-image.js

low Package runs install-time scripts (postinstall)MTC-SUP-010

"marketing-mcp" executes postinstall script(s) at install time. An install hook runs at install time; most are routine build/setup, but review what it does before trusting it.

Evidence: node -e "const fs=require('fs');if(fs.existsSync('dist/secrets/postinstall.js')){require('child_process').execSync('node dist/secrets/postinstall.js',{stdio:'in

Fix: Review the scripts; install with --ignore-scripts where possible and vet what they do.

Location: package marketing-mcp

Tools 45

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

  • agency_bulk_readno sensitive capability
  • agency_clear_active_clientno sensitive capability
  • agency_get_active_clientno sensitive capability
  • agency_health_checkno sensitive capability
  • agency_list_clientsno sensitive capability
  • agency_reload_clientsno sensitive capability
  • agency_set_active_clientno sensitive capability
  • ahrefs_api_usageno sensitive capability
  • ahrefs_get_backlinksno sensitive capability
  • ahrefs_get_organic_keywordsno sensitive capability
Show 35 more tools ↓
  • ahrefs_get_top_pagesno sensitive capability
  • ahrefs_keyword_overviewno sensitive capability
  • ahrefs_serp_overviewno sensitive capability
  • ahrefs_site_overviewno sensitive capability
  • auth_reconnect_googleno sensitive capability
  • auth_statusno sensitive capability
  • ga4_get_conversionsno sensitive capability
  • ga4_get_realtimeno sensitive capability
  • ga4_get_top_pagesno sensitive capability
  • ga4_get_traffic_sourcesno sensitive capability
  • ga4_list_propertiesno sensitive capability
  • ga4_run_reportno sensitive capability
  • generate_imageno sensitive capability
  • google_ads_generate_reconnect_linkno sensitive capability
  • google_ads_get_ad_groupsno sensitive capability
  • google_ads_get_campaign_performanceno sensitive capability
  • google_ads_get_campaignsno sensitive capability
  • google_ads_get_keywordsno sensitive capability
  • google_ads_get_pmax_search_term_categoriesno sensitive capability
  • google_ads_get_pmax_search_termsno sensitive capability
  • google_ads_get_pmax_search_terms_reportno sensitive capability
  • google_ads_get_pmax_search_terms_with_costno sensitive capability
  • google_ads_get_search_termsno sensitive capability
  • google_ads_get_shopping_performanceno sensitive capability
  • google_ads_list_accountsno sensitive capability
  • gsc_inspect_urlno sensitive capability
  • gsc_list_sitemapsno sensitive capability
  • gsc_list_sitesno sensitive capability
  • gsc_search_analyticsno sensitive capability
  • meta_get_ad_setsno sensitive capability
  • meta_get_adsno sensitive capability
  • meta_get_campaignsno sensitive capability
  • meta_get_insightsno sensitive capability
  • meta_health_checkno sensitive capability
  • meta_list_ad_accountsno sensitive capability

What this scan could not see

Versions 1

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.1.21 latest A 94/100 2 1.13.0 2026-09-05

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

Use the free API → How scoring works

More in Security & Testing