# @cesteral/sa360-mcp

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

- **Type:** MCP server
- **Trust:** 85/100 (A), scored on the package rubric
- **Verification:** verified (build provenance)
- **Version:** 1.1.0
- **Author:** Unknown
- **License:** Apache-2.0
- **npm:** @cesteral/sa360-mcp
- **Endpoints:** streamable-http https://{host}/sa360-mcp/mcp
- **Source:** https://github.com/cesteral/mcp-open-advertising
- **Compatible clients:** claude-code, cursor, copilot, chatgpt, gemini (basis: transport)

## Trust

85/100 (A), scored on the package rubric
- Publisher verified: no
- Build provenance: verified attestation
- npm trusted publishing (OIDC): yes
- Install scripts: nothing suspicious found
- Prompt-injection scan: not run
- Obfuscation scan: not run
- Evidence age: 0 days

## Security scan

- **Status:** warnings
- **Scanned:** 2026-08-30T00:17:18.987Z
- **Version scanned:** 1.1.0
- **CVEs:** none found by OSV at scan time

## Tools

14 declared. Statically extracted from the shipped source — a floor on the surface, not a census.
- `sa360_conversion_upload_workflow` — Guide for uploading offline conversions to SA360 via legacy v2 API
- `agencyId` — SA360 Agency ID
- `advertiserId` — SA360 Advertiser ID
- `sa360_cross_engine_reporting_workflow` — Guide for unified cross-engine reporting across Google Ads, Microsoft Ads, Yahoo Japan, and Baidu
- `customerId` — SA360 Manager Account Customer ID
- `cross_platform_campaign_setup` — Multi-platform campaign setup guide with budget allocation and naming conventions
- `totalBudget` — Total campaign budget (e.g., 50000)
- `objective` — Campaign objective: awareness, consideration, conversion
- `cross_platform_performance_comparison` — Cross-platform performance comparison and budget reallocation guide
- `dateRange` — Date range (e.g., LAST_7_DAYS, LAST_30_DAYS, or custom dates)
- `sa360_query_language_workflow` — Guide for writing SA360 query language queries
- `sa360_tool_schema_exploration` — Guide for discovering and understanding SA360 MCP tools, resources, and schemas
- `sa360_troubleshoot_entity` — Diagnostic workflow for troubleshooting SA360 reporting and conversion issues
- `issue` — Issue type: missing-data, conversion-errors, query-errors, account-access

## Install

**Verdict: install** — No blocking findings and no open coverage gaps — safe to install as configured.
**Config** (claude-code):
```json
"{\n  \"mcpServers\": {\n    \"sa360\": {\n      \"command\": \"npx\",\n      \"args\": [\n        \"-y\",\n        \"@cesteral/sa360-mcp\"\n      ]\n    }\n  }\n}"
```

## Blast radius

Extensive blast radius — mutates data; runs locally and hosted.
- Floor 34, ceiling 58 (tier: extensive)
- This is impact, not likelihood. A high radius is not a defect: a filesystem server is supposed to write files. It is never part of the trust score.

## Machine-readable views of this entry

- Signed JSON: https://forgeregistry.com/api/v1/packages/%40cesteral%2Fsa360-mcp
- Install plan: https://forgeregistry.com/api/v1/packages/%40cesteral%2Fsa360-mcp/install-plan
- Alternatives: https://forgeregistry.com/api/v1/alternatives/%40cesteral%2Fsa360-mcp
- HTML page: https://forgeregistry.com/registry/%40cesteral%2Fsa360-mcp
- MCP: POST https://forgeregistry.com/api/mcp → `forge_get_package` / `forge_install_plan`

## About this document

Generated by Forge (https://forgeregistry.com) — a compact rendering of the same record served, signed, at the JSON URL above. Trust and scan facts are the registry's own measurements; anything Forge did not measure is named as unmeasured rather than omitted.