mcp-gads (pijusz/mcp-gads) is an MCP server listed on the M8ven Trust Index. It scores 74 out of 100, grade C. It declares 41 tools. No publisher has claimed this listing.

C
Emerging
74/100

mcp-gads

Enables querying and managing Google Ads campaigns, keywords, assets, and more via natural language, with support for multiple MCP clients.

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

⚡ Live Monitored: not connected

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

⚡ Connect GitHub → continuous verification on every pushwhy connect →

Who stands behind it

pijusz

Source: 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 →

Install from

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
No credential exfiltration, no sensitive file access, no obfuscation
Static analysis found nothing flowing your secrets to unexpected places.
Open source with a license and README
Anyone can audit the code, the license is declared, and the publisher documents what it does.
🔐
You'll be asked for 1 credential: GOOGLE_ADS_CLIENT_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.
configGOOGLE_ADS_CLIENT_ID
🔐 secretGOOGLE_ADS_CLIENT_SECRET
configGOOGLE_ADS_CREDENTIALS_PATHUse absolute paths for . Codex spawns the server with its own cwd, so relative paths silently miss.
configGOOGLE_ADS_ENABLE_MUTATIONSEnable with =true:
configGOOGLE_ADS_ENV_FILEPath to .env file (loaded if present, never overrides existing env)
// 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

41/41 tools missing one or more hints — list_accounts (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint); get_account_currency (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint); get_account_hierarchy (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint), +38 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.

Tool inputs are validated

30/41 tool handlers declare input schemas (73%)

Declare an inputSchema with zod/joi/yup on every tool definition.

Tool test coverage

Only 0/41 tools referenced in tests (0%)

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

Shell command execution

1 call in production code run through a shell (src/auth/setup.ts:75)

Prefer library functions over shell-outs. If you must shell out, ensure all inputs are properly escaped.

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/pijusz/mcp-gads)](https://m8ven.ai/mcp/pijusz/mcp-gads)
Shows your grade and updates automatically. Prefer no grade? Append ?variant=verified to the badge URL.
commit: 34a00d3ab3c96598b82531d61486342f2119eaa1
code hash: 705053924c91cf69ef0ceff1cae50fc6c96e329aa717300040ce43cc781d0ad8
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