eclipse-social-core
mcp-name: io.github.CYAN-ECLIPSE-TECHNOLOGIES-LLC/social-core
What this is: the MCP server for Eclipse Social Core — the shared core of Cyan Eclipse Technologies' Eclipse social adapter family. One canonical, versioned, hash-bound content package; per-adapter native variants with classified adaptation diffs; hash-bound owner approvals that any change invalidates; a per-account capability mode registry with downgrade-on-probe-failure semantics; per-adapter/account/family kill switches; and the engagement policy module (the house engagement playbook as data).
What this is not: it performs no platform action — no posting, no liking, no commenting, no network call, and it holds no credential material. Adapters execute (or hand the owner a prep pack) elsewhere, only in their sanctioned mode.
Run it
$ pip install eclipse-social-core
$ eclipse-social-core # MCP over stdio, Python stdlib only
MCP client config:
{ "mcpServers": { "eclipse-social-core": { "command": "uvx", "args": ["eclipse-social-core"] } } }
Tools (15)
account_set · account_inventory · content_ingest · content_get ·
adapt_preview · adaptation_diff · variant_revise · approval_pack ·
approve_variant · approval_check · policy_check · engagement_log ·
engagement_report · adapter_kill_switch · receipt_list
Honest scope
- Governance only (phase S0). Hash law: an approval binds the exact canonical hash and the exact variant hash — any later change to media, copy, links, order, disclosure, schedule, or destination changes the variant hash and invalidates that variant's approval.
- Every ingest, adaptation, approval, revision, policy check (ALLOW and DENY alike), kill-switch change, and probe-driven downgrade appends a hash-chained receipt — append-only, verifiable.
- State persists in
data/state.jsonbeside the server (override withECLIPSE_SOCIAL_CORE_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-social-core 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_social_core-0.1.0.tar.gz | 36.7 kB | With provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| eclipse_social_core-0.1.0-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 55.1 kB
Security for eclipse-social-core 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_social_core-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.