Eclipse Dispatch MCP
Drafts once, syndicates drafts everywhere sanctioned, unifies the analytics. Never publishes without approval; never scrapes.
status: in-developmentclass: mcpPublishing / Newsletters
Vendor: Cyan Eclipse Technologies
What it does
- One canonical, versioned, hash-bound draft: any post-approval edit invalidates the approval by name
- Syndication as per-platform drafts via sanctioned-API-shaped adapters (beehiiv, Ghost)
- Read-only platforms (Substack) get a paste pack, never a write; the beehiiv adapter has no publish method
- Unified analytics with per-source metric definitions: differing definitions flagged DEFINITIONS_DIFFER, never blended
- Hash-chained receipts over drafts, approvals, syndications and analytics runs
Tools
draft_create · draft_preview · draft_approve · syndicate_drafts · analytics_report · receipt_list
Platforms
- MCP over stdio (HTTP transport on roadmap)
Certification
Bench verdict: CERTIFIED(local)
Certified scope: CERTIFIED(local) — Eclipse Bazaar Test Bench 2026-10-25, 13/14 checks pass, 1 na (U1 auth: stdio process boundary). Run by W-003 (Verity), suites/dispatch.py.
Not tested:
- Live platform wiring: adapters run against fixtures and local stub HTTP servers shaped like the real APIs. beehiiv signup is an owner Wave-2 item; no Ghost instance runs here; Substack live reads (official MCP analytics) not exercised.
Bench scorecard (evidence): https://eclipsebazaar.com/cards/eclipse-dispatch-mcp-2026-10-25.json
Pricing
Free local v0.1; hosted tier TBD per spec
Install / verify
uvx eclipse-dispatch
Official MCP Registry name: io.github.CYAN-ECLIPSE-TECHNOLOGIES-LLC/dispatch
Registry listing: https://registry.modelcontextprotocol.io/v0.1/servers/io.github.CYAN-ECLIPSE-TECHNOLOGIES-LLC%2Fdispatch/versions/0.1.0
Repository: https://github.com/CYAN-ECLIPSE-TECHNOLOGIES-LLC/eclipse-dispatch-mcp
Verify any MCP server in your client configs against this catalog with bazaar check (Eclipse Bazaar MCP / CLI — see llms.txt).