Browse / MCP servers
googleads/google-ads-mcp
No description on GitHub.
- MCP
Not tested.Tested on 2026-10-25. The saved checks do not establish a product verdict.
What we checked
Does it run from the README?Not tested.The run
The saved checks do not establish a current product result.
Does it do what the README says?No claims established. The saved evidence does not establish an answer.Why
We check claims after it’s running.
Which checks were skipped?2 checks skipped.Reasons
Skipped checks count as neither passes nor failures.
README claims: 1 skipped
- Retrieves metadata about a Google Ads API resource type.: Actual MCP call returned Your default credentials were not found (ADC); no credentials are available.
Examples: 1 skipped
- Start the documented MCP server: The README's pipx MCP configuration requires Google Ads credentials; installed package and exercised the server entry point, but no credentials are available.
Is it safe to run?Made outbound connections: yes (hosts not recorded) by google-ads-mcpWhat we saw
Review signals across current setups: connection review.
Repository processes attempted these non-loopback connections; proxies can hide the final hostname. 9 distinct locations. 2 attributed processes.
Reviewed as expected for a test run: attempted writes that failed, so nothing was written.
Full event, path and process lists for each observed setup:
A quiet run is not a safety guarantee.
Is it maintained?Maintained · 47 commits in 90 days · 15 merged PRs in 90 days · 4 open issues · 9 open PRsActivity
actively maintained: last commit 16 days ago; 47 commits and 15 merged PRs in 90 days; 4 open issues, 9 open PRs; 16 of 38 recent threads got a maintainer reply, median first reply 12.7h; latest release 2026-10-09
Independent test, not endorsed by the project.