# @cesteral/dbm-mcp

DBM MCP Server - Generic cross-platform reporting and metrics

- **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/dbm-mcp
- **Endpoints:** streamable-http https://{host}/dbm-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-29T21:42:48.096Z
- **Version scanned:** 1.1.0
- **CVEs:** none found by OSV at scan time

## Tools

17 declared. Statically extracted from the shipped source — a floor on the surface, not a census.
- `cross_platform_campaign_setup` — Guide for setting up a coordinated multi-platform campaign across DV360 (dv360-mcp), The Trade Desk (ttd-mcp), Google Ads (gads-mcp), Meta Ads (meta-mcp), Linke
- `totalBudget` — Total campaign budget across all platforms (e.g., '50000' for $50,000)
- `objective` — Campaign objective: 'awareness', 'consideration', or 'conversion' (default: conversion)
- `cross_platform_performance_comparison` — Guide for comparing campaign performance across DV360 (via dbm-mcp), The Trade Desk (ttd-mcp), Google Ads (gads-mcp), and Meta Ads (meta-mcp). Normalizes metric
- `dateRange` — Date range for comparison (e.g., LAST_7_DAYS, LAST_30_DAYS, or custom YYYY-MM-DD format)
- `custom_query_workflow` — Step-by-step guide for building custom Bid Manager queries with the dbm_run_custom_query tool
- `advertiserId` — DV360 Advertiser ID to query
- `queryGoal` — What you want to analyze (e.g., 'campaign performance', 'device breakdown', 'video metrics')
- `pacing_performance_analysis_workflow` — Step-by-step guide for DV360 pacing assessment and performance deep-dive: check delivery pacing, analyze CPM/CTR/CPA/ROAS, identify historical trends, and recom
- `campaignId` — DV360 Campaign ID to analyze
- `focus` — Analysis focus: 'pacing', 'performance', or 'both' (default: both)
- `dbm_run_custom_query_async` — Execute a custom Bid Manager API query asynchronously. Returns a task handle immediately —
- `tool_schema_exploration_workflow` — Step-by-step workflow for exploring available MCP tools, prompts, and resources with minimal context usage.
- `serverFocus` — Server to focus on: dbm-mcp, dv360-mcp, or both (default: both)
- `troubleshoot_report` — Diagnostic workflow for debugging failed Bid Manager queries and common issues
- `errorMessage` — The error message from the failed query
- `queryType` — Type of query that failed (e.g., 'dbm_run_custom_query', 'dbm_get_campaign_delivery')

## Install

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

## Blast radius

Contained to extensive — no credential declaration found, from the publisher, the upstream registry, or the README. Known so far: runs locally and hosted; read-only tool surface.
- Floor 17, ceiling 35 (tier: unknown)
- `unknown` means the floor and ceiling land in different bands — not measured enough to name one. It does not mean low.
- 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%2Fdbm-mcp
- Install plan: https://forgeregistry.com/api/v1/packages/%40cesteral%2Fdbm-mcp/install-plan
- Alternatives: https://forgeregistry.com/api/v1/alternatives/%40cesteral%2Fdbm-mcp
- HTML page: https://forgeregistry.com/registry/%40cesteral%2Fdbm-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.