
Eclipse Warranty
io.github.CYAN-ECLIPSE-TECHNOLOGIES-LLCPublished by GitHub account CYAN-ECLIPSE-TECHNOLOGIES-LLCv0.1.1Updated Oct 29, 2026
Warranty witness for agent purchases: sealed, transferable claim packs. LOCAL/fixture only.
Overview
Local MCP server that seals purchase records into transferable, verifiable warranty claim packs for agent purchases.
- What you can do
- Register a warranty claim pack from a serial, product reference, buyer mandate reference, retailer receipt reference and purchase timestamp, one pack per serial
- Retrieve a pack with its bindings, current holder and transfer chain
- Verify a pack's seal and chain linkage by pack ID or supplied pack object, flagging tampered fields as invalid
- Transfer a pack to a new holder with a chained transfer record that still verifies without the original holder
- Check whether a given serial has a valid transferable claim pack
- When to use it
- For experimenting with a local, fixture-only prototype of warranty registration and resale transfer for agent-initiated purchases, where you want a sealed witness record that can be verified and handed on without a retailer account.
- Requirements
- Runs as a local process over stdio, started with python3 server.py. State is kept in data/packs.json and a demo HMAC key in keys/, both gitignored; the locations can be overridden with the ECLIPSE_WARRANTY_DATA_DIR and ECLIPSE_WARRANTY_KEY_FILE environment variables. Fixture purchase records are supplied by the caller.
Installation
In SourceWeft
- Open Eclipse Warranty in the dashboard and add it to a workspace.
- Enable the server for the chats that should use its tools.
Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.
Other MCP clients
Follow the launch instructions in the repository.
README
Eclipse Warranty
Warranty registration witness for agent purchases — binds serial, buyer mandate, and retailer receipt into one transferable claim pack.
Status: v0.1.1 — CERTIFIED (local, fixture) (Verity re-bench 1, 2026-10-26: 95 asserted PASS / 0 FAIL; D1 full-content seal + D2 schema enforcement closed; prior v0.1.0 verdict CONDITIONAL). Spec: SPEC.md (see its Bench Fix addendum — v0.1.0-sealed packs verify INVALID under v0.1.1; fixture packs are re-registered, no migration). Scope: LOCAL / fixture.
Novel mechanism
The claim pack is transferable on resale because it is bound to the product serial + sealed purchase proof, not to a retailer account login. Transfer appends a chained record and re-seals; verification recomputes the seal from the serial, bindings, and transfer chain alone — no account credential, no original holder. Incumbents (Extend / Mulberry) attach plans to retailer accounts with no agent mandate proof; here buyer_mandate_ref is a sealed binding.
Honest scope
Registrations operate on fixture purchase records supplied by the caller. Seals are local HMAC-SHA256 hash seals using a demo key generated at runtime in keys/ (gitignored). The pack is a witness record, not a warranty contract — no legal warranty adjudication, coverage, or enforceability is claimed, and no retailer or manufacturer is contacted.
Tools (exactly five)
Pricing
FREE + funnel role — free registration drives Eclipse Procure order volume and Till receipts. No payment anything.
Run
State: data/packs.json (gitignored; override ECLIPSE_WARRANTY_DATA_DIR). Demo key: keys/demo.key (gitignored, generated on first use; override ECLIPSE_WARRANTY_KEY_FILE). Fixture seeds: fixtures/.
MIT License · Copyright © 2026 Cyan Eclipse Technologies LLC · cetech.ai
Source: README.md at commit 7814ce5
Tools
0Version history
1- v0.1.1LatestOct 29, 2026
Score
50% of the applicable checks met
How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.
- Reached in the last 30 days25 pts
Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.
- Auth declared10 pts
Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.
- Tools listed15 pts
Answer tools/list without a credential, or ship a package that starts in a sandbox without one.
- DescriptionRequired15 pts
- Logo10 pts
- Documentation15 pts
- License10 pts