Eclipse Aperture MCP
Related Servers
Alternatives to Eclipse Aperture MCP
No user-submitted related servers found.
Related Servers
- AlicenseBqualityAmaintenanceEnables canonical social content packages to be ingested, adapted into platform-native variants with classified diffs, and bound to hash-verified owner approvals. It also evaluates engagement policy, tracks accounts and kill switches, and records hash-chained receipts without performing platform actions or network calls.15MIT
- FlicenseNot gradedqualityBmaintenanceEnables publishing and managing organic Facebook Page and Instagram content directly through Meta's Graph API without paid third-party services.-
- AlicenseBqualityBmaintenanceEnables reading, publishing, commenting on, and analyzing Instagram Business/Creator accounts through the official Graph API, with multi-account support and an optional self-hosted publishing panel.29MIT
- AlicenseNot gradedqualityBmaintenanceConnects AI apps to your own Instagram professional account through Instagram's official API for reading stats, posts, comments and DMs, auditing accounts, checking reels, replying to comments and messages, and publishing or scheduling posts. Actions are previewed for approval before anything is posted, sent, hidden, or deleted.MIT
- AlicenseAqualityCmaintenanceEnables publishing photos, reels, and stories to Instagram, reading and moderating comments, fetching performance insights, drafting captions via MCP sampling, and scheduling reels for later.138 npmMIT
- FlicenseNot gradedqualityCmaintenanceEnables automated creation and publishing of branded Instagram and Facebook posts, with topic management, typeset image rendering, and social media publishing via the Meta Graph API.-
TDQS
Scored across 4 tools
Each tool targets a distinct stage: capability probing, variant construction, previewing, and receipt listing. There is minor overlap because variant_build and preview_pack both surface diffs and hashes, which could make an agent pause over which output is authoritative.
Names are consistently snake_case and mostly follow an object_action pattern: capability_probe, variant_build, receipt_list. preview_pack is slightly less natural but still readable and within the same convention.
Four tools is well-scoped for this narrow v0.1 formalization workflow. Each tool represents a distinct step and none appears redundant.
The surface covers probing, building, previewing, and listing receipts, but there is no exposed tool for managing canonical content packages or recording an approval/receipt action. The mention that previews expose hashes an approval would bind highlights a notable lifecycle gap.