@cesteral/sa360-mcp

MCPattested
v1.1.0UnknownApache-2.0Updated 2mo agonpmGitHub

Search Ads 360 MCP Server - Reporting and conversion upload via SA360 Reporting API v0 and legacy v2 API

Works in
ClaudeCursorCopilotChatGPTGemini

Inferred from the transports this listing declares (stdio, streamable-http). A client not listed here hasn’t been ruled out — it just isn’t something Forge can confirm.

Attested build
A verified provenance attestation binds this artifact to the listed repository. Nobody has claimed the listing yet — this proves where the code was built, not who stands behind it.
225Downloads/wk
2mo agoLast update
Package
AuthorUnknown
LicenseApache-2.0
Version1.1.0
Sourcenpm+mcp-registry
npm@cesteral/sa360-mcp
GitHubcesteral/mcp-open-advertising
SBOMCycloneDX 1.6 ↓
Trust Status
A
85/100Trusted
✓Listed in Forge index+10/10
✓Identity verified · attested build+20/20
—Ed25519 publish signature+0/5
→ Included automatically when the publisher runs `forge publish`
—Domain verification+0/5
→ Publisher: host /.well-known/forge.json on the package homepage with { "publisher": "<github-login>" }
✓npm Trusted Publishing (Sigstore)+5/5
—npm maintainer match+0/5
→ Publisher: add the verified GitHub login to the npm package's maintainers (npm owner add <login>)
✓CVE scan · clean+30/30
✓Static analysis · clean+20/20
Paste into Claude Code, Cursor, or any AI assistant to fix all gaps
StatusIdentity verified
PublisherUnverified
SignatureUnsigned
Domain—
Provenance✓ Sigstore-verified · 2128234
Dependencies60 resolved · 2 with advisories
Tool surface14 tools · 1 privileged
Security scan⚠ Warnings (2)v1.1.0 · todayHow well does this scan work?
HIGH@opentelemetry/auto-instrumentations-node@0.67.3Prometheus exporter process crash via malformed HTTP request · transitiveHIGH@opentelemetry/sdk-node@0.208.0Prometheus exporter process crash via malformed HTTP request · transitive
EvalsNone
IndexedAug 26, 2026

Verification confirms publisher identity (repo ownership), not code safety. The security scan covers known CVEs and suspicious install scripts.

Tools

14 tools · 1 privileged
Statically extracted from the published packagev1.1.0 · 5h ago

Read out of the source npm actually ships, at scan time. The package was never executed. Tools registered dynamically at runtime, or hidden inside bundled or minified code, can be missed — so this is a floor on the tool surface, not a complete census of it.

sa360_conversion_upload_workflowprivilegedGuide for uploading offline conversions to SA360 via legacy v2 API

Guide for uploading offline conversions to SA360 via legacy v2 API

No input schema was published for this tool.

agencyIdSA360 Agency ID

SA360 Agency ID

No input schema was published for this tool.

advertiserIdSA360 Advertiser ID

SA360 Advertiser ID

No input schema was published for this tool.

sa360_cross_engine_reporting_workflowGuide for unified cross-engine reporting across Google Ads, Microsoft Ads, Yahoo Japan, and Baidu

Guide for unified cross-engine reporting across Google Ads, Microsoft Ads, Yahoo Japan, and Baidu

No input schema was published for this tool.

customerIdSA360 Manager Account Customer ID

SA360 Manager Account Customer ID

No input schema was published for this tool.

cross_platform_campaign_setupMulti-platform campaign setup guide with budget allocation and naming conventions

Multi-platform campaign setup guide with budget allocation and naming conventions

No input schema was published for this tool.

totalBudgetTotal campaign budget (e.g., 50000)

Total campaign budget (e.g., 50000)

No input schema was published for this tool.

objectiveCampaign objective: awareness, consideration, conversion

Campaign objective: awareness, consideration, conversion

No input schema was published for this tool.

cross_platform_performance_comparisonCross-platform performance comparison and budget reallocation guide

Cross-platform performance comparison and budget reallocation guide

No input schema was published for this tool.

dateRangeDate range (e.g., LAST_7_DAYS, LAST_30_DAYS, or custom dates)

Date range (e.g., LAST_7_DAYS, LAST_30_DAYS, or custom dates)

No input schema was published for this tool.

sa360_query_language_workflowGuide for writing SA360 query language queries

Guide for writing SA360 query language queries

No input schema was published for this tool.

sa360_tool_schema_explorationGuide for discovering and understanding SA360 MCP tools, resources, and schemas

Guide for discovering and understanding SA360 MCP tools, resources, and schemas

No input schema was published for this tool.

sa360_troubleshoot_entityDiagnostic workflow for troubleshooting SA360 reporting and conversion issues

Diagnostic workflow for troubleshooting SA360 reporting and conversion issues

No input schema was published for this tool.

issueIssue type: missing-data, conversion-errors, query-errors, account-access

Issue type: missing-data, conversion-errors, query-errors, account-access

No input schema was published for this tool.

14 of 14 tools published a description.

Tool names and descriptions are written by the publisher and shown verbatim as inert text. They are the strings an MCP client passes to a model, so Forge scans them for prompt-injection patterns — any finding appears with the security scan above. “Privileged” is a keyword match on the tool name, not an audit of what the tool does: a benign-sounding name can still do anything.

About

Search Ads 360 MCP Server - Reporting and conversion upload via SA360 Reporting API v0 and legacy v2 API

Keywords
mcpmodel-context-protocoladvertisingsearch-ads-360sa360
Alternatives
Comparing tool surfaces…

Tools exposed

14 tools · 1 privileged · observed by static extraction. A tool surface is what one scan read on one day, not a live capability list.

Linked names open Forge’s index of every entry observed exposing that tool. Browse all indexed tools.

Dependency tree

What one Forge scan resolved from npm metadata on 2026-08-30 — observed resolution, not a publisher declaration.

60 packages resolved · 4 direct · 2 carrying advisories Resolution stops at depth 4 and 60 packages.

The crawl stopped at the 60-package limit. The rest of the tree was never resolved.

36 more resolved packages are not drawn here (display cap: 24). Every dependency carrying an advisory is drawn regardless of the cap. Full inventory (CycloneDX SBOM)

Declared but not resolved

167 declared dependencies never landed in the tree. They are missing from Forge's resolution, not from the package.

+155 more not listed. The counts by reason above cover all of them.

Not followed: peerDependencies. This tree covers runtime dependencies only, so anything those pull in was never resolved.

Topics

Related in search & retrieval