Eclipse Aperture MCP
PYPI · ECLIPSE-APERTURE
The Instagram adapter, formalized: capability-declared, hash-bound native variants for Feed
Available components
Last scanned (18 hours ago)
Scores higher than 65% of PyPI servers
Category Marketing and SEO
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. How we score → Why this is hard to score →
Supply Chain Security100
- No malware found by supply-chain analysis.Pass
- No known CVEs affecting this package version or its production dependencies.Pass
- Runs hatchling.build at install time, a recognised build step with no custom scripting around it. View diagnostics → Pass
- No production dependencies, so there is no dependency health to assess. View diagnostics → Pass
Provenance & Transparency71
- Repository check failed: the declared repository URL redirects; it must resolve directly. See how to fix → View diagnostics → Fail
- Cryptographically verified build provenance (signed, bound to CYAN-ECLIPSE-TECHNOLOGIES-LLC/eclipse-aperture-mcp). View diagnostics → Pass
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 7 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability60
- AI-judged instruction clarity (fair).Partial
- Tool/resource definitions use about 269 tokens (~67/item across 4 items; 4 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management0
- Stability not yet verified: not enough scan history yet (needs a 30-day window).Unverified
Tool Coverage67
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 0% of tool parameters carry a description.Fail
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 4 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 4 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
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.
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 29 Oct 26 −6
- Source repository: pass → fail ▼ security
- 28 Oct 26 +15
- Malware scan: unverified → pass ▲ security
- 27 Oct 26 61
First indexed and scored.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 4 Nov 2026 · Analysed pypi/eclipse-aperture@0.1.0
Provenance Verified
A signed build attestation was found and verified, binding this exact artifact to the source repository it claims to come from.
| Result | Verified |
|---|---|
| Ecosystem | pypi |
| Reason | Verified |
| Discovered via | Registry attestation endpoint |
| Source repo | CYAN-ECLIPSE-TECHNOLOGIES-LLC/eclipse-aperture-mcp |
| Certificate issuer | https://token.actions.githubusercontent.com |
| Certificate SAN | https://github.com/CYAN-ECLIPSE-TECHNOLOGIES-LLC/eclipse-aperture-mcp/.github/workflows/publish-pypi.yml@refs/tags/v0.1.0 |
| Rekor log index | 3517909332 |
| Predicate type | PyPI publish attestation https://docs.pypi.org/attestations/publish/v1 |
| Subject digest | sha256:4b5092a6521800900d97a3a7471c5b82d8580d149ea5f3e18bdbaa756ab45584 |
Background: How many MCP packages publish verified provenance →
Install scripts 1 script
| Hook | Tier | Command |
|---|---|---|
| build_backend | allowlisted | hatchling.build |
Background: Why install scripts are a supply-chain risk →
Dependencies 0 packages
| Packages resolved | 0 |
|---|---|
| Tree resolution | Complete |
Background: SBOMs and build attestations, explained →
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
capability_probe ~91
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.
| Name | Type | Req | Description |
|---|---|---|---|
| simulate_probe_failure | boolean | – | – |
No output schema declared.
No examples provided.
preview_pack ~47
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.
| Name | Type | Req | Description |
|---|---|---|---|
| variant_id | string | yes | – |
No output schema declared.
No examples provided.
receipt_list ~22
The append-only, hash-chained receipt ledger, with chain verification.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
variant_build ~109
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.
| Name | Type | Req | Description |
|---|---|---|---|
| account_id | string | – | – |
| package | object | yes | – |
| surface | string | – | – |
No output schema declared.
No examples provided.
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.
pypi · eclipse-aperture
claude mcp add cyan-eclipse-technologies-llc-aperture -- uvx eclipse-aperture
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.