Cyan Eclipse Darkseal
OfficialDarkseal is a free MCP server that seals a flow's traversal-start default selections from the executing surface and diffs them against the principal's charge/binding artifacts to mint a recomputable pres election verdict.
Seal default-state vectors element by element from an executing surface's witness module, rejecting bundles from other sources on provenance.
Diff confirmation/charge artifact digests against sealed defaults to produce verdicts naming pre-selected elements that caused charges or binding terms.
Retrieve the full verdict record, including verdict class, charged element names, grammar version, coverage statement, and receipt refs.
Get a counterparty view showing only the verdict class and names of charged elements.
Recompute a verdict offline from an exported capture, grammar version, and outcome artifacts with no service state.
Export a sealed capture with its receipt-chain head for independent recomputation.
Use every operation free at every tier, with no metering or paid wording changes.
Click on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@Cyan Eclipse Darkseal seal this checkout's default state, then diff it against my receipt"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
Cyan Eclipse Darkseal
Powered by Cyan Eclipse Technologies — https://cetech.ai
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 |
| Seal a traversal-start default-state vector from the executing surface's witness module. Free. |
| Diff the principal's own confirmation/charge artifacts against the sealed defaults and mint the verdict. Free. |
| The full verdict record: verdict, charged element names, grammar version, coverage statement, receipt refs. Free. |
| Counterparty view: verdict class and the names of charged elements only. Free. |
| Recompute a verdict from an exported capture + the grammar version + the outcome artifacts, with no service state. Free. |
| 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 stdioEnvironment: 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 toolsdarkseal_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
Scored across 6 tools
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.
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.
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.
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
Related MCP Connectors
Durable commitment lifecycle, verification, governance and recovery layer for agentic commerce.
Pre-execution policy gate for consequential agent actions with durable trust receipts.
Your agent carries its own resume — outcome receipts minted at settlement, held by the agent.
Policy-aware AI execution, verification, cost, and trajectory evidence for agents.
Related MCP Servers
- FlicenseNot gradedqualityDmaintenanceEnables AI agents to create intent contracts, check boundaries, record completions, and export receipts for structured agent workflows-
- AlicenseNot gradedqualityCmaintenanceEnables step-debugging, deterministic replay, and signed audit evidence for AI agents, compliant with EU AI Act.79 PyPIMIT
- AlicenseNot gradedqualityBmaintenanceEnables transparent MCP proxying with a hash-chained effect ledger, classifying agent actions by reversibility, enforcing approval gates, and dry-run previews of sessions.MIT
- AlicenseNot gradedqualityBmaintenanceEnables deterministic verification of AI agent decisions and actions, providing PASS/FAIL/ABSTAIN verdicts with replayable proofs and an optional signed receipt ledger.4 npmApache 2.0