Skip to main content

eclipse-aperture

mcp-name: io.github.CYAN-ECLIPSE-TECHNOLOGIES-LLC/aperture

What this is: the MCP server for Eclipse Aperture — the Instagram adapter of Cyan Eclipse Technologies' Eclipse social adapter family, formalized. 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.

What this is not: v0.1 is a formalization, not a second Instagram pipe. It posts nothing and makes no live Graph API calls. The house's existing sanctioned connector route is referenced here, never duplicated — no token path, session handling, or credential material exists in this server.

Run it

$ pip install eclipse-aperture
$ eclipse-aperture           # MCP over stdio, Python stdlib only

MCP client config:

{ "mcpServers": { "eclipse-aperture": { "command": "uvx", "args": ["eclipse-aperture"] } } }

Tools (4)

capability_probe · variant_build · preview_pack · receipt_list

  • capability_probe returns the capability matrix from a static declaration fixture (dated, [verify]-flagged). A simulated probe failure downgrades the declared modes exactly as the family core prescribes — write modes collapse to prep, never to a workaround.
  • variant_build builds Feed (4:5), Carousel (narrative order), Reel (9:16), and Story (9:16) variants, each hash-bound with classified diffs vs canonical and the working link path (profile link / Story sticker — caption links are not clickable and are never the conversion path).
  • preview_pack is the exact native preview the owner approves.

Honest scope

  • Formalization only (phase S0). Approval here binds hashes; execution happens only through the house's existing sanctioned route, outside this product.
  • State persists in data/state.json beside the server (override with ECLIPSE_APERTURE_STATE); the capability declaration ships in the wheel at fixtures/capability.json.
  • 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. Not affiliated with Meta or Instagram; platform names describe the adapter surface only.

Metadata

Release files for eclipse-aperture 0.1.0

For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.

Source distribution (sdist)

Source distribution for eclipse-aperture 0.1.0
File Size Uploaded Provenance
eclipse_aperture-0.1.0.tar.gz 28.9 kB With provenance Details

Built distribution (wheel)

Table of built distributions (wheels) for eclipse-aperture 0.1.0
File Interpreter ABI Platform
eclipse_aperture-0.1.0-py3-none-any.whl Python 3 none any Details

Total release size: 41.4 kB

Release files / eclipse_aperture-0.1.0.tar.gz

Download URL eclipse_aperture-0.1.0.tar.gz
Size 28.9 kB
Tags Source
SHA-256 checksum
How to use checksums
4b5092a6521800900d97a3a7471c5b82d8580d149ea5f3e18bdbaa756ab45584
BLAKE2b-256 checksum
How to use checksums
ae9b63e6c482db2f6c82557bb7859f4e001deea9a54e051f34e7f74f28ff3877
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/7.0.0 CPython/3.13.16

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.

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 log

Release files / eclipse_aperture-0.1.0-py3-none-any.whl

Download URL eclipse_aperture-0.1.0-py3-none-any.whl
Size 12.5 kB
Tags Python 3
SHA-256 checksum
How to use checksums
58faec0a4e32b63ea79a545f1ee999877a0855d9fc9f4e519f4872bbb041c2ed
BLAKE2b-256 checksum
How to use checksums
bf5c0439eeaea5a219d005c3dea05989bdad65505a7562dffbfb0d1656faeb2e
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/7.0.0 CPython/3.13.16

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.

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 log

Security for eclipse-aperture 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.

Select from 2 files

Attestation for eclipse_aperture-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 log

A 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.

Release history Release notifications | RSS feed

This release

0.1.0 This release

2 release files Full provenance

Anthropic, PBC Visionary sponsor Bloomberg Visionary sponsor Hudson River Trading Visionary sponsor Meta Visionary sponsor NVIDIA Visionary sponsor Microsoft Sustainability sponsor Depot Continuous Integration AWS Cloud computing and Security Sponsor Datadog Monitoring Fastly CDN Google Download Analytics Sentry Error logging StatusPage Status page