Eclipse Social Core MCP

io.github.CYAN-ECLIPSE-TECHNOLOGIES-LLCPublished by GitHub account CYAN-ECLIPSE-TECHNOLOGIES-LLCv0.1.1Updated Oct 29, 2026

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

The publisher's own server: core.blue

VerifiedSTDIODesktop onlyProductivity & WorkflowCommunication & CollaborationSecurity & Monitoring

Overview

AI-generated overview

Local governance-only MCP server that holds canonical social content, builds per-platform variants with diffs, and records hash-bound approvals.

What you can do
  • Register accounts with declared and effective capability modes, and list their mode matrices and kill-switch state
  • Ingest and read canonical content packages with provenance, claims and sources, rights, alt text and disclosures
  • Preview per-platform variants with geometry, copy limits, link placement and disclosures, and inspect classified adaptation diffs
  • Revise variants, build approval packs, and record or verify hash-bound owner approvals
  • Evaluate engagement policy against daily caps and stop signals, log engagement and produce daily reports
  • Toggle kill switches and list the hash-chained receipt ledger with chain verification
When to use it
Useful when you want an assistant to prepare and review social content packages for several platforms under explicit owner approval, with every change and policy decision receipted, before any adapter actually posts. It is a governance and review layer, not a publishing tool.
Requirements
Runs locally over stdio as a Python package launched with uvx (or python3 server.py); Python standard library only, no dependencies. No credentials or API keys are declared. State is stored in data/state.json beside the server, overridable with the ECLIPSE_SOCIAL_CORE_STATE environment variable.
Before you install
It performs no platform actions and makes no network calls in this version, so it cannot post anything itself. Approvals bind hashes: any change to copy, schedule, destination, link or disclosure invalidates an approval. Policy checks and engagement logs are recorded permanently in a hash-chained ledger, and kill switches freeze writes. No certification is claimed and the bench is pending.

Installation

In SourceWeft

  1. Open Eclipse Social Core MCP in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.

Other MCP clients

Follow the launch instructions in the repository.

README

Eclipse Social Core MCP

Powered by Cyan Eclipse Technologies — https://cetech.ai

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)

ToolWhat it does
account_setRegister/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_inventoryAll accounts with declared + effective mode matrices, last probe, kill-switch state.
content_ingestAccept 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_getOne canonical record in full.
adapt_previewBuild 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_diffThe 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_reviseRevise a variant; the hash recomputes and any approval bound to the old hash is invalidated.
approval_packThe review artifact: canonical item + variants + diffs + destinations + schedule.
approve_variant / approval_checkRecord / verify a hash-bound owner approval.
policy_checkThe 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_reportAppend-only log of executed/owner-completed actions + the daily-report view (totals vs caps). No action goes unreported.
adapter_kill_switchDisable family / one adapter / one account. Writes freeze first; drafts and receipts remain readable.
receipt_listThe 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

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.

License / attribution

A Cyan Eclipse Technologies product. The "Powered by Cyan Eclipse Technologies" attribution travels with it.

Source: README.md at commit 49e4686

Tools

0
SourceWeft has not started this package in its sandbox yet, so its tools are not known.

Version history

2
  1. v0.1.1LatestOct 29, 2026
  2. v0.1.0Oct 26, 2026

Score

50% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 days25 pts

    Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.

  • Auth declared10 pts

    Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.

  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts
  • License10 pts

Other Core integrations

core.blue

blue.coreOfficial publisher

Remote MCP endpoint for core.blue's private per-customer agent memory "houses": read its manual, try a sandbox, get pricing and recommendations, and request a…

Streamable HTTPWeb executable
Business & Commerce10 toolsNov 4, 2026

Brevio Core

Published by GitHub account Brevio-Ventures

Local MCP server that lets a coding agent scan code for recurring agent-written mistakes, explain rules, list rules and turn a fix into a guard.

STDIODesktop only
Developer ToolsNot validated yetNov 7, 2026

brain-core

Published by GitHub account xy-claude

Local MCP server that gives a Claude Code agent persistent memory across sessions, stored as markdown files plus a SQLite and vector index on your disk.

STDIODesktop only
Developer ToolsNot validated · the package did not installNov 7, 2026

Scovant Core

Published by GitHub account Scovant

Passive AI-agent readiness scan of a website: robots, llms.txt, JSON-LD, MCP discovery, security.

STDIODesktop only
AI & MLNot validated yetNov 3, 2026

ProofCore

Published by GitHub account ProofCore-Protocol

Zero-Auth Cryptographic Notarization & Evidence Layer on TON Blockchain for AI Agents.

Streamable HTTPWeb executable
AI & ML4 toolsNov 3, 2026