Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

Google_ads

NPM · @PIPEWORX/MCP-GOOGLE_ADS · 2 COMPONENTS

Google Ads MCP Pack

+3 this week 84 Trust /100

Last scanned (1 hour ago)

Scores higher than 82% of npm servers

Category Marketing and SEO

Trust breakdown (7 categories)

How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score → Why this is hard to score →

Supply Chain Security100
  • No malware found by supply-chain analysis.Pass
  • No known CVEs affecting this package version or its production dependencies.Pass
  • No install/post-install scripts declared.Pass
  • No production dependencies, so there is no dependency health to assess. View diagnostics → Pass
Provenance & Transparency97
  • Source repository is publicly reachable at the declared URL. View diagnostics → Pass
  • Cryptographically verified build provenance (signed, bound to pipeworx-io/mcp-google_ads). View diagnostics → Pass
  • Clear OSI-approved license (MIT).Pass
  • Actively maintained (last published 3 days ago).Pass
  • Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability75
  • AI-judged instruction clarity (good).Pass
  • Tool/resource definitions use about 566 tokens (~113/item across 5 items; 5 tools + 0 resources), lean.Pass
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management23
  • Stability observed for 7 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 100% of tool parameters carry a description.Pass
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 5 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 6 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
  • Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Changelog

Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.

  • 4 Nov 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 17 to 20. That category is still filling its 30-day observation window: 5 days of observed history at the previous scan, 6 at this one. The score rises as the window fills, whether or not the server changes.

  • 3 Nov 26 +15
    • Malware scan: unverified → pass ▲ security
  • 2 Nov 26 −13
    • Malware scan: pass → unverified ▼ security
    • Stability: unverified → 0.13 ▲ functional
    • Package version: 0.2.0 → 0.2.1 functional
  • 30 Oct 26 0
    • Security disclosure: unverified → fail ▼ functional
  • 29 Oct 26 81

    First indexed and scored.

Diagnostics

Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.

Captured 5 Nov 2026 · Analysed npm/@pipeworx/mcp-google_ads@0.2.1

Provenance Verified

A signed build attestation was found and verified, binding this exact artifact to the source repository it claims to come from.

Result Verified
Ecosystem npm
Reason Verified
Discovered via Registry attestation endpoint
Source repo pipeworx-io/mcp-google_ads
Certificate issuer https://token.actions.githubusercontent.com
Certificate SAN https://github.com/pipeworx-io/mcp-google_ads/.github/workflows/publish.yml@refs/heads/main
Rekor log index 3637330640
Predicate type SLSA build provenance https://slsa.dev/provenance/v1
Subject digest sha512:ae0da56f5be78922a80f29da51253cbf10dda893854f12befd57efe9806ec1673be777d38e329208545a1e55e4a0b47dd61528ae223f304e5ac06f4f5

Background: How many MCP packages publish verified provenance →

Dependencies 0 packages
Packages resolved 0
Tree resolution Complete

Background: SBOMs and build attestations, explained →

MCP tools · 5 exposed · ~514 tokens

The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →

Tool Tokens
gads_campaign_metrics ~145

Get performance metrics for campaigns over a date range. Returns impressions, clicks, cost, conversions, CTR, and CPC. Use to analyze campaign effectiveness or compare performance trends.

NameTypeReqDescription
campaign_idstring–Campaign ID to filter (optional, returns all campaigns if omitted)
customer_idstringyesGoogle Ads customer ID
end_datestringyesEnd date in YYYY-MM-DD format (e.g., "2024-01-31")
limitnumber–Maximum number of rows to return (default 50)
start_datestringyesStart date in YYYY-MM-DD format (e.g., "2024-01-01")

No output schema declared.

No examples provided.

gads_get_campaign ~66

Get detailed settings for a specific campaign. Returns name, status, budget, bidding strategy, and configuration. Use to review or audit a campaign's current setup.

NameTypeReqDescription
campaign_idstringyesThe campaign resource ID
customer_idstringyesGoogle Ads customer ID

No output schema declared.

No examples provided.

gads_list_ad_groups ~106

List ad groups within a campaign by campaign ID. Returns ad group names, IDs, statuses, and CPC bids. Use to explore campaign structure or select an ad group for analysis.

NameTypeReqDescription
campaign_idstringyesCampaign ID to list ad groups for
customer_idstringyesGoogle Ads customer ID
limitnumber–Maximum number of ad groups to return (default 50)
statusstring–Filter by ad group status (optional)

No output schema declared.

No examples provided.

gads_list_campaigns ~112

List all campaigns in your Google Ads account. Returns campaign names, IDs, statuses, budgets, and types. Use to overview account structure or find a campaign ID for detailed analysis.

NameTypeReqDescription
customer_idstringyesGoogle Ads customer ID (e.g., "1234567890" or "123-456-7890")
limitnumber–Maximum number of campaigns to return (default 50)
statusstring–Filter by campaign status (optional, returns all if omitted)

No output schema declared.

No examples provided.

gads_search ~85

Run custom GAQL queries against Google Ads data. Use for advanced analysis—filter by keywords, matching types, or aggregate metrics by custom dimensions.

NameTypeReqDescription
customer_idstringyesGoogle Ads customer ID
querystringyesGAQL query string (e.g., "SELECT campaign.name, metrics.clicks FROM campaign WHERE segments.date DURING LAST_7_DAYS")

No output schema declared.

No examples provided.

Install

How do I install the Google_ads MCP server?

Google_ads runs locally as an npm package, launched with npx -y @pipeworx/mcp-google_ads. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

npm · @pipeworx/mcp-google_ads

# add to Claude Code
claude mcp add pipeworx-io-google-ads -- npx -y @pipeworx/mcp-google_ads
Common questions

What is the Google_ads MCP server?

Google_ads is an MCP server listed in the public MCP registry as io.github.pipeworx-io/google_ads. Google Ads MCP Pack. This page covers its npm package (@pipeworx/mcp-google_ads).

Is the Google_ads MCP server safe to use?

Google_ads scores 84 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 5 November 2026. It declares no install or post-install scripts. Its build provenance is signed and verified. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

What tools does the Google_ads MCP server expose?

Google_ads exposes 5 tools: gads_list_campaigns, gads_get_campaign, gads_campaign_metrics, gads_list_ad_groups, gads_search. Their descriptions and schemas cost roughly 514 tokens of context every time the server is loaded.

Is the Google_ads MCP server still maintained?

Google_ads is still listed as active in the MCP registry. We last reached this channel on 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

What licence is the Google_ads MCP server under?

Google_ads declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.