# Ad Spec Guard Muse connector

From musedirectory.ai, the independent directory of Meta Muse connectors. Not affiliated with Meta.

## Ad Spec Guard

Checks ad copy, creative sizes and tracking links against platform rules before you publish.

- Record: https://musedirectory.ai/connector/ad-spec-guard
- Category: Marketing & Ads
- Developer: notformal (https://adsbeast.pro)
- Muse status: Extra setup. Not in Muse's Connectors list yet. Muse can still use it: its page gives you a request to paste into Muse.
- Health: Working, 434ms, checked 2026-11-22T19:31:09Z
- Endpoint: https://adsbeast.pro/api/mcp
- Auth: No account needed; Pricing: unknown
- Screening: Screened, no issues found (2026-11-22T11:51:31Z)
- Source: Found in the official MCP Registry (io.github.notformal/ad-spec-guard) https://registry.modelcontextprotocol.io/v0/servers?search=io.github.notformal%2Fad-spec-guard

Connects to a built-in reference of ad platform specs for Google, Meta, LinkedIn, TikTok, Microsoft and Telegram. Muse can validate character limits, image and video dimensions, UTM tags, policy risk patterns, A/B test significance and whether a campaign has enough data to change.

Example request: "Check my Meta ad headlines and descriptions against the character limits before I upload them."

How to connect: Not in Muse's Connectors list yet, but Muse can still use it. Paste this into Muse: "Use Ad Spec Guard to help me. It is a free service with an MCP server at https://adsbeast.pro/api/mcp. It does not need an API key. Ask me before you share anything with it." Muse asks before it shares anything with the app's site. Meta does not review apps used this way, so only use ones you trust. We tested this in the Muse app on September 24, 2026: Muse used an app's link directly this way and returned a live answer.

Tools:
- get_platform_specs: Return the verified specification sheet for one ad platform: hard character limits per copy field, image formats with their required dimensions and file size caps, learning-phase windows, and the conversion history automated bidding needs. Call this before writing ad copy or brie
- validate_ad_copy: Check drafted ad copy against the hard character limits of one platform, field by field, and report which fields exceed the limit and by how much. Use it on every draft before presenting it, because copy over the limit is rejected when the ad is uploaded, not when it is written.
- validate_creative_spec: Check an image or video against a platform placement's required dimensions, aspect ratio, file size cap and accepted file types. Width and height are enough to answer whether a size fits a placement; supply file size and type as well when the file exists, and the result says whic
- check_decision_readiness: Decide whether a live campaign has produced enough data to justify pausing it, scaling its budget, rotating a creative or switching bidding strategy, and whether it is still inside the platform's learning phase. Returns the unmet requirements with the shortfall and an estimate of
- ab_test_significance: Run a two-proportion z-test on two variants of an ad, landing page or audience, and report the p-value, whether the difference is statistically significant at the chosen confidence level, and how much more traffic would be needed to resolve it if it is not. Use it for any compari
- build_utm: Assemble a campaign URL with consistent UTM tagging, normalise the values so they do not split into duplicate rows in analytics, and report every correction made and every risk found. Also flags a source or medium that departs from the conventional value for the platform, which s
- validate_utm: Inspect the UTM parameters already on a URL and report missing required parameters and values that will fragment reporting, such as mixed case or encoded spaces. Does not rewrite the URL.
- estimate_budget_feasibility: Work out whether a monthly budget can reach a target cost per acquisition or return on ad spend, and whether it produces enough weekly conversions for automated delivery to leave the learning phase. Nothing is filled in from industry averages: for any input not supplied, it solve
- check_ad_policy_preflight: Scan ad copy for the two patterns behind most rejections: a business category the platform prohibits or gates behind certification, and a claim the platform treats as unverifiable. Returns each match with the governing policy page. This is a pattern pre-check, not an approval; on

Screening checks:
- MCP handshake: pass (Answered in 90ms)
- Domain against threat feeds (Cloudflare security DNS): pass (adsbeast.pro not flagged)
- Published packages against the OSV malicious-package database: n/a (No npm or PyPI package published)
- Hidden instructions or invisible characters in tool text: pass (9 tools read, nothing found)
- Inputs asking for passwords, card numbers or seed phrases: pass (None found)
- Domain and redirects: pass (No redirects off the domain)
- AI review of purpose and tool behavior: pass (No concerns)
