Eclipse Social Core MCP

io.github.CYAN-ECLIPSE-TECHNOLOGIES-LLC由 GitHub 帳號 CYAN-ECLIPSE-TECHNOLOGIES-LLC 發布v0.1.1更新於 Oct 29, 2026

One canonical, hash-bound package behind every Eclipse social adapter. It publishes nothing itself

發布方自己的服務：core.blue

已驗證STDIO僅桌面效率與工作流溝通與協作安全與監控

服務詳細資訊

識別碼: io.github.CYAN-ECLIPSE-TECHNOLOGIES-LLC/social-core
傳輸: STDIO
執行環境: Desktop only
信任: Verified
發布於: Oct 26, 2026

安全提示

MCP 服務會接收對話中的工具呼叫請求，並可能執行外部操作。啟用前請先了解該服務能做什麼，並只授予它所需的權限。

註冊中心已驗證此條目所屬的 GitHub 帳號 CYAN-ECLIPSE-TECHNOLOGIES-LLC。這並不表明該帳號就是產品方。

SourceWeft 的檢查只涵蓋條目是否完整、端點是否回應；不審查伺服器的程式碼，也不審查其工具的行為。

在 README 中新增徽章

向讀者展示該 MCP 服務已收錄於 SourceWeft，徽章連結到本頁。

