Bot traffic detector for paid ads. Input: domain. Returns trigger, fake sessions, daily USD waste.
The last two health checks of this connector failed. If this server requires authentication, missing or expired test credentials may be the cause. A test profile lets Glama authenticate for health checks and discover tools; it is separate from your personal connections.
If you are the author, claim ownership, then add or update a test profile under Admin → Test Profile.
Scored across 1 tool
Only one tool exists, so there is no possibility of confusing it with another. Its purpose is clearly defined."
The tool name follows a clear verb_noun pattern ('check_ad_traffic'), and with only one tool, consistency is inherently maintained.
A single tool is too few for a server named 'botguard-pro' which implies a broader bot protection service. The lone detection tool feels under-scoped for the apparent purpose.
The server only provides detection of bot traffic and wasted spend. Missing are expected capabilities like blocking traffic, detailed analytics, configuration, or remediation, leaving obvious gaps in the domain.
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
check_ad_trafficGoogle Ads, Meta Ads, GA4, Search Console and Shopify insights, alerts, ROAS rules and ad actions.
Real-device ad verification: malvertising and cloaking scans, AI policies, alerts, webhooks.
Audit a landing page before paid ads: readiness score, ad pixels found, conversion paths, top fixes.
Keyword volume, keyword ideas, domain SEO, Trends volume, AI visibility, Maps rank. Pay per result.
Add one secure layer between your agents and this server.
