com.7275/adwhiz — Watchlist

MCP100 Assessment

Watchlist / Tracking

Why we’re tracking it

Track identity, package activity, privileges, documentation and data handling

Reviewed Oct 10, 2026 · Documentation review; complete setup workflow not independently tested

Best fit

DEXUN AdWhiz analytics and recommendations

What we know

Read ad accounts, recommendations, usage and savings insights; documented current version is read-only. Read-only MCP access to your DEXUN AdWhiz account: ad accounts, AI recommendations, savings.

Maintenance / activity evidence

117 downloads from 2026-09-09 through 2026-10-08

Tracking evidence observed Oct 10, 2026. These dated signals do not establish current maintenance. Reviewed enrichment confidence: medium_identity_and_metrics; published-function claims not execution verified.

Verification gaps / watch-outs

Installation and comprehensive security have not been independently audited.
Ad-account data needs user API key; future budget-changing features are not in current documented tool scope. Complete write authority is not verified.
See package authentication documentation; not independently tested.
Ad-account data needs user API key; future budget-changing features are not in current documented tool scope.

Ad-account data needs user API key; future budget-changing features are not in current documented tool scope.
Public listing does not imply a safe runtime or security audit.

Full authority, access and evidence limits are available in Review context and Access & risk.

Popularity

· 117 package downloads / 30 days

Downloads observed Oct 10, 2026.

Exact npm package @dexun/adwhiz-mcp; provider interval 2026-09-09–2026-10-08 (inclusive); observed 2026-10-10T17:26:34Z.

All limitations / Review context

Have @dexun/adwhiz-mcp permissions, hosted data retention, publication identity or supported MCP operations changed?

Bounded public tracking review; known consequences disclosed: Ad-account data needs user API key; future budget-changing features are not in current documented tool scope.

Ad-account data needs user API key; future budget-changing features are not in current documented tool scope.
Public listing does not imply a safe runtime or security audit.
See package authentication documentation; not independently tested.
Complete write authority is not verified.
Installation, client compatibility and comprehensive security have not been independently audited. Authentication and access depend on the configured services.
Operator must review permissions and remote data processing before installation.
runtime_installer_exact
Write actions/tool inventory not confirmed against exact tool documentation; listed action classes remain illustrative or context-dependent. Empty inventory does not establish read-only.
Exact install command and full env contract unverified except where explicitly documented; check official package before running.
Exact npm download observation only; no independent installation test.

Original activity observations

117 downloads from 2026-09-09 through 2026-10-08

Technical identity

npm/@dexun/adwhiz-mcp

Exact implementation source: https://www.npmjs.com/package/@dexun/adwhiz-mcp ↗
Reviewed resource type: MCP Server
Package identity: npm:@dexun/adwhiz-mcp

Evidence & Sources

Evidence basis: Recorded source evidence
Setup runtime verification: Not independently runtime-tested by MCP100 for this setup workflow.

Reviewed Oct 10, 2026 · Latest source observation Oct 10, 2026

Package registry ↗
@dexun/adwhiz-mcp
Recorded package identity, distribution or download evidence.

Setup · Watchlist

Install & Agents

Publisher instructions.

Source evidence observed Oct 14, 2026.

Additional setup details required — see the specific gaps below.

Install / connect
Publisher instructions
Publisher explicitly requires source checkout, Node 18+, `node <absolute checkout>/src/index.mjs`, ADWHIZ_API_KEY. All five documented tools are read-only.
publisher install or stdio launch · Publisher instructions
git clone https://github.com/dexun-inc/adwhiz-mcp.git ~/.adwhiz-mcp
Configure / authenticate
MCP100 setup guide
Publisher describes a single Node stdio script; clone repository and register `node /path/to/src/index.mjs` with ADWHIZ_API_KEY. No `npm install` required for its runtime.
Check connection
Suggested check
Verify tool discovery with configured key; avoid advertisement purchases/changes.
Remove / uninstall / revoke
MCP100 setup guide
For a Claude Code registration named `dexun-adwhiz-mcp`, run `claude mcp remove dexun-adwhiz-mcp`; otherwise remove the exact entry in the chosen MCP client settings and restart/reconnect. This client-host removal command is MCP100-composed from Claude Code lifecycle documentation, not a vendor-authored uninstall. With `npx`, a separate global package uninstall normally is unnecessary. Do not delete provider data or credentials by default.
Client unregister, package uninstall, data deletion, and OAuth/API token/wallet permissions are distinct.
Remove client registration · Claude Code only · MCP100 composed guide
claude mcp remove dexun-adwhiz-mcp

Official Documentation & Sources

What it does

Read ad accounts, recommendations, usage and savings insights; documented current version is read-only. Read-only MCP access to your DEXUN AdWhiz account: ad accounts, AI recommendations, savings.

Capability: Data & Databases
Resource type: MCP Server
Industry: Media & Marketing
Best fit: DEXUN AdWhiz analytics and recommendations

Representative uses

Review ad-account recommendations
Inspect recent account activity

Limitations

Ad-account data needs user API key; future budget-changing features are not in current documented tool scope.
Exact install command and full env contract unverified except where explicitly documented; check official package before running.
Exact npm download observation only; no independent installation test.

Reviewed access

Access & risk

Review the exact access boundary before connecting this MCP to accounts, credentials, or sensitive data.

Authentication: See package authentication documentation; not independently tested.
Permissions: Ad-account data needs user API key; future budget-changing features are not in current documented tool scope.
Data handling: Ad-account data needs user API key; future budget-changing features are not in current documented tool scope.
Cost: Not verified; check vendor terms
Risk and cautions: Ad-account data needs user API key; future budget-changing features are not in current documented tool scope.

Access scope and cautions

Write actions: Not verified
Risk level: medium
Security notes: Ad-account data needs user API key; future budget-changing features are not in current documented tool scope. Public listing does not imply a safe runtime or security audit.

The reviewed evidence does not establish the complete write authority of this MCP. Consult the unresolved evidence before granting write access.

FAQ

Based on reviewed evidence as of 2026-10-10T17:26:34Z. Watchlist tracking is not a recommendation or a security certification.

Which tasks are documented for this implementation?

The reviewed tasks include: Review ad-account recommendations; Inspect recent account activity.

What setup and authentication are documented?

A complete connection procedure is not verified. Client notes: Never infer missing startup flags or credentials. These facts do not supply missing installation commands, credentials or a verified authentication procedure. Authentication: API credential or authenticated app account required; exact setup should be checked in upstream package

Can it modify data or perform write operations?

Not verified. The available evidence does not establish the complete write authority. Recorded permission context: Ad-account data needs user API key; future budget-changing features are not in current documented tool scope.

What data-handling boundary should I consider?

Ad-account data needs user API key; future budget-changing features are not in current documented tool scope.

What limitations and risks should I check before use?

Ad-account data needs user API key; future budget-changing features are not in current documented tool scope. Exact install command and full env contract unverified except where explicitly documented; check official package before running. Exact npm download observation only; no independent installation test. Public listing does not imply a safe runtime or security audit. Operator must review permissions and remote data processing before installation.