Eclipse Aperture MCP

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

The Instagram adapter, formalized: capability-declared, hash-bound native variants for Feed

VerifiedSTDIODesktop onlyProductivity & WorkflowMedia & Design

Overview

AI-generated overview

Local stdio MCP server that builds Instagram Feed, Carousel, Story and Reel variants from an approved content package, with previews and hash-chained receipts.

What you can do
  • Probe a static capability matrix for publishing, reading, own-media comments and community prep, with a simulated downgrade path
  • Build native variants (Feed 4:5, Carousel, Reel 9:16, Story 9:16) from a canonical package, with link path, AI-media label, diffs and variant hash
  • Produce the exact native preview an owner approves, including geometry, caption, safe zones, hashtags, disclosures and bound hashes
  • List the append-only, hash-chained receipt ledger and verify the chain
When to use it
Useful when you want an assistant to turn one approved content package into correctly proportioned Instagram variants and an approval-ready preview, with an auditable record, without any live posting. It is a formalization-phase tool, so it suits evaluation and drafting rather than running a real Instagram account.
Requirements
Runs locally over stdio as a Python package (eclipse-aperture, launched with uvx) or via python3 server.py; Python standard library only, no dependencies. No authentication, API keys or environment variables are declared. State is kept in data/state.json, overridable with ECLIPSE_APERTURE_STATE; capability data comes from a local fixture file.
Before you install
The README states the server posts nothing and makes no live calls, and that no certification is claimed; the capability matrix is a static fixture flagged for verification, so treat its claims as unproven. Variant building and previews write local state and receipts. It is desktop-only and not web-executable.

Installation

In SourceWeft

  1. Open Eclipse Aperture 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 Aperture MCP

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

Eclipse Aperture — the Instagram adapter: one approved package becomes native Feed, Carousel, Story, and Reel variants for a professional account, with publishing and analytics only through Meta's sanctioned Graph API surface.

Why this exists

The White Report already operates Instagram professionally through the house's existing sanctioned connector. S0 turns that working route into a capability-probed, hash-bound product surface instead of a collection of habits (spec §9, §18). Aperture is that surface: the capability declaration, the native variants, the preview the owner approves, and the receipts.

Status — honest labels

v0.1.0, phase S0 formalization. This server posts nothing and makes no live calls. The house's Instagram operation continues through its existing connector, outside this product; Aperture references that route and never duplicates it — there is no second token path, no session handling, and no credential material anywhere in this code. Local stdio, Python stdlib only. No certification claimed — bench pending.

Tools (4)

ToolWhat it does
capability_probeReturns the capability matrix from a static declaration fixture (dated 2026-10-25, [verify]-flagged): PUBLISH_API for publishing/drafts, READ_API for reads, OWN_ENGAGEMENT_API for own-media comments, COMMUNITY_PREP for community engagement — the §9 posture for eligible professional accounts, grade A subject to Meta app permissions, review, account role, and current Graph API version. simulate_probe_failure=true exercises the family downgrade rule: write modes collapse to prep — automatically, and never to a workaround.
variant_buildBuild one native variant from a canonical package: Feed 4:5, Carousel in narrative order (first card = hook, payoff before end card), Reel 9:16, Story 9:16 — with the working link path (profile link; Story link sticker — caption links are not clickable and are never the conversion path), the platform AI-media label carried on the variant, classified diffs vs canonical, and the variant hash.
preview_packThe exact native preview the owner approves: rendered geometry, caption, link path, safe-zone notes, hashtags, disclosures, order — plus diffs and the hashes an approval binds.
receipt_listThe append-only, hash-chained receipt ledger, with chain verification.

Native rules carried in code (§9)

  • Feed portrait 4:5 uses the grid better than square; landscape derivatives are shown, never center-cropped blindly.
  • Reels/Stories 9:16 with platform safe zones respected — text and evidence stay out of the top/bottom UI bands.
  • Hashtags are searchable metadata, not stuffing; the approved set appears in the diff.
  • Threads is not a separate product (§8): it rides as a sub-adapter inside this Meta family tooling when its gated modes are proven — no Threads listing or claim exists.

Run it

bash
python3 server.py            # MCP over stdio, stdlib only, no dependenciespython3 smoke.py             # probe + Reel variant + preview over real stdiopython3 -m unittest discover tests   # 11 tests

State persists in data/state.json (override with ECLIPSE_APERTURE_STATE). data/ is gitignored. The capability fixture lives at fixtures/capability.json; the smoke drives the social core's sample_content.json package.

Roadmap (per spec §21)

  • Dated Meta terms/capability record replacing the static declaration → live ig_capability_probe.
  • ig_media_stage / ig_container_verify / ig_publish_receipt / ig_insights_read / ig_own_comment_queue — only against the sanctioned Graph surface, only for approved hash-bound packs, with publish read-back before any completion claim. Execution wiring stays on the house's existing route.

License / attribution

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

Source: README.md at commit b6c1fe9

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