# Eclipse Aperture MCP (pypi · eclipse-aperture)

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

- Trust score: 70/100 (medium)
- Change this week: −6
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-04

## Components

- pypi · `eclipse-aperture`: 70/100 (this document), [markdown](https://verifymcp.io/servers/cyan-eclipse-technologies-llc-aperture/eclipse-aperture.md), [page](https://verifymcp.io/servers/cyan-eclipse-technologies-llc-aperture/eclipse-aperture)

## Channel facts

- Registry: `pypi`
- Package: `eclipse-aperture`
- Version: `0.1.0`
- Transport: `stdio`

## Trust breakdown

How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-11-04.

- **Supply Chain Security**: 100/100
  - No malware found by supply-chain analysis.
  - No known CVEs affecting this package version or its production dependencies.
  - Runs hatchling.build at install time, a recognised build step with no custom scripting around it.
  - No production dependencies, so there is no dependency health to assess.
- **Provenance & Transparency**: 71/100
  - Repository check failed: the declared repository URL redirects; it must resolve directly.
  - Cryptographically verified build provenance (signed, bound to CYAN-ECLIPSE-TECHNOLOGIES-LLC/eclipse-aperture-mcp).
  - Clear OSI-approved license (MIT).
  - Actively maintained (last published 7 days ago).
  - Disclosure check failed: no security disclosure policy was found in the source repository.
- **Schema Quality & AI Usability**: 60/100
  - AI-judged instruction clarity (fair).
  - Tool/resource definitions use about 269 tokens (~67/item across 4 items; 4 tools + 0 resources), lean.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 0/100
  - Stability not yet verified: not enough scan history yet (needs a 30-day window).
- **Tool Coverage**: 67/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 0% of tool parameters carry a description.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 4 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 4 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

**Unverified: 1 category.** A category scored 0 because we could not verify it: a data source with nothing on this package, evidence we could not reach, or a check we could not run. We only credit what we can confirm.

## Install

### How do I install the Eclipse Aperture MCP server?

Eclipse Aperture MCP runs locally as a PyPI package, launched with uvx eclipse-aperture. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

### Claude

```bash
claude mcp add cyan-eclipse-technologies-llc-aperture -- uvx eclipse-aperture
```

### Cursor

```json
{
  "mcpServers": {
    "cyan-eclipse-technologies-llc-aperture": {
      "command": "uvx",
      "args": [
        "eclipse-aperture"
      ]
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "cyan-eclipse-technologies-llc-aperture": {
      "command": "uvx",
      "args": [
        "eclipse-aperture"
      ]
    }
  }
}
```

### Codex

```bash
codex mcp add cyan-eclipse-technologies-llc-aperture -- uvx eclipse-aperture
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "cyan-eclipse-technologies-llc-aperture": {
      "type": "local",
      "command": [
        "uvx",
        "eclipse-aperture"
      ],
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add cyan-eclipse-technologies-llc-aperture --command uvx --arg eclipse-aperture
```

### Hermes

```yaml
mcp_servers:
  cyan-eclipse-technologies-llc-aperture:
    command: "uvx"
    args: ["eclipse-aperture"]
```

### Netclaw

```json
{
  "McpServers": {
    "cyan-eclipse-technologies-llc-aperture": {
      "Transport": "stdio",
      "Command": "uvx",
      "Arguments": [
        "eclipse-aperture"
      ]
    }
  }
}
```

### Vellum

```bash
assistant mcp add cyan-eclipse-technologies-llc-aperture -t stdio -c uvx -a eclipse-aperture
```

### Other

```json
{
  "mcpServers": {
    "cyan-eclipse-technologies-llc-aperture": {
      "command": "uvx",
      "args": [
        "eclipse-aperture"
      ]
    }
  }
}
```

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-10-29 (score 70, −6)

- [security regression] Source repository: pass → fail

### 2026-10-28 (score 76, +15)

- [security improvement] Malware scan: unverified → pass

### 2026-10-27 (score 61)

First indexed and scored.

## MCP tools (4)

### `capability_probe` (~91 tokens)

Return Aperture's capability matrix from the STATIC declaration fixture (dated, [verify]-flagged): per-capability modes for an eligible professional Instagram account per spec SS9. NO live Graph API call is made in v0.1. Pass simulate_probe_failure=true to exercise the family downgrade rule: write modes collapse to prep, own-engagement to COMMUNITY_PREP.

Input parameters:

- `simulate_probe_failure` (boolean)

### `variant_build` (~109 tokens)

Build one native Instagram variant (feed 4:5 | carousel narrative order | reel 9:16 | story 9:16) from a canonical content package: geometry, caption, the working link path (profile link / Story sticker — caption links are not clickable), platform AI-media label, classified diff vs canonical, and the variant's hash. Formalization only — nothing is posted.

Input parameters:

- `account_id` (string)
- `package` (object, required)
- `surface` (string)

### `preview_pack` (~47 tokens)

The exact native preview for a built variant — rendered geometry/caption/link path/safe zones — plus its diffs and the hashes an approval would bind.

Input parameters:

- `variant_id` (string, required)

### `receipt_list` (~22 tokens)

The append-only, hash-chained receipt ledger, with chain verification.

## Diagnostics

Captured diagnostic sections: Provenance, Install scripts, Dependencies. The full working is on the page: https://verifymcp.io/servers/cyan-eclipse-technologies-llc-aperture/eclipse-aperture#diagnostics

## Score history

- 2026-11-04: 70
- 2026-11-03: 70
- 2026-11-02: 70
- 2026-11-01: 70
- 2026-10-31: 70
- 2026-10-30: 70
- 2026-10-29: 70
- 2026-10-28: 76
- 2026-10-27: 61

## Common questions

### What is the Eclipse Aperture MCP server?

Eclipse Aperture MCP is listed in the public MCP registry as io.github.CYAN-ECLIPSE-TECHNOLOGIES-LLC/aperture. The Instagram adapter, formalized: capability-declared, hash-bound native variants for Feed. This page covers its PyPI package (eclipse-aperture).

### Is the Eclipse Aperture MCP server safe to use?

Eclipse Aperture MCP scores 70 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 4 November 2026. Its build provenance is signed and verified. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

### What tools does the Eclipse Aperture MCP server expose?

Eclipse Aperture MCP exposes 4 tools: capability_probe, variant_build, preview_pack, receipt_list. Their descriptions and schemas cost roughly 269 tokens of context every time the server is loaded.

### Is the Eclipse Aperture MCP server still maintained?

Eclipse Aperture MCP is still listed as active in the MCP registry. We last reached this channel on 4 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

### What licence is the Eclipse Aperture MCP server under?

Eclipse Aperture MCP declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.

## Links

- PyPI project: https://pypi.org/project/eclipse-aperture/
- Socket report: https://socket.dev/pypi/package/eclipse-aperture
- Website: https://eclipsebazaar.com/
- Changelog RSS feed: https://verifymcp.io/servers/cyan-eclipse-technologies-llc-aperture/eclipse-aperture.xml
- Changelog JSON feed: https://verifymcp.io/servers/cyan-eclipse-technologies-llc-aperture/eclipse-aperture.json
- HTML version of this page: https://verifymcp.io/servers/cyan-eclipse-technologies-llc-aperture/eclipse-aperture