Eclipse Airtime MCP
Eclipse Airtime — mandate-bound ad operations.
status: in-developmentclass: mcpMarketing & Ads Governance
Vendor: Cyan Eclipse Technologies
What it does
- Spend enforcement pre-call: every campaign mutation passes a gate against a Herald-signed mandate (account × platform ceilings, geo/audience bounds, and flight windows) before any platform call; a refusal makes zero platform calls
- Claims binding at the publish path: copy may publish only from a signed claims record, with paraphrase screening, special-category classification, implied-attribute screening, crypto permission classes, and political verification as versioned policy data
- Advertiser-held evidence that survives the account: mutations and refusals seal into an append-only, hash-chained, signed ledger and export as an offline-verifiable appeal pack
- A closed refusal vocabulary and no override tool at any tier — more spend requires a new signed mandate, never an exception path
- P0 is Meta-first and local/simulator only: the transport is a simulator/test-double, no live spend exists, and no campaign activates for real
Tools
mandate_issue · mandate_get · mandate_check · mandate_revoke · claims_record_upsert · claims_record_get · copy_screen · ad_account_list · campaign_list · campaign_get · insights_get · campaign_create_draft · campaign_update · campaign_set_status · audience_attach · ledger_get · appeal_pack_export
Platforms
- MCP over stdio
Certification
Bench verdict: CERTIFIED(local/simulator)
Certified scope: CERTIFIED(local/simulator) — Eclipse Bazaar Test Bench 2026-10-25, 23/23 checks. Run by W-003 (Verity), suites/airtime.py. The original PARTIAL card (20/23; D1 MEDIUM + D2 HIGH) is retained append-only; the scoped re-bench card -2 closed both defects and is the standing verdict basis. N-CHECK: NOVELTY_PROVEN — spend enforcement happens pre-call, ad copy is bound to a signed claims record at the publish path, and every mutation or refusal seals into an advertiser-held evidence ledger. Simulator/test-double only; no live transport, campaign, or spend was tested.
Not tested:
- Live Meta transport — NOT built and out of P0 scope: simulator/test-double only; no live spend exists.
- Standalone Claims Checker as a separate Bazaar Tool — P1 per spec §3.3; P0 ships the internal harness form (tools/claims_checker.py), exercised as part of the benched product surface.
- Google/TikTok/X/LinkedIn/Reddit phases (P1/P3), hosted connector + CASA posture (P2), and Till billing composition (P2).
- Production Herald custody for the signing key — P0 uses a local seed key (keys/, gitignored, chmod 600); production custody is a hard gate before any P2/live scope.
Bench scorecard (evidence): https://eclipsebazaar.com/cards/eclipse-airtime-mcp-2026-10-25-2.json
Pricing
Free local v0.1; governed-seat + per-screen pricing TBD per spec section 13 (Evidence Verifier free/unmetered by design)
Install / verify
docker run -i ghcr.io/cyan-eclipse-technologies-llc/eclipse-airtime-mcp:latest
Official MCP Registry name: ai.cetech/eclipse-airtime
Registry listing: https://registry.modelcontextprotocol.io/v0.1/servers/ai.cetech%2Feclipse-airtime/versions/0.1.0
Verify any MCP server in your client configs against this catalog with bazaar check (Eclipse Bazaar MCP / CLI — see llms.txt).