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.

io.github.Synter-Media-AI/synter-ads

NPM · @SYNTERAI/MCP-SERVER · 2 COMPONENTS

One MCP for 30+ ad platforms. Build reports from Claude, ChatGPT or Cursor. Free to read.

−9 this week 77 Trust /100

Last scanned (18 hours ago)

Scores higher than 56% of npm servers

Category Marketing and SEO

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 Security80
  • No malware found by supply-chain analysis.Pass
  • CVE check failed: a known high-severity CVE affects @modelcontextprotocol/sdk 0.6.1, a direct dependency. A fixed version is available. View diagnostics → Fail
  • No install/post-install scripts declared.Pass
  • 7 of 14 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency45
Schema Quality & AI Usability82
  • 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
  • AI-judged instruction clarity (good).Pass
  • Context-footprint check failed: tool/resource definitions use about 6451 tokens (~107/item across 60 items; 56 tools + 4 resources), over budget; trim descriptions and params. See how to fix → Fail
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management100
  • No destabilizing schema changes in the last 30 days.Pass
Tool Coverage100
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 100% of tool parameters carry a description.Pass
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • All 3 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation.Pass
  • An AI judge read all 57 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities20
  • Spec-recency check failed: implements MCP spec 2024-11-05; the latest is 2026-07-28. See how to fix → Fail
What we tested

Checks we ran (16)

  • Malware scan
  • Known CVEs
  • Install scripts
  • Dependency health
  • Source repository
  • Provenance
  • License
  • Maintenance
  • Security disclosure
  • Schema quality
  • Stability
  • Tool coverage
  • Injection markers
  • Destructive annotations
  • Judged manipulation
  • MCP protocol

Does not apply to this package (2)

  • Endpoint SecurityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.
  • Transport & ReachabilityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.

The score does not measure everything. What the score does not measure →

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 Nov 26 +1
    • Stability: 0.97 → pass security
  • 19 Nov 26 −1
    • Stability: pass → 0.97 functional
  • 18 Nov 26 +15
    • Malware scan: unverified → pass ▲ security
  • 17 Nov 26 −24
    • CVE-2026-111769 affects this package: high ▼ security
    • CVE-2025-66414 affects this package: high ▼ security
    • CVE-2023-54404 affects this package: high ▼ security
    • Malware scan: pass → unverified ▼ security
    • Known CVEs: pass → fail ▼ security
    • Schema quality: 3570 → 6451 ▼ functional
    • MCP protocol: pass → fail ▼ functional
    • Destructive annotations: pass → 100 functional
    • Package version: 1.4.0 → 1.4.6 functional
  • 13 Nov 26 +1
    • Stability: 0.97 → pass security
  • 11 Nov 26 +1

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

  • 9 Nov 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.

  • 8 Nov 26 0
    • Security disclosure: unverified → fail ▼ 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 21 Nov 2026 · Analysed npm/@synterai/mcp-server@1.4.6

Provenance No attestation

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

Result No attestation
Ecosystem npm

Background: How many MCP packages publish verified provenance →

Vulnerabilities 3 findings
ID CVE Severity Vector Fix available
GHSA-6prh-2h8m-c8cw CVE-2026-111769 medium CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:L/A:N yes
GHSA-w48q-cv73-mx4w CVE-2025-66414 high yes
GHSA-mrhx-c7xc-m3w5 CVE-2023-54404 high CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H yes

Background: What a vulnerability scan can and cannot prove →

Dependencies 14 packages
Packages resolved 14
Stale 7
Tree resolution Complete

Background: SBOMs and build attestations, explained →

MCP tools · 56 exposed · ~6,297 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
sync_audience ~503

Upload an audience to an ad platform (Google, Meta, LinkedIn, Microsoft, Reddit, TikTok, X, StackAdapt). Accepts inline hashed identifiers (hashed_emails, hashed_phones), raw mobile_ids (IDFA/GAID), company_domains, a public csv_url, or *_artifact_id references staged via stage_audience_artifact. Costs 10 credits on success.

