Cyan Eclipse Zephyr MCP — Cyan Eclipse Bazaar

Vendor: Cyan Eclipse Technologies · Platforms: MCP over stdio (HTTP transport on roadmap)

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

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_readactor_searchauthor_feed_readpost_thread_readreceipt_list

Problems it addresses

I need Bluesky reads inside the same governed workflow as my other channels
Failed lookups belong on the audit record too

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: test-bench/results/eclipse-zephyr-mcp-2026-10-25-2.json

Evaluation-intake listing

This listing records the tool's place in the Bazaar's evaluation and monitoring pipeline, with the evidence gathered so far printed above — verdict, scope, and not-tested items included. It is not sold on this site, and its presence in the catalog is not a claim beyond that evidence. The service behind every verdict is the bench: what a bench run buys →