Skip to main content
Glama

Cyan Eclipse Darkseal

Powered by Cyan Eclipse Technologies — https://cetech.ai

Cyan Eclipse Darkseal icon

Icon: branding/icon.svg — v3, owner-elected 2026-11-12 (Tap 45). Icongate PASS: legible at 48 px and 32 px (cap 4.94 px @48 · 3.29 px @32).

Darkseal seals the state the flow started in — every pre-ticked add-on, pre-chosen plan, and continuity toggle, element by element — at the moment your agent entered it. If a charge began as a default you never chose, the sealed record names the element it began as, and anyone can recompute the verdict from the record itself.

Cyan Eclipse Darkseal is a Model Context Protocol (MCP) server. It witnesses the default state of agent-traversed flows from the buyer's side of the seam: the capture happens in the executing surface — the buying agent's own runtime, or a Checkout-Hands-class surface — at traversal start, before any principal or agent action. The sealed vector is diffed against the charges and terms that resulted, from the principal's own confirmation and charge artifacts, held as digests.

Verdicts, from a fixed grammar:

  • PRESELECTED-AND-CHARGED — names the pre-selected elements that produced charges or binding terms.

  • PRESELECTED-NOT-CHARGED — defaults were sealed; no resulting charge or term appears in the principal's artifacts.

  • NO-PRESELECTION — no grammar-covered element was pre-selected in the rendered flow.

  • UNVERIFIABLE — the capture is below the capture standard; a state of the evidence, never any party's fault.

The element grammar (GRAMMAR.md, darkseal-grammar/1) covers four classes in v1: checkboxes, toggles, radio/plan selectors, and continuity switches. Elements outside the grammar are named in the capture's coverage statement and never judged. A checkout flow whose pre-selected elements are all checkbox add-on defaults is a sibling product's object — the record is marked UPSELLSEAL-OBJECT and Darkseal mints no duplicate whole-flow verdict for it.

Darkseal is a witness, not an auditor and not a notary: it accepts captures only from the executing surface's own witness module — bundles submitted by any other party are rejected on provenance — and it renders no finding about what any person saw, understood, or agreed to. The record names the state the flow started in and what that state produced. Nothing more.

Tools

Tool

What it does

darkseal_seal_defaults

Seal a traversal-start default-state vector from the executing surface's witness module. Free.

darkseal_diff_outcome

Diff the principal's own confirmation/charge artifacts against the sealed defaults and mint the verdict. Free.

darkseal_get_verdict

The full verdict record: verdict, charged element names, grammar version, coverage statement, receipt refs. Free.

darkseal_check

Counterparty view: verdict class and the names of charged elements only. Free.

darkseal_recompute

Recompute a verdict from an exported capture + the grammar version + the outcome artifacts, with no service state. Free.

darkseal_export_captures

Export a sealed capture with the receipt-chain head for independent recomputation. Free.

The check is free at every tier — there is no metering anywhere in this product, and no paid tier changes verdict wording.

Related MCP server: agent-replay-debugger-mcp

Custody

The store carries only the sealed element field set: element class and identity as presented, default state as rendered, flow identity, timestamps, seals, outcome-artifact digests, and the verdict with its named grammar basis. Form-field values are never captured, held, or sealed — Darkseal seals default states, not inputs. No page bodies beyond the grammar-named elements, no browsing history, no principal profile. Records serve the principal whose side sealed them; there is no cross-principal aggregation surface. Every capture and verdict appends one record to a hash-chained receipt journal, verified at load; a store that fails verification fails closed.

Status

v0.1.0 · built · bench-pending (independent bench requested; builder tests are not a bench verdict) · name "Cyan Eclipse Darkseal" is provisional pending trademark screen · not listed, not offered for sale — review-first standing posture.

Run

python3 server.py   # MCP over stdio

Environment: ECLIPSE_DARKSEAL_STATE (record store path), ECLIPSE_DARKSEAL_SURFACE_KEYS (executing-surface channel keys, JSON — surface-held in production; the keys in keys/ are test fixtures only).

License

MIT — see LICENSE.

Available Tools

6 tools
darkseal_checkC

Counterparty view: the verdict class and the names of charged elements only. The check is free.

Inputs: capture_id (required).

darkseal_diff_outcomeB

Diff the principal's own confirmation and charge artifacts (held as digests) against the sealed defaults and mint the verdict: a charge or binding term that began as a sealed pre-selected element verdicts PRESELECTED-AND-CHARGED naming that element. The check is free.

Inputs: capture_id (required), outcome_artifacts (required).

darkseal_export_capturesB

Export a sealed capture (element states + seal) with the receipt chain head and grammar version, for independent recomputation. The check is free.

Inputs: capture_id (required).

darkseal_get_verdictC

The full verdict record for a capture: verdict, charged element names, grammar version, coverage statement, separation marker, receipt refs. The check is free.

Inputs: capture_id (required).

darkseal_recomputeB

Recompute a verdict from an exported capture plus the element grammar version plus the outcome artifacts, with no service state. The check is free.

Inputs: capture (required), grammar_version (required), outcome_artifacts (required).

darkseal_seal_defaultsC

Seal a flow's default-state vector element by element at traversal start, as captured by the executing surface's own witness module: element class, identity as presented, and default state as rendered, across checkboxes, toggles, radio/plan selectors, and continuity switches. Bundles from any non-executing source are rejected on provenance. The check is free. Darkseal seals the state the flow started in — every pre-ticked add-on, pre-chosen plan, and continuity toggle, element by element — at the moment your agent entered it. If a charge began as a default you never chose, the sealed record names the element it began as, and anyone can recompute the verdict from the record itself.

Inputs: source (required), flow_id (required), elements (required), surface_id (required), +4 more.

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

Loading tool schema changelog…

    TDQS

    B3.2/5.0

    Scored across 6 tools

    Disambiguation3/5

    The capture-side tools (seal_defaults, export_captures) are distinct, but four of six tools (diff_outcome, get_verdict, check, recompute) all revolve around producing or reading a verdict. The descriptions differentiate them (mint vs. full record vs. counterparty-limited view vs. stateless recompute), but the boundaries are subtle and an agent could easily pick 'check' when it needs 'get_verdict' or vice versa.

    Naming Consistency4/5

    All names share the darkseal_ prefix in snake_case, and most follow a verb_noun shape (seal_defaults, diff_outcome, get_verdict, export_captures). The bare 'check' and 'recompute' break the noun pattern slightly, but the set is otherwise predictable.

    Tool Count5/5

    Six tools is well-scoped for a seal-and-verdict protocol: capture, diff, retrieve, counterparty view, recompute, export. Each appears to earn its place with no filler.

    Completeness4/5

    The surface covers the full lifecycle from sealing defaults through verdict minting, retrieval, counterparty disclosure, independent recomputation, and export. Minor gaps exist (no listing/enumeration of existing captures and no revocation or deletion of a seal), but core workflows are covered.

    Maintenance

    ActivityMaintained
    ResponsivenessNo recent community issues

    Related MCP Connectors

    Related MCP Servers