eclipse-muster
mcp-name: io.github.CYAN-ECLIPSE-TECHNOLOGIES-LLC/muster
What this is: the MCP server for Eclipse Muster — the shared core of Cyan Eclipse Technologies' Eclipse customer adapter family. One canonical Customer Graph becomes governed reads, internal writes, and owner-approved drafts across the popular CRM and customer-service platforms, according to what each platform actually sanctions.
What this is not: phase C0 is a local core over owner-fed records with synthetic fixtures. No platform is contacted, no credential exists in this build, and no message is sent from here — sends are adapter tools gated by owner approval tokens, elsewhere.
Run it
$ pip install eclipse-muster
$ eclipse-muster # MCP over stdio, Python stdlib only
MCP client config:
{ "mcpServers": { "eclipse-muster": { "command": "uvx", "args": ["eclipse-muster"] } } }
Tools (9)
record_ingest · record_read · record_search · merge_propose ·
merge_execute · merge_unmerge · reply_draft · policy_show ·
receipt_list
Honest scope
- Every field on every record carries provenance and every record a Data Rights Ledger block; a field without provenance does not enter the graph. Identity merges are propose-only — a merge executes only on an owner-confirm token bound to the proposal hash, and can be unmerged exactly from its receipt.
- Field-level masking is enforced at egress; reply drafts are
generated only from record facts with citations — untraceable facts
surface as
MISSING_FACTmarkers. Instruction-shaped customer text is quarantined at ingest (Herald Security Law #1): data, never commands. Receipts carry IDs, hashes, tiers, and verdicts — never content. - Policy floors live in
policy.json, shipped beside the server in the wheel (override withECLIPSE_MUSTER_POLICY); state persists indata/state.json(override withECLIPSE_MUSTER_STATE). - Certified (local) by the Eclipse Test Bench at v0.1.0; the listing status in the Eclipse Bazaar catalog is in-development.
Powered by Cyan Eclipse Technologies LLC (cetech.ai) — a Veteran-Owned Small Business. MIT licensed.
Metadata
Release files for eclipse-muster 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_muster-0.1.0.tar.gz | 34.6 kB | With provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| eclipse_muster-0.1.0-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 51.6 kB
Release files / eclipse_muster-0.1.0.tar.gz
| Download URL | eclipse_muster-0.1.0.tar.gz |
|---|---|
| Size | 34.6 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
580498ee06d71d87bda2adbe1e15ab3eed73e9a2a3c9419a6092ddfd1fff3ec6
|
|
BLAKE2b-256 checksum How to use checksums |
06bbbe3350e997d37b5e14eff05b67339ff46e89b9e77e8741ad70b347ad0c14
|
| 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_muster-0.1.0-py3-none-any.whl
| Download URL | eclipse_muster-0.1.0-py3-none-any.whl |
|---|---|
| Size | 17.0 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
d8f6c8973edbbdd036fb59afd569ff3dcad9238d4875ab606ff59c0d777e5f47
|
|
BLAKE2b-256 checksum How to use checksums |
47506299e3dc09b5615e86467f9659618649e011fac0953d1656adb324659dd3
|
| 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-muster 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_muster-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.