Vendor: Cyan Eclipse Technologies · Platforms: MCP over stdio (HTTP transport on roadmap)
Certification scope
CERTIFIED(local) — Eclipse Bazaar Test Bench 2026-10-26, 23 pass, 1 na of 24 checks (U1 auth: stdio process boundary). Run by W-003 (Verity), suites/census.py. Run 2 is the standing card; run 1 FAILED card is retained append-only. N-CHECK: NOVELTY_PROVEN — the render path itself enforces discovery law: an item that cannot cite a receipted discovery event cannot render, and source claims stay attributed per source and are never promoted to Census fields.
What it does
- Agent discovery and inventory of record from authorized sources only, with a per-source authorization record carried through the inventory
- Receipt-chained discovery events {source, method, observed_at, observer}; the render path refuses any item that cannot cite its discovery event
- Discovered-unregistered (shadow) agents are a reconciliation state, never an accusation; stale items render with last-seen instead of disappearing
- Mandatory coverage in every export — sources authorized, available-but-unauthorized, and not yet adapted; suppressing the gap section refuses by name and is receipted
- Source-native claims stay attributed per source and are never promoted to Census fields; reconciliation is propose-only until a named human accepts. v0.1 is local over fixture sources; tenant connectors are gated and not built
Tools
census_sourcescensus_discovercensus_listcensus_getcensus_shadowcensus_reconcilecensus_exportcensus_diffreceipt_listreceipt_verify
Problems it addresses
- I need an inventory of agents that only includes systems discovered from authorized sources
- A vendor export gives every agent a risk score, but I need source claims kept separate from inventory truth
- I need coverage gaps and stale agents shown instead of a false claim of completeness
Not tested
- Tenant connectors (Microsoft Entra Agent ID, Google, cloud agent services) — NOT built. Gate N1: each adapter requires the customer's admin authorization record per tenant plus owner approval. Those families render in every coverage section as available-but-unauthorized.
- Endpoint / manifest collectors and any network discovery — held by spec §7.7 (later phase, own spec). Discovery of systems the customer does not administer is T3-permanent: no probe/scan/enumerate capability exists in this package and there is no network code in v0.
- CETech fleet live dogfood export (§7.6/§15) — a CETech-fleet SEED FIXTURE ships as dogfood-shaped data; the standing live fleet inventory export as the first real Census artifact follows the dogfood loop after bench, and is not claimed from this build.
- Hosted / multi-tenant operation and auth beyond the stdio process boundary.
Bench scorecard: test-bench/results/eclipse-census-mcp-2026-10-26-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 →