Eclipse Bazaar · products.json · verdicts.json · llms.txt

Eclipse Environment MCP

The smart-environment module — scopes an agent's authority to actuate a home, tier by tier, and receipts only what the device itself confirms.

status: in-developmentclass: mcpSmart Environment / Physical-Actuation Governance

Vendor: Cyan Eclipse Technologies

What it does

Tools

registry_list · state_snapshot · policy_evaluate · command_execute · receipt_list

Platforms

Certification

Bench verdict: CERTIFIED(simulator)

Certified scope: CERTIFIED(simulator) — Eclipse Bazaar Test Bench 2026-10-25, 14/15 checks pass, 1 na (U1 auth: stdio process boundary). Run by W-003 (Verity), suites/environment.py.

Not tested:

  • A real Home Assistant instance — v0.1's hub is a local HA-shaped stub (stdlib http, fixtures). The wrapper's client speaks the /api/states + /api/services shape, but parity with real HA behavior (auth, service payloads, state semantics) is [verify] and untested; connecting the owner's instance is a Wave-2 owner-gated step.
  • Tier 2 / Tier 3 EXECUTION — by phase design v0.1 evaluates both and denies by phase; the Tier 2 receipt + owner-notification wiring and any Tier 3 execution path are unbuilt, so there is nothing to test yet.
  • Vehicle rails (Smartcar, Tesla Fleet API) — designed in the Procure concept doc's Environment module; no adapter exists in v0.1.
  • Real-home scale and latency — fixture hub carries 7 entities; nothing about a real home's entity count, hub latency, or state churn has been measured.

Bench scorecard (evidence): https://eclipsebazaar.com/cards/eclipse-environment-mcp-2026-10-25.json

Pricing

Free local v0.1; hosted tier TBD per spec

Install / verify

docker run -i ghcr.io/cyan-eclipse-technologies-llc/eclipse-environment-mcp:latest

Verify any MCP server in your client configs against this catalog with bazaar check (Eclipse Bazaar MCP / CLI — see llms.txt).