[![Listed on SourceWeft](https://sourceweft.com/badge/mcp/io.github.CYAN-ECLIPSE-TECHNOLOGIES-LLC%2Fsocial-core.svg)](https://sourceweft.com/mcp/io.github.CYAN-ECLIPSE-TECHNOLOGIES-LLC%2Fsocial-core?utm_source=readme&utm_medium=badge)

概覽

AI 產生的概覽

僅做治理的本機 MCP 伺服器：保存正規化的社群內容、產生各平台變體與差異，並記錄雜湊綁定的核准。

可以做什麼: 註冊帳號並檢視其宣告與生效的能力模式矩陣及熔斷狀態
接收並讀取正規化內容包，含來源、聲明與出處、權利、替代文字和揭露資訊
預覽各平台變體（尺寸、文案上限、連結位置、揭露標籤），並檢視分類後的改寫差異
修訂變體、產生核准包，並記錄或驗證雜湊綁定的擁有者核准
依每日上限與停止訊號評估互動策略，記錄互動並產生每日報告
切換熔斷開關，並列出含鏈結驗證的雜湊鏈回執帳本
適用情境: 適合讓助理在明確的擁有者核准下，為多個平台準備與審閱社群內容包，並讓每次變更與策略判定都留下回執，之後再由轉接器實際發布。它是治理與審閱層，不是發布工具。
執行需求: 以 uvx 啟動的 Python 套件在本機透過 stdio 執行（也可用 python3 server.py）；僅用 Python 標準函式庫，無相依套件。未宣告任何憑證或 API 金鑰。狀態存於伺服器旁的 data/state.json，可用環境變數 ECLIPSE_SOCIAL_CORE_STATE 覆寫。

安裝前請注意

此版本不執行任何平台動作，也不發起網路請求，因此本身無法發布內容。核准綁定雜湊：文案、排程、目的地、連結或揭露的任何變更都會使核准失效。策略檢查與互動日誌會永久寫入雜湊鏈帳本，熔斷開關會先凍結寫入。未聲稱任何認證，評測尚待進行。

安裝

在 SourceWeft 中

開啟儀表板中的 Eclipse Social Core MCP，將其新增到工作區。
為需要使用其工具的對話啟用該服務。

Desktop only，透過 STDIO。 STDIO 服務會啟動本機處理程序，因此需要 SourceWeft 桌面主機。

其他 MCP 客戶端

參照儲存庫中的啟動說明。

README

Eclipse Social Core MCP

The shared core of the Eclipse social adapter family — one canonical, owner-approved content package becomes a native draft, scheduled post, live post, or prep pack on each platform, according to what that platform actually sanctions. Analytics return with their platform definitions intact. It never uses a session workaround, never automates around a platform gate, and never publishes an unapproved variant.

Why this exists

Social platforms are separate publishing systems with separate accounts, media rules, API permissions, metrics, link behavior, and enforcement risk. A generic "post everywhere" abstraction that hides those differences produces broken crops, dead links, false analytics, and account jeopardy. The core holds the things every adapter must agree on — canonical content, rights, claims, approval, adaptation diffs, receipts, account safety — so each adapter only has to tell the truth about one platform. Spec: ~/workspace/cyan-eclipse/eclipse-social-family-spec-20261025.md (§3–§7).

Status — honest labels

v0.1.0, phase S0 core. Governance only: this server performs no platform action and makes no network calls. It holds packages, computes variants + diffs, records hash-bound approvals, evaluates engagement policy, and receipts everything. Adapters execute — or hand the owner a prep pack — elsewhere, only in their sanctioned mode. Local stdio, Python stdlib only, synthetic fixture package. No certification claimed — bench pending.

The hash law

An approval binds hashes, not vibes (§3.1). Ingest issues a SHA-256 content hash over the canonical object; every variant gets a variant hash over its media, copy, link, order, disclosures, schedule, and destination. approve_variant records both hashes; approval_check recomputes them from current fields. Any change — copy, schedule, destination, link, disclosure — changes the hash and invalidates the approval; the variant returns to review. Proven three ways in the test suite, including a direct field-tamper case.

Tools (15)

Tool	What it does
`account_set`	Register/update an authorized account: declared capability modes (capability → mode) + latest capability probe. A failed probe downgrades effective modes automatically — publish/draft collapse to `PREP_PACK`, own-engagement to `COMMUNITY_PREP`, reads stay flagged. Evaluation only; no credentials exist in this system.
`account_inventory`	All accounts with declared + effective mode matrices, last probe, kill-switch state.
`content_ingest`	Accept a canonical content object (§3.1): masters + provenance, copy, claims with sources, rights per asset, accessibility assets, disclosure record, intended/prohibited surfaces, schedule. Missing rights, unsourced claims, or missing alt text are named blockers. Re-ingesting changed content bumps the version.
`content_get`	One canonical record in full.
`adapt_preview`	Build one native variant for an adapter profile (`aperture_feed`, `aperture_reel`, `aperture_story`, `prism_shorts`, `zephyr`, `wire`): geometry, copy under the surface's limit, the surface's working link placement, platform-required disclosure labels, element order — plus the classified diff.
`adaptation_diff`	The classified diff for a variant (`MEDIA_CROP`, `TEXT_REWRITE`, `LINK_PLACEMENT`, `ORDER`, `DISCLOSURE`, `METADATA`, `FORMAT_OMISSION`, …). A rewrite that drops a canonical number/claim is flagged substantive — never silent.
`variant_revise`	Revise a variant; the hash recomputes and any approval bound to the old hash is invalidated.
`approval_pack`	The review artifact: canonical item + variants + diffs + destinations + schedule.
`approve_variant` / `approval_check`	Record / verify a hash-bound owner approval.
`policy_check`	The engagement playbook as an evaluator (§5). Actions: `like`, `comment`, `report_stop`, `reset`. Enforces week-1 caps (≤15 likes, ≤5 comments/day), week-2+ caps (≤30/≤10), ≤2 likes per target per day, no links / no self-promo / no hashtag stuffing / ≤1 emoji in comments, no duplicate comments, and stop-signal finality (an action block stops the session until an owner reset). Every check is receipted, ALLOW and DENY alike.
`engagement_log` / `engagement_report`	Append-only log of executed/owner-completed actions + the daily-report view (totals vs caps). No action goes unreported.
`adapter_kill_switch`	Disable family / one adapter / one account. Writes freeze first; drafts and receipts remain readable.
`receipt_list`	The hash-chained receipt ledger, with chain verification.

Modes (§2.1)

PUBLISH_API · DRAFT_API · PREP_PACK · READ_API · OWN_ENGAGEMENT_API · COMMUNITY_PREP · COMMUNITY_API_PILOT. No mode includes browser-session scripting, cookie reuse, proxies, or password collection — ever (§7). Community engagement defaults to COMMUNITY_PREP for every adapter at launch.

Run it

bash

python3 server.py            # MCP over stdio, stdlib only, no dependenciespython3 smoke.py             # end-to-end smoke over real stdio (temp state)python3 -m unittest discover tests   # 26 tests

python3 server.py            # MCP over stdio, stdlib only, no dependenciespython3 smoke.py             # end-to-end smoke over real stdio (temp state)python3 -m unittest discover tests   # 26 tests

State persists in data/state.json beside the server (override with ECLIPSE_SOCIAL_CORE_STATE). data/ is gitignored.

Fixtures

fixtures/sample_content.json — one synthetic White-Report-style episode package (9:16 reel master + cover, a sourced claim, owned rights, alt text, AI-media disclosure) that the tests and smoke drive end to end.

Roadmap (per spec §21)

S1 — Prism product face over Eclipse Connect rails.
S2 — Zephyr (built alongside this core) + Commons.
S3/S4 — Wire, Meridian, Pulse, Comet, Atlas by gate state. Each phase starts from a dated terms/capability record; a phase never inherits another adapter's verdict.