Microsoft Ads MCP

Create and manage Microsoft Advertising campaigns (Bing Ads / DuckDuckGo Ads) via MCP server - campaigns, ad groups, keywords, ads, and reporting

This skill appears to do what it claims (manage Microsoft Ads via an MCP server) but several operational details are missing or inconsistent in the registry metadata. Before installing or running it: 1) Inspect the GitHub repo (https://github.com/Duartemartins/microsoft-ads-mcp-server) and review server.py and requirements.txt for any unexpected behavior or risky dependencies. 2) Confirm you want to install and run third‑party Python code on your machine and understand where credentials and OAuth tokens will be stored (the instructions suggest ~/.mcporter/mcporter.json). 3) If possible, use least‑privilege credentials or a dedicated test Microsoft Ads account while evaluating. 4) Consider running the server in a sandbox or isolated environment (container/VM). 5) Ask the publisher to update the skill metadata to declare required binaries (mcporter), config paths (~/.mcporter/mcporter.json), and environment/credential needs explicitly — that would remove the main coherence concerns. If you cannot validate the repository and token storage practices, avoid installing or supplying production credentials.

Type: OpenClaw Skill Name: microsoft-ads-mcp Version: 1.0.0 The skill is classified as suspicious due to its reliance on an external GitHub repository (`https://github.com/Duartemartins/microsoft-ads-mcp-server.git`) for its core functionality, as detailed in `SKILL.md`. The setup instructions involve cloning this repository and installing its dependencies via `pip install -r requirements.txt`, followed by executing `server.py` from the cloned content. This introduces a significant supply chain risk, as the integrity of the external repository directly impacts the security of the agent's environment and the sensitive credentials (Microsoft Ads Developer Token, Azure AD Client ID) that are configured to be passed to the external server.