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.