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.

Unified Ad Intelligence

PYPI · UNIFIED-AD-INTELLIGENCE-MCP · 2 COMPONENTS · SCANNED SEP 20

Cross-platform ad spend, attribution, true ROAS, budget, and anomaly intelligence.

−14 this week 55 Trust /100
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 Security50
  • Malware scan not yet available for this package.Unverified
  • No known CVEs affecting this package version or its production dependencies.Pass
  • No install/post-install scripts declared.Pass
  • 1 of 23 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency6
Schema Quality & AI Usability61
  • AI-judged instruction clarity (fair).Partial
  • Tool/resource definitions use about 287 tokens (~28/item across 10 items; 10 tools + 0 resources), lean.Pass
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management87
  • Stability observed for 26 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage66
  • 90% of tools have a non-trivial description (not blank, and not just the tool's name).Partial
  • 0% of tool parameters carry a description.Fail
  • Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 10 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 10 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
  • Implements a current MCP spec version (2026-07-28).Pass
Install

How do I install the Unified Ad Intelligence MCP server?

Unified Ad Intelligence runs locally as a PyPI package, launched with uvx unified-ad-intelligence-mcp. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

pypi · unified-ad-intelligence-mcp

# add to Claude Code
claude mcp add atul0016-unified-ad-intelligence -- uvx unified-ad-intelligence-mcp
// .cursor/mcp.json
{
  "mcpServers": {
    "atul0016-unified-ad-intelligence": {
      "command": "uvx",
      "args": [
        "unified-ad-intelligence-mcp"
      ]
    }
  }
}
// .vscode/mcp.json
{
  "servers": {
    "atul0016-unified-ad-intelligence": {
      "command": "uvx",
      "args": [
        "unified-ad-intelligence-mcp"
      ]
    }
  }
}
# add to Codex CLI
codex mcp add atul0016-unified-ad-intelligence -- uvx unified-ad-intelligence-mcp
// opencode.json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "atul0016-unified-ad-intelligence": {
      "type": "local",
      "command": [
        "uvx",
        "unified-ad-intelligence-mcp"
      ],
      "enabled": true
    }
  }
}
# add to OpenClaw
openclaw mcp add atul0016-unified-ad-intelligence --command uvx --arg unified-ad-intelligence-mcp
# ~/.hermes/config.yaml
mcp_servers:
  atul0016-unified-ad-intelligence:
    command: "uvx"
    args: ["unified-ad-intelligence-mcp"]
// ~/.netclaw/config/netclaw.json
{
  "McpServers": {
    "atul0016-unified-ad-intelligence": {
      "Transport": "stdio",
      "Command": "uvx",
      "Arguments": [
        "unified-ad-intelligence-mcp"
      ]
    }
  }
}
# add to Vellum
assistant mcp add atul0016-unified-ad-intelligence -t stdio -c uvx -a unified-ad-intelligence-mcp
// mcp.json
{
  "mcpServers": {
    "atul0016-unified-ad-intelligence": {
      "command": "uvx",
      "args": [
        "unified-ad-intelligence-mcp"
      ]
    }
  }
}
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.

  • 20 Sept 26 +1

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

  • 19 Sept 26 −2
    • Stability: pass → 0.83 functional
  • 18 Sept 26 0
    • Stability: 0.97 → pass security
  • 17 Sept 26 +1

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

  • 14 Sept 26 −14
    • Malware scan: pass → unverified security
  • 13 Sept 26 +15
    • Malware scan: unverified → pass security
  • 12 Sept 26 +1

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

  • 11 Sept 26 −3
    • Stability: pass → 0.77 functional
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 20 Sept 2026 · Analysed pypi/unified-ad-intelligence-mcp@0.1.1

Provenance No attestation

The registry publishes no build provenance for this version, so there is nothing to verify.

Result No attestation
Ecosystem pypi

Background: How many MCP packages publish verified provenance →

Dependencies 23 packages
Packages resolved 23
Stale 1
Tree resolution Complete

Background: SBOMs and build attestations, explained →

MCP tools · 10 exposed · ~287 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
detect_campaign_anomalies ~34

Detect spend spikes, CPA jumps, conversion drops, and tracking outages.

NameTypeReqDescription
lookback_daysinteger

Structured output declared, but exposes no named fields.

No examples provided.

get_budget_recommendation ~36

Recommend budget shifts using marginal ROAS and confidence.

NameTypeReqDescription
goalstring
total_budgetnumberyes

Structured output declared, but exposes no named fields.

No examples provided.

get_cross_platform_summary ~40

Summarize spend, attributed revenue, true revenue, and duplication risk across platforms.

NameTypeReqDescription
date_rangestring
platforms

Structured output declared, but exposes no named fields.

No examples provided.

get_license_status ~27

Return payment/license readiness for AtulHritik-Mcp-Suite without exposing secrets.

Input schema present but exposes no named parameters.

Structured output declared, but exposes no named fields.

No examples provided.

get_live_connector_status ~21

Return Meta and Google Ads connector readiness without exposing secrets.

Input schema present but exposes no named parameters.

Structured output declared, but exposes no named fields.

No examples provided.

get_new_vs_returning_roas ~37

Split acquisition quality by new and returning customers.

NameTypeReqDescription
date_rangestring
platformstringyes

Structured output declared, but exposes no named fields.

No examples provided.

get_true_roas ~47

Compare platform-reported ROAS against deduplicated revenue truth.

NameTypeReqDescription
date_rangestring
platform_astringyes
platform_bstringyes

Structured output declared, but exposes no named fields.

No examples provided.

health ~4

No description provided.

Input schema present but exposes no named parameters.

Structured output declared, but exposes no named fields.

No examples provided.

test_google_ads_connection ~20

Run a read-only Google Ads API smoke check.

Input schema present but exposes no named parameters.

Structured output declared, but exposes no named fields.

No examples provided.

test_meta_marketing_connection ~21

Run a read-only Meta Marketing API smoke check.

Input schema present but exposes no named parameters.

Structured output declared, but exposes no named fields.

No examples provided.

Common questions

What is the Unified Ad Intelligence MCP server?

Unified Ad Intelligence is an MCP server listed in the public MCP registry as io.github.atul0016/unified-ad-intelligence. Cross-platform ad spend, attribution, true ROAS, budget, and anomaly intelligence. This page covers its PyPI package (unified-ad-intelligence-mcp).

Is the Unified Ad Intelligence MCP server safe to use?

Unified Ad Intelligence scores 55 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 20 September 2026. It declares no install or post-install scripts. 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 Unified Ad Intelligence MCP server expose?

Unified Ad Intelligence exposes 10 tools: health, get_license_status, get_live_connector_status, test_meta_marketing_connection, test_google_ads_connection, and 5 more. Their descriptions and schemas cost roughly 287 tokens of context every time the server is loaded.

Is the Unified Ad Intelligence MCP server still maintained?

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