AdCrunch

The materials explicitly state that no keys or environment variables are required, and no API keys, OAuth tokens, or local sensitive credentials are requested; based on the provided facts, credential exposure appears low.

It connects to the remote endpoint mcp.adcrunch.dev, and its described function involves querying Meta, TikTok, and Google Ads performance, implying that user queries and related ad data may be processed or relayed by that service; this is a normal risk for a networked MCP, and no unrelated or unknown endpoints are disclosed in the materials.

System checks indicate that the tool executes code or starts a process, which is a standard property of MCP tools; the materials do not indicate requests for elevated system privileges or any red flags suggesting unusually broad command execution.

Based on the description, its core purpose is to answer questions about ad performance, so access to advertising analytics data is expected; however, the missing README does not clarify what local files, caches, or external resources it can read or write, leaving only moderate transparency around data access boundaries.

Positive signals include the official registry source, an auditable open-source repository, and updates within the last year; however, the repository does not declare a license, community adoption is very low (0 stars), and documentation is sparse, which raises the review burden for dependencies and implementation details, so the supply-chain posture warrants caution but not a high-risk rating.