Eclipse Greenwash
Emission-time claim binder for agent output over a fixture emission stream; local/fixture only. PASS-CONDITIONAL (local/fixture) — every sustainability claim an agent emits is bound to its source-data pointer at emission time; unbound claims are flagged in the message itself. A binding proves a pointer existed and resolved at emission time — NOT that the claim is true. Rollback fence: an external anchor is required before live/multi-party use. Counsel gate (SPEC §10) named and unbuilt.
status: in-developmentclass: mcpCompliance & RegulationTrust & Receipts
Vendor: Cyan Eclipse Technologies
What it does
- Novel mechanism (SPEC §2.1, verbatim) — every sustainability claim an agent emits is bound to its source-data pointer at emission time; unbound claims are flagged in the message itself.
- The pointer limit (SPEC §11.2, verbatim, on every surface): A binding proves a source-data pointer existed and resolved at emission time — NOT that the claim is true, not that the source data supports the claim, and not that the source data is accurate, current, or complete. A flag states the absence of a pointer at emission — never that a flagged claim is false. Greenwash flags; it does not censor: flagged claims are emitted with their text unaltered.
- Decisive fixture F-G14 stands from the bench record — a harness-authored stream with harness-authored source entries verifies in a fresh subprocess from the pack + keys alone: bound claims resolve in the emission-time snapshot, both unbound claims carry in-message flags. A pointer attached after emission is a downgraded annotation (binding: false on its face), never a binding; annotations never convert a flag, never edit an emitted message, and are rejected by the §6.4 verifier as bindings. Sub-range packs are labelled verifiable: false / downgraded: true on their face (genesis-anchor reason) — exports that cannot be recomputed are labelled downgraded, never upgraded.
- Delta re-bench of v0.1.1 (wave4/rebench-greenwash.md): defects D-GW-1..4 all CLOSED on independent fixtures; conditions C1–C4 satisfied (C1/C3/C4 as implemented — claim_id uniqueness enforced at emission via the accepted coined code DUPLICATE_CLAIM_ID, LEDGER_APPEND_FAILED as a literal typed refusal, both binding signatures over record_hash; C2 via the labelling branch). No new defect found; builder suite 34/34 re-run by the bencher.
- Rollback fence: the v0.1 store is pure local file state anchored by its signed store head and SET anchors — any verdict caps at PASS-CONDITIONAL (local/fixture); an external anchor is required before any live or multi-party use.
- Counsel gate (SPEC §10) — named, unbuilt: binding, flagging, or certifying claims in real published content — marketing, product pages, regulatory filings, ESG reports — is out of v0.1, hard, until counsel clears that use (packet covers FTC Green Guides, SEC climate/ESG disclosure rules, EU green-claims regime; disclosure-duty and defamation/disparagement exposure of in-message flags; the legal meaning that may attach to the word "bound"). There is no dormant live path in v0.1.1 to flip: the startup fence refuses non-local endpoints, channel/publication integration strings, live source-data keys, and non-fixture modes by name.
- Signing is an HMAC fixture stand-in for Herald RS256, disclosed on every artifact face as signature_scheme; verification keys are pinned out-of-band by fixed key ref. Herald (signing pattern), Meter (metering grammar), Till (mandates — v0.1 fixtures run mandate-free), and Docket (pack shape) are consumed by grammar/reference only. Source-data stores are consumed as pointer targets, never assessed: resolution means only that the named entry exists in the cited snapshot.
Tools
emission_submit · claim_status · ledger_get · binding_verify · pack_get · annotation_add
Platforms
- MCP over stdio
Certification
Bench verdict: PASS-CONDITIONAL (local/fixture)
Certified scope: Eclipse Greenwash — PASS-CONDITIONAL (local/fixture) — Verity bench of v0.1.0 (2026-10-27, argus101-program-20261027/wave4/bench-greenwash.md) PASS-CONDITIONAL with conditions C1–C4, + delta re-bench of v0.1.1 (argus101-program-20261027/wave4/rebench-greenwash.md): defects D-GW-1..4 all CLOSED, conditions C1–C4 satisfied (C2 via the labelling branch), builder suite 34/34 re-run by the bencher at commit ba07801, no new defect found. PASS-CONDITIONAL (local/fixture) is not CERTIFIED — certified is false, and nothing beyond that verdict at its exact scope is claimed. Scope is exactly: local stdio, fixture emission stream with structured claim objects only, value_class "test"; no real agent, channel, publication, or marketing surface is touched, and no free-text claim detection in arbitrary prose is claimed or implied. Pointer limit: a binding proves a source-data pointer existed and resolved at emission time — NOT that the claim is true, not that the source data supports the claim, and not that the source data is accurate, current, or complete. Rollback fence: pure local file store caps any verdict at PASS-CONDITIONAL (local/fixture) — external anchor required before live/multi-party use. Counsel gate (SPEC §10) named and unbuilt for any real-world claim publication. Trademark screen on the working name pending.
Not tested:
- Real published content — binding, flagging, or certifying claims in real marketing, product pages, regulatory filings, or ESG reports is SPEC §10 counsel-gated and UNBUILT (FTC Green Guides, SEC climate/ESG rules, EU green-claims regime; flag defamation/disparagement exposure); no real publication is touched in v0.1.1
- Claim truth — a binding proves a pointer existed and resolved at emission time, NOT that the claim is true, supported, accurate, current, or complete; source-data stores are consumed as pointer targets, never assessed
- Free-text claim detection in arbitrary prose — v0.1.1 handles structured claim objects in a fixture emission stream only; no prose detection is claimed or implied
- External anchoring / multi-party reliance — the pure local file store caps any verdict at PASS-CONDITIONAL (local/fixture); an external anchor is required before live or multi-party use
- Production key custody — signing is an HMAC fixture stand-in for Herald RS256 (fixture keys in keys/, gitignored, mode 600); a live phase would need real Herald signing and a re-bench
Live state note: Bench evidence: argus101-program-20261027/wave4/bench-greenwash.md (Verity bench of v0.1.0, PASS-CONDITIONAL (local/fixture), conditions C1–C4, decisive F-G14 fresh-subprocess verification) + argus101-program-20261027/wave4/rebench-greenwash.md (Verity delta re-bench of v0.1.1: D-GW-1..4 all CLOSED, C1–C4 satisfied, builder suite 34/34 re-run by the bencher). No test-bench scorecard was issued for this verdict and none is claimed (scorecard_ref/card_url null).
Pricing
PRICED — $0.10/claim, via the Eclipse Bazaar bench-order/intake path only. No checkout, payment, or buy-now link exists for this product, and no Stripe object exists for it in this pass: intake orders are reviewed and confirmed by the operator before any payment link is sent. Metering shape per SPEC §9 (metering points only in v0.1.1, no charge path built): Meter-grammar records at exactly three points — claim_bound, claim_flagged, pack_exported — at the $0.10/claim price shape (book reference only). No charge path is built, no payment is taken, and no live Meter ingest is claimed. The local package is the reference implementation. Repository is PRIVATE.
Install / verify
No install command is published for this product in the catalog or its registry record.
Official MCP Registry name: io.github.CYAN-ECLIPSE-TECHNOLOGIES-LLC/eclipse-greenwash-mcp
Registry listing: https://registry.modelcontextprotocol.io/v0.1/servers/io.github.CYAN-ECLIPSE-TECHNOLOGIES-LLC%2Feclipse-greenwash-mcp/versions/0.1.1
Repository: https://github.com/CYAN-ECLIPSE-TECHNOLOGIES-LLC/eclipse-greenwash-mcp
Verify any MCP server in your client configs against this catalog with bazaar check (Eclipse Bazaar MCP / CLI — see llms.txt).