NameTypeReqDescription
account_idstring–Platform ad account id. Optional — defaults to the user's primary account on that platform.
audience_namestring–Name for the audience as it should appear in the platform's UI.
company_domainsstring–Comma-separated company domains for B2B account targeting (Google + LinkedIn).
csv_urlstring–Public CSV URL with audience identifiers. Alternative to inline params / artifact ids.
customer_file_sourcestring–Meta only: USER_PROVIDED_ONLY (default), PARTNER_PROVIDED_ONLY, or BOTH_USER_AND_PARTNER_PROVIDED.
hashed_emailsstring–Comma-separated SHA-256 hashed emails (lowercase hex). For small batches; use hashed_emails_artifact_id for >500.
hashed_emails_artifact_idstring–Artifact id from stage_audience_artifact for SHA-256 hashed emails.
hashed_phonesstring–Comma-separated SHA-256 hashed phones (E.164 format pre-hash). For small batches.
hashed_phones_artifact_idstring–Artifact id from stage_audience_artifact for SHA-256 hashed phones. Meta + most platforms; not supported by Google's customer match script today.
i_have_consentboolean–Confirm the customer has lawful basis (GDPR Art. 6) and required consent under CCPA / Meta Custom Audience Terms / Google Customer Match Policy for every identifier in this audience. Soft-launch: omi…
mobile_idsstring–Comma-separated raw mobile advertising IDs (IDFA / GAID, uppercase UUID). Meta and TikTok only. NOT hashed.
mobile_ids_artifact_idstring–Artifact id for raw mobile ids. Meta only.
platformstringyesAd platform to upload to.

No output schema declared.

No examples provided.

update_campaign_budget ~141

Update the daily budget for a campaign across all 16 connected ad platforms. Supports `dry_run: true` ($0.00 / 0 credits, zero credentials required). Live execution passes the server-side Agent Shield safety gate (daily spend ceiling, max 2x budget-change multiplier, approval mode, and immutable audit log).

NameTypeReqDescription
campaign_idstringyesCampaign ID
daily_budgetnumberyesNew daily budget in USD
dry_runboolean–Preview the budget update and spend-cap check without modifying live ad spend ($0.00 / 0 credits; works with zero credentials).
platformstringyesAd platform

No output schema declared.

No examples provided.

upload_image ~58

Upload an image as an asset for use in ads.

NameTypeReqDescription
asset_namestringyesName for the asset
image_urlstringyesURL of the image to upload
platformstring–Target platform (default: google)

No output schema declared.

No examples provided.

user_budget_pacing_report ~74

Return a deterministic per-user/trader budget ownership and pacing snapshot from saved workspace assignments (target budget, actual spend, expected spend, projected spend, variance, and pacing status). Free read-only tool ($0.00 / 0 credits).

NameTypeReqDescription
include_archivedboolean–Include archived assignments in the snapshot.

No output schema declared.

No examples provided.

validate_organic_post ~40

Validate an organic social post draft against platform character limits, media requirements, and content policies.

NameTypeReqDescription
post_idstringyesOrganic post draft ID

No output schema declared.

No examples provided.

verify_angstrom_claim ~57

Verify advertising claims, budget shifts, or campaign targets against Synter Ångström deterministic ground-truth verification model. Free claim verification tool.

NameTypeReqDescription
claimstringyesCampaign optimization claim, targeting rule, or creative copy to verify

No output schema declared.

No examples provided.

Install

How do I install the io.github.Synter-Media-AI/synter-ads MCP server?

io.github.Synter-Media-AI/synter-ads runs locally as an npm package, launched with npx -y @synterai/mcp-server. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

npm · @synterai/mcp-server

# add to Claude Code
claude mcp add synter-media-ai-synter-ads -- npx -y @synterai/mcp-server
Common questions

What is the io.github.Synter-Media-AI/synter-ads MCP server?

io.github.Synter-Media-AI/synter-ads is an MCP server listed in the public MCP registry as io.github.Synter-Media-AI/synter-ads. One MCP for 30+ ad platforms. Build reports from Claude, ChatGPT or Cursor. Free to read. This page covers its npm package (@synterai/mcp-server).

Is the io.github.Synter-Media-AI/synter-ads MCP server safe to use?

io.github.Synter-Media-AI/synter-ads scores 77 out of 100 on VerifyMCP. We recorded 3 known advisories against it as of 21 November 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 io.github.Synter-Media-AI/synter-ads MCP server expose?

io.github.Synter-Media-AI/synter-ads exposes 56 tools: list_campaigns, create_search_campaign, create_display_campaign, create_pmax_campaign, pause_campaign, and 51 more. Their descriptions and schemas cost roughly 6,297 tokens of context every time the server is loaded.

Is the io.github.Synter-Media-AI/synter-ads MCP server still maintained?

io.github.Synter-Media-AI/synter-ads is still listed as active in the MCP registry. We last reached this channel on 21 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

What licence is the io.github.Synter-Media-AI/synter-ads MCP server under?

io.github.Synter-Media-AI/synter-ads declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.

What did VerifyMCP test on the io.github.Synter-Media-AI/synter-ads MCP server?

VerifyMCP ran 16 checks on io.github.Synter-Media-AI/synter-ads, covering Malware scan, Known CVEs, Install scripts, Dependency health and 12 more. Endpoint Security and Transport & Reachability do not apply to an npm package, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.