Is Google/Meta Ads + GA4 MCP safe to use?

Google/Meta Ads + GA4 MCP has an HVTrust score of 54.4/100 (Grade C), ranked #806 of 1325 tracked AI agent projects. This score reflects verifiable supply-chain integrity, transparency, maintenance, and adoption signals.

What is the trust score for Google/Meta Ads + GA4 MCP?

Google/Meta Ads + GA4 MCP scores 54.4/100 on HVTracker's evidence-weighted HVTrust scale. It has 2.5k GitHub stars and is categorized under MCP Servers.

Google/Meta Ads + GA4 MCP

irinabuht12-oss/google-meta-ads-ga4-mcp

Google Ads MCP server + Meta Ads MCP (Facebook Ads MCP) + GA4 + Search Console in one hosted remote MCP for Claude, ChatGPT, Cursor & n8n: 250+ tools, OAuth login, no API keys, approval-gated writes, free. By Ryze AI.

MCP Servers Listed MIT

Is Google/Meta Ads + GA4 MCP safe? Thin or incomplete trust evidence. Review carefully before production use.

OSSF Scorecard 3.8 / 10

Provenance None

Signed commits 6%

Last push yesterday

Compare Google/Meta Ads + GA4 MCP

How does it stack up against its MCP Servers neighbours?

Pick any agent to compare →

Suggest a correction

In detail: Google/Meta Ads + GA4 MCP scores 54.4/100 (Grade C), ranked #806 of 1325 tracked open-source AI agent projects, on evidence coverage C (2 of 5 independent signal types). The public evidence: no package-provenance attestation found; OSSF Scorecard rates its supply-chain practices 3.8/10; 6% of recent commits are signed; last pushed 2026-09-25. Every point is earned from checkable signals — never paid placement. How scoring works →

How Google/Meta Ads + GA4 MCP compares in MCP Servers

#448 OrangePro 54.5 +0.1
#449 MCP Dev Latam 54.4 ±0
#450 Google/Meta Ads + GA4 MCP 54.4 this agent
#451 MCP Abap Abap Adt Api 54.4 ±0
#452 Local FAISS MCP Server 54.4 ±0

Bars show each HVTrust score; the tick marks Google/Meta Ads + GA4 MCP’s 54.4.

Where the 54.4 comes from

HVTrust dimensions vs the MCP Servers average

54.4 / 100 · 100.0% confidence

Google/Meta Ads + GA4 MCP MCP Servers average (775 agents)

Safety / Integrity50% OSSF Scorecard · 30% provenance · 20% signed commits

5.0 / 25

5.3 below avg 10.3

Identity / Provenance60% listing status · 40% build provenance

10.8 / 18

2.6 below avg 13.4

Transparency50% declared license · 50% OSSF Scorecard

11.7 / 17

0.5 below avg 12.2

Maintenance60% last-push freshness · 40% commit activity

16.7 / 20

4.6 above avg 12.1

AdoptionLog-scaled stars · package downloads

8.2 / 20

1.0 above avg 7.2

Quick Trust Read

What Would Improve It

Publish package provenance or release attestations for stronger supply-chain evidence.

Recent Changes

2026-09-24

Rank Moved

