Meta & Google Ads Connector (benheis/ads-mcp-connector) is an MCP server listed on the M8ven Trust Index. M8ven has not graded it: there is no public source to read and no endpoint we can reach, so there is nothing for us to inspect. No publisher has claimed this listing.

C
Limited view
71/100
2 months ago

Meta & Google Ads Connector

MCP server connecting to Meta Ads and Google Ads APIs to retrieve campaign performance metrics and audience insights.

Limited view. Automated analysis covers part of this stack. Findings reflect what we verified. Grades reflect the full trust pyramid: code, verification depth, and reputation. New projects cap at C until adoption is earned.

Limited view: static analysis for Python is partially covered.

How we verified

Code 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

benheis

Source: PulseMCP

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

M8ven verifies MCPs across every public registry — install directly from whichever one you prefer.

// key findings
No credential exfiltration, no sensitive file access, no obfuscation
Static analysis found nothing flowing your secrets to unexpected places.
🔐
You'll be asked for 4 credentials: GOOGLE_DEVELOPER_TOKEN, GOOGLE_CLIENT_SECRET, GOOGLE_REFRESH_TOKEN, META_ACCESS_TOKEN
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_CUSTOMER_ID
configGOOGLE_LOGIN_CUSTOMER_ID
🔐 secretGOOGLE_DEVELOPER_TOKEN
configGOOGLE_CLIENT_ID
🔐 secretGOOGLE_CLIENT_SECRET
🔐 secretGOOGLE_REFRESH_TOKEN
configGOOGLE_SHEETS_CREDENTIALS_PATH/path/to/your-service-account-key.json
🔐 secretMETA_ACCESS_TOKEN
configMETA_AD_ACCOUNT_ID
// 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

38/38 tools missing one or more hints — check_connection (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint); exchange_meta_token (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint); write_env_vars (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint), +35 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.

License file

No license file

Add a LICENSE file (MIT, Apache-2.0, etc.).

Tests exist

No test files found

Add tests that exercise each declared tool.

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 4 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/benheis-ads-mcp-connector-keb07j)](https://m8ven.ai/mcp/benheis-ads-mcp-connector-keb07j)
Shows your grade and updates automatically. Prefer no grade? Append ?variant=verified to the badge URL.
commit: 60b974dc4201fb62f23bdbfe201fc51693dcf52e
code hash: 44be4704f417eb7a6e3b94d47ec62c903373f800a5178f74b541b43839ff9f48
verified: 6/16/2026, 1:01:30 PM
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