eclipse-dispatch
mcp-name: io.github.CYAN-ECLIPSE-TECHNOLOGIES-LLC/dispatch
What this is: eclipse-dispatch is the MCP server edition of
Eclipse Dispatch — Cyan Eclipse Technologies' newsletter layer
above the platforms: it drafts once and syndicates the drafts to every
sanctioned platform, unifies the analytics, and watches your own
subscriptions like a portfolio.
What this is not: it never publishes — there is no publish tool, at any tier, for any platform — and it never scrapes. In v0.1 the adapters run against shipped fixtures and local stub HTTP servers shaped like the real APIs; nothing contacts a platform.
Use
$ pip install eclipse-dispatch
$ eclipse-dispatch # MCP server over stdio
Or run it as a container: ghcr.io/cyan-eclipse-technologies-llc/eclipse-dispatch-mcp:0.1.0.
Local stdio transport, Python stdlib only.
Tools (6)
| Tool | What it does |
|---|---|
draft_create |
Create the canonical draft (title, body, subtitle, canonical URL, tags, audience, per-platform variants). Versioned and hash-bound: returns the content_hash approval will bind to. |
draft_preview |
Per-platform rendered previews plus every adaptation diff vs the canonical draft. |
draft_approve |
Record owner approval; returns a token bound to the content hash. |
syndicate_drafts |
Fan the approved draft out: beehiiv/Ghost drafts via API-shaped adapters; Substack gets a paste pack. Requires the approval token and an un-invalidated hash. Receipt per platform. |
analytics_report |
Unified analytics, read-only. Figures carry platform provenance + the platform's own definition; a combined figure appears only where definitions are identical, otherwise flagged DEFINITIONS_DIFFER — never silently averaged. |
receipt_list |
Hash-chained receipts (drafts, approvals, syndications, analytics runs) + chain verification. |
Honest scope
- Hash-bound approval. Any post-approval edit invalidates the approval; syndication recomputes the hash and refuses by name.
- The beehiiv adapter has no publish method — deliberately, mirroring the platform's own design. The Substack adapter is read-only; write attempts raise a named refusal.
- Live platform wiring is owner-gated later-phase scope and is not in v0.1.
Powered by Cyan Eclipse Technologies LLC (cetech.ai) — a Veteran-Owned Small Business. MIT licensed.
1 maintainer
Metadata
1 maintainer
Release files for eclipse-dispatch 0.1.0
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | |
|---|---|---|---|---|
| eclipse_dispatch-0.1.0.tar.gz | 31.1 kB | With provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| eclipse_dispatch-0.1.0-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 47.4 kB
Release files / eclipse_dispatch-0.1.0.tar.gz
| Download URL | eclipse_dispatch-0.1.0.tar.gz |
|---|---|
| Size | 31.1 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
cebfea8c68fe6847d2a20add98d62059c27ed3193db29479ecb816e2bc999767
|
|
BLAKE2b-256 checksum How to use checksums |
4e4b2a8db0a2345fd288cc92af1564f27dc5ab681e38c04e193032c6d8b92c72
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.16
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Oct 27, 2026.
Transparency logRelease files / eclipse_dispatch-0.1.0-py3-none-any.whl
| Download URL | eclipse_dispatch-0.1.0-py3-none-any.whl |
|---|---|
| Size | 16.4 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
6788e5703bca2a1bec6145d9436bd4020288aae4fe6269d32f05580ed3b1f28d
|
|
BLAKE2b-256 checksum How to use checksums |
ae28ca6a6ad86487d1fddfc9209ecc7e3a910caced7b9526e70a70c7c3db4c4e
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.16
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Oct 27, 2026.
Transparency logSecurity for eclipse-dispatch 0.1.0
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
Full provenance
All 2 files in this release have been uploaded with provenance metadata.
Attestation for eclipse_dispatch-0.1.0.tar.gz
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Oct 27, 2026.
Transparency logA note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.
