Eclipse Zephyr MCP
The Bluesky adapter: real public reads over the open AT Protocol, with review-first and house caps fully in force. No posting surface exists in v0.1.
status: in-developmentclass: mcpSocial Adapter / Bluesky (AT Protocol)
Vendor: Cyan Eclipse Technologies
What it does
- Real public reads over the AT Protocol public API, no auth: profile, actor search, author feed, thread reads
- Normalized output with per-item source endpoints
- Every read receipted into a hash-chained ledger — failed reads receipted as errors
- No write tools exist (surface asserted by test)
- CERTIFIED(live-read): the catalog's first live scope, earned under independent bench drive
Tools
profile_read · actor_search · author_feed_read · post_thread_read · receipt_list
Platforms
- MCP over stdio (HTTP transport on roadmap)
Certification
Bench verdict: CERTIFIED(live-read)
Certified scope: CERTIFIED(live-read) — Eclipse Bazaar Test Bench 2026-10-25, 12/13 checks pass, 1 na (U1 auth: stdio process boundary). Run by W-003 (Verity), suites/zephyr.py. Standing card is run 2 (-2.json); run 1 FAILED is retained in results/ — its Z5 failure was a defect in this bench probe (the tamper set a receipt field to its existing value, a no-op the verifier correctly accepted), fixed and disclosed here; no product defect.
Not tested:
- Posting / record staging (bsky_record_stage, bsky_thread_verify, bsky_label_preflight) — not built; owner account is a Wave-2 gate.
- COMMUNITY_API_PILOT — spec-eligible for Zephyr only after S2, a dated terms record, and separate owner enable; not built, not enabled.
Bench scorecard (evidence): https://eclipsebazaar.com/cards/eclipse-zephyr-mcp-2026-10-25-2.json
Pricing
Free local v0.1; hosted tier TBD per spec
Install / verify
docker run -i ghcr.io/cyan-eclipse-technologies-llc/eclipse-zephyr-mcp:latest
Verify any MCP server in your client configs against this catalog with bazaar check (Eclipse Bazaar MCP / CLI — see llms.txt).