Rank rose 14 spots (#820 → #806)

2026-09-23

Mcp Status Changed

Detected MCP server support changed: none → implemented

2026-09-23

Grade Changed

Trust grade D → C

Maintainer Checklist

Raise Scorecard signals Current OSSF Scorecard is 3.8/10. Tighten the weakest checks to improve public safety evidence.

Publish provenance Add package provenance or release attestations so users can verify where shipped artifacts came from.

Increase signed commits Raise the share of verified-signed commits to make maintainer identity and release history easier to trust.

Compare with another agent Get email alerts for Google/Meta Ads + GA4 MCP View MCP Servers Report missing data

72.3

Activity sub-score · out of 100

#450

In MCP Servers

How to read this: HVTrust (0–100) weighs supply-chain signals (provenance, OSSF Scorecard, signed commits, open license) alongside real-world adoption. Grade C reflects the trust score band: A ≥ 80, B ≥ 65, C ≥ 50, D < 50. Evidence coverage C is separate — it grades how many independent signal types back the score (2 of 5), so a high score on thin evidence stays visible. Full methodology →

Rank Trend

2026-08-11 2026-09-26

Activity & Reach

Stars

2.5k

Forks

363

Last Push

2026-09-25

yesterday

Commits (4 wk)

Downloads (7d)

—

HN mentions (30d)

—

Open Issues

Rank Change

▲5

was #811

Analysis

Activity Inputs

72.3 / 100

StarsRepository reach

20.4 / 30

FreshnessLast push recency

24.9 / 25

ActivityRecent commits

15.0 / 25

CommunityFork signal

11.9 / 20

Supply Chain Trust

Package Provenance

None

No package attestations found

OSSF Scorecard

3.8 / 10

OpenSSF Scorecard · scanned Sep 26, 2026

Signed Commits

of last 100 commits verified

Binary-Artifacts 10

Branch-Protection 0

CI-Tests -1

CII-Best-Practices 0

Code-Review 0

Contributors 3

Dangerous-Workflow -1

Dependency-Update-Tool 0

Fuzzing 0

License 10

Maintained 10

Packaging -1

Pinned-Dependencies -1

SAST 0

Security-Policy 0

Signed-Releases -1

Token-Permissions -1

Vulnerabilities 10

Common questions about Google/Meta Ads + GA4 MCP

Public trust evidence for Google/Meta Ads + GA4 MCP is thin: several supply-chain signals are missing or weak. This does not mean the project is unsafe — it means an outside observer cannot easily verify the usual integrity checks. Treat with extra scrutiny.

Does Google/Meta Ads + GA4 MCP publish package provenance?

No published build provenance is currently detected for Google/Meta Ads + GA4 MCP. This is common for open-source projects but means consumers cannot independently verify that the package on the registry matches the GitHub source.

Does Google/Meta Ads + GA4 MCP have an OpenSSF Scorecard?

Google/Meta Ads + GA4 MCP has an OpenSSF Scorecard score of 3.8/10. The Scorecard checks for branch protection, signed releases, dependency updates, fuzzing, code review, and other supply-chain hygiene items. See the full check breakdown on this page.

Is Google/Meta Ads + GA4 MCP actively maintained?

Actively maintained. The repository was pushed to within the last 1 day(s).

What license does Google/Meta Ads + GA4 MCP use?

Google/Meta Ads + GA4 MCP ships under MIT. A declared, OSI-approved license is one of the transparency signals HVTrust scores.

Are Google/Meta Ads + GA4 MCP's commits signed?

5% of the last 100 commits to Google/Meta Ads + GA4 MCP are verified-signed (GPG, SSH, S/MIME, or GitHub's signing flow). Signed commits help confirm that code was authored by who the commit claims.

Not a safety endorsement. HVTracker describes what public signals show, not whether a project is safe for your use case. Run your own security review before adopting in production.

AI agent surface

MCP, providers, tool surface

Scored in HVTrust

These runtime-trust fields — detected from public repo docs and manifests — contribute a bounded adjustment to this project's HVTrust score alongside supply-chain evidence. The exact values each field can add or subtract are documented in the methodology → Compare this surface across every listed agent in the capability matrix →

MCP Server Support

medium confidence

Implemented

Google/Meta Ads + GA4 MCP appears to expose MCP server capabilities.

Detailed evidence is not shown in the public view.

External Service Dependencies

None detected

No clear third-party provider dependency detected.

Credential signal: No explicit API-key/config marker detected.

Tool / Plugin Surface

None detected

No clear plugin system or broad tool surface detected.

Detailed evidence is not shown in the public view.

Package Provenance Drift

N/A

No package source configured

Detailed evidence is not shown in the public view.

MCP signal live
External deps live
Tool / plugin surface live
Package provenance drift live

How this surface has changed

Detected changes to Google/Meta Ads + GA4 MCP's runtime surface and supply-chain posture, from daily public-signal snapshots. A change here means our detectors see something different — a genuinely changed capability, or better evidence of an existing one.

2026-09-23

Mcp Status Changed

Detected MCP server support changed: none → implemented

2026-09-02

Tool Surface Changed

Detected tool/plugin surface changed: extension-based → none

2026-08-29

Activity Resumed

Activity resumed

Maintain Google/Meta Ads + GA4 MCP?

For maintainers

HVTrust scores Google/Meta Ads + GA4 MCP from public signals only — we never contact maintainers first. If a signal is wrong, stale, or missing (provenance you publish, a Scorecard you run, signed releases), tell us and we'll review it. Corrections are public and tracked on GitHub.

Submit a correction → Add the trust badge

Reputation Timeline

Signal history

2026-09-24

Rank Moved

Rank rose 14 spots (#820 → #806)

2026-09-23

Mcp Status Changed

Detected MCP server support changed: none → implemented

2026-09-23

Grade Changed

Trust grade D → C

2026-09-23

Rank Moved

Rank dropped 348 spots (#472 → #820)

2026-09-23

HVTrust Changed

HVTrust up 10.7pts (43.2 → 53.9)

2026-09-22

Newly Listed

First tracked at rank #472

2026-09-21

Removed From Active Tracking

Removed from active tracking

2026-09-19

Rank Moved

Rank rose 25 spots (#843 → #818)

2026-09-16

Rank Moved

Rank rose 52 spots (#887 → #835)

2026-09-12

Rank Moved

Rank dropped 12 spots (#867 → #879)

2026-09-11

Rank Moved

Rank dropped 15 spots (#852 → #867)

2026-09-09

Grade Changed

Trust grade D → C

2026-09-09

Rank Moved

Rank rose 81 spots (#937 → #856)

2026-09-09

HVTrust Changed

HVTrust up 3.0pts (48.8 → 51.8)

2026-09-08

Rank Moved

Rank dropped 17 spots (#920 → #937)

2026-09-07

Rank Moved

Rank dropped 34 spots (#886 → #920)

2026-09-06

Rank Moved

Rank dropped 17 spots (#869 → #886)

2026-09-05

Rank Moved

Rank dropped 46 spots (#823 → #869)

2026-09-04

Rank Moved

Rank dropped 18 spots (#805 → #823)

2026-09-03

Rank Moved

Rank dropped 47 spots (#758 → #805)

2026-09-02

Tool Surface Changed

Detected tool/plugin surface changed: extension-based → none

2026-09-02

Scorecard Added

OSSF Scorecard: 2.9/10

2026-09-02

Rank Moved

Rank rose 463 spots (#1221 → #758)

2026-09-02

HVTrust Changed

HVTrust up 26.0pts (22.2 → 48.2)

2026-09-01

Rank Moved

Rank dropped 28 spots (#1193 → #1221)

2026-08-31

Rank Moved

Rank dropped 19 spots (#1174 → #1193)

2026-08-30

Rank Moved

Rank dropped 16 spots (#1158 → #1174)

2026-08-29

Activity Resumed

Activity resumed

2026-08-29

Rank Moved

Rank rose 119 spots (#1277 → #1158)

2026-08-29

HVTrust Changed

HVTrust up 5.3pts (16.0 → 21.3)

2026-08-29

Activity Score Changed

Activity score up 24pts (32 → 55)

2026-08-26

Rank Moved

Rank dropped 25 spots (#1241 → #1266)

2026-08-16

Rank Moved

Rank dropped 25 spots (#1208 → #1233)

2026-08-10

Newly Listed

First tracked at rank #1203

GitHub →

Embed Badge Badge guide for maintainers →

For maintainers

Markdown:
            [![HVTrust](https://hvtracker.net/badge/google-meta-ads-ga4-mcp.svg)](https://hvtracker.net/agents/google-meta-ads-ga4-mcp)
            
HTML:
            <a href="https://hvtracker.net/agents/google-meta-ads-ga4-mcp"><img src="https://hvtracker.net/badge/google-meta-ads-ga4-mcp.svg" alt="HVTrust"></a>

Other agents in MCP Servers

Data sources
GitHub REST API (repo, commits, stars, forks, license) · OpenSSF Scorecard CLI
Each agent's signals refresh once daily across 6 staggered batches. Methodology v4.3 · Raw JSON