Cyan Eclipse Darkseal
OfficialRelated Servers
Alternatives to Cyan Eclipse Darkseal
No user-submitted related servers found.
Related Servers
- AlicenseBqualityBmaintenanceEnables principals to seal granted scopes at connect time, capture scopes exercised by their own agent runtime, and mint verdicts that identify out-of-scope use, renewal scope expansion, or unverifiable evidence without enforcing or blocking calls.7MIT
- AlicenseNot gradedqualityCmaintenanceEnables step-debugging, deterministic replay, and signed audit evidence for AI agents, compliant with EU AI Act.79 PyPIMIT
- AlicenseNot gradedqualityBmaintenanceEnables capturing a tamper-evident, hash-chained local record of every AI agent tool call — both the decision before a tool runs and its outcome — so you can review what the agent actually did in order, detect edits, deletions, or reordering at the exact index, and export a signed evidence pack any third party can verify with no installs.2MIT
- 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
- FlicenseNot gradedqualityDmaintenanceEnables AI agents to create intent contracts, check boundaries, record completions, and export receipts for structured agent workflows-
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.