
Cyan Eclipse Basketseal
One question, answered with a receipt: what was in the basket? Basketseal seals a checkout basket as presented and recomputes its charged total from its own sealed components — v0.1.0, fixture scope.
status: liveclass: mcpTrust & ReceiptsAgent Commerce
Vendor: Cyan Eclipse Technologies
What it does
- Seals a checkout basket exactly as presented at a first-party surface — components in presentation order, amounts as decimal strings exactly as presented (JSON numbers refused, so no float normalization ever occurs), line descriptions hash-sealed with their class in clear
- Recomputes the charged total from the sealed components alone under the basket's own stated rounding discipline (per-line / per-total / stated precision), naming the outcome in a closed grammar: RECOMPUTES, MISCOMPUTES (per-component diff class and amount), or UNWITNESSED (no first-party capture record; no verdict issued)
- A standalone verifier — an independent re-implementation sharing no code with the core — re-derives the verdict offline from an exported bundle, with no service state
- Verdict issuance is gated by the deployed Cyan Eclipse License Server; the licence leg is proven live at fixture scope across no-licence / valid / revoked states, revocation honoured in real time
- Honest scope — one artifact, one question: Basketseal never evaluates a payment or a surcharge rule, never compares a basket against a second artifact, and never sits in a checkout path; sibling shapes are refused byte-identically
Tools
basketseal_seal_basket · basketseal_get_record · basketseal_check · basketseal_recompute · basketseal_export_record
Platforms
- MCP over stdio
- MCP over HTTP
Certification
Bench verdict: PASS (fixture scope) — cure delta, 2026-11-15
Certified scope: First bench (2026-11-15): FAIL on BK-B3 / F-1 (HIGH — record_id collision: distinct baskets with identical arithmetic shared an id and the second seal silently overwrote the first), with F-2 (MED), F-3 (MED), F-4 (LOW) also recorded; all other claims passed. Cure: four commits, one per finding, each with named regression tests failing pre-cure and passing post-cure. Cure-delta verdict (2026-11-15): PASS at fixture scope, 48 of 48 probes; combined with the standing PASS claims of the first bench, no claim in the v0.1.0 fixture-scope filing is left failed. A bench PASS at fixture scope is not a certification and not a production-scope claim.
Not tested:
- Production scope — v0.1.0 is built and benched at fixture scope only; no live checkout surface has been witnessed
- Hosted deployment — no hosted endpoint exists or is claimed; the server runs where an operator runs it
- Per-op charging — no price has been adopted for this product and no charge path exists in v0.1.0
Live state note: Shipped 2026-11-16: repository public with the v0.1.0 release (GitHub); licence leg proven live against the deployed License Server at fixture scope.
Pricing
No price adopted. v0.1.0 ships at fixture scope; metering follows the PC-4 pattern (event class and count only, never basket content) and no charge path exists in this version.
Install / verify
No install command is published for this product in the catalog or its registry record.
Repository: https://github.com/CYAN-ECLIPSE-TECHNOLOGIES-LLC/eclipse-basketseal-mcp
Verify any MCP server in your client configs against this catalog with bazaar check (Cyan Eclipse Bazaar MCP / CLI — see llms.txt).