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

Eclipse Genesis

Agent birth-certificate issuer — at registration the agent's creator, model, config hash, and declared purpose scope are sealed; acting outside the declared purpose is detectable by any counterparty who checks the certificate. PASS-CONDITIONAL(local/fixture) — local stdio, fixture agents/creators/keys only, value_class "test"; Genesis detects, it never blocks. Sole condition: full coordinated rollback is a fenced condition — external anchor required before live/multi-party use.

status: in-developmentclass: mcpIdentity & AttestationTrust & Receipts

Vendor: Cyan Eclipse Technologies

What it does

Tools

genesis_certificate_register · genesis_certificate_amend · genesis_certificate_revoke · genesis_certificate_get · genesis_certificate_verify · genesis_purpose_detect · genesis_certificate_export · genesis_family_list · genesis_metering_read

Platforms

Certification

Bench verdict: PASS-CONDITIONAL(local/fixture)

Certified scope: PASS-CONDITIONAL(local/fixture) — Verity bench of v0.1.0 (2026-10-27, argus101-program-20261027/wave3/bench-genesis.md): builder suite 43/43 re-run clean by the bencher; decisive fixture F-G13 independently re-derived from the bencher's own corpus and bencher-generated keys — registration agent_ref matched the bencher-predicted mint, exported certificate / seed prev_hash / creator + witness signatures / export head anchor all recompute under bencher code, fresh-process verify from export + pinned keys alone returned SEAL_VALID, and detection over the bencher's 5 actions reproduced exactly [IN_PURPOSE, IN_PURPOSE, IN_PURPOSE, OUT_OF_PURPOSE, INDETERMINATE] with the out-of-purpose record naming clause action_types and the indeterminate record naming reason unmapped, never coerced. PASS-CONDITIONAL is not CERTIFIED — certified is false, and nothing beyond this scope is claimed. Scope is exactly: local stdio, fixture agents/creators/keys, fixture Docket/Meter-grammar action records, value_class "test"; no live registry, no third-party reliance, no enforcement use. Sole condition (verbatim): cross-artifact cross-commitment — full coordinated rollback = fenced condition — external anchor required before live/multi-party use. Genesis detects, it never blocks: no blocking/enforcement verb exists on either surface (dispatch enumeration by the bencher).

Not tested:

  • Live registry reliance — SPEC §10 counsel gate (named, unbuilt): a real registry accepting real registrations, certificates presented to third parties for reliance, detection records used in disputes, enforcement, or platform decisions, or any "registered agent" claim towards regulated buyers requires counsel review before build (claim language, declaration-warranty/liability, creator-identity data posture, retention/takedown). v0.1.0 contains no dormant live path, no dormant enforcement/blocking verb, and no config flip that turns this build live; the startup fence refuses live-registry / non-local config (CONFIG_FENCE_REFUSED). Genesis DETECTS, NEVER BLOCKS — this listing does not imply any blocking or enforcement capability.
  • Sole condition (verbatim from the bench record): full coordinated rollback is a fenced condition — external anchor required before live/multi-party use. The local stream seed anchor + witness-signed export head anchor are implemented and verified, but no external/cross-artifact anchor exists.
  • Live Herald signing — v0.1.0 signing is an HMAC fixture stand-in for Herald RS256, disclosed on the product's face; a live phase (counsel-gated, SPEC §10) would need real Herald signing and a re-bench. Verification keys are pinned out-of-band by fixed ref from the local key file only; a record-supplied key is never read (UNKNOWN_FIELD refusal).
  • Production key custody — fixture keys live in keys/fixture-keys.json (chmod 600, gitignored, never committed; GitHub contents/keys verified 404); a fresh clone must supply its own fixture key file to run the full suite.
  • Hosted or live operation / charge path — local stdio only; metering records only per SPEC §9 (registration = exactly 1 zero-value FREE record; verify/detect receipts carry the $0.05/verification-shape meter record inside the signed receipt; a BROKEN verify still meters because the issuance happened; tool refusals never meter); no charge path, payment call, entitlement check, or live Meter ingest is built or claimed.

Live state note: Bench evidence: argus101-program-20261027/wave3/bench-genesis.md (Verity bench of v0.1.0, 2026-10-27; builder suite re-run clean-state 43/43, F-G13 independently re-derived with bencher corpus/keys, detects-never-blocks dispatch enumeration, metering partition probed). No test-bench scorecard was issued for this verdict and none is claimed (scorecard_ref/card_url null). Repository PUBLIC (free-tier policy, Benchkit precedent): https://github.com/CYAN-ECLIPSE-TECHNOLOGIES-LLC/eclipse-genesis-mcp @ v0.1.0. Official MCP Registry: io.github.CYAN-ECLIPSE-TECHNOLOGIES-LLC/eclipse-genesis-mcp v0.1.0, status active, isLatest true.

Pricing

FREE — free local v0.1.0; registration is FREE and emits exactly 1 zero-value FREE Meter record (amount_minor: 0), so the funnel is counted. Verification-class issuances carry a $0.05/verification metering shape, 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 honesty per SPEC §9 / bench: verify and detect receipts carry the $0.05-shape meter record inside the signed receipt; a BROKEN verify still meters (the issuance happened); tool refusals never meter; no charge path, payment call, or entitlement check is built. The local package is the reference implementation. Repository is PUBLIC (free-tier policy, Benchkit precedent).

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-genesis-mcp

Registry listing: https://registry.modelcontextprotocol.io/v0.1/servers/io.github.CYAN-ECLIPSE-TECHNOLOGIES-LLC%2Feclipse-genesis-mcp/versions/0.1.0

Repository: https://github.com/CYAN-ECLIPSE-TECHNOLOGIES-LLC/eclipse-genesis-mcp

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