Eclipse Insurepack
Continuous cyber-insurance evidence assembly over fixture records; local/simulator only. PASS-CONDITIONAL (local/simulator) — a live underwriter-facing evidence API fed by bench verdicts, incident records, and control receipts — premium-relevant changes emit change receipts to the insured. Evidence assembly only; no underwriting. Amended Condition 1′: a single-pack VERIFY_PASS is not proof of completeness of earlier transitions. Counsel gate (SPEC §10) named and unbuilt: any live phase.
status: in-developmentclass: mcpCompliance & EvidenceSecurity & Audit
Vendor: Cyan Eclipse Technologies
What it does
- Novel mechanism (SPEC §2.1, verbatim) — a live underwriter-facing evidence API fed by bench verdicts, incident records, and control receipts — premium-relevant changes emit change receipts to the insured. (In v0.1.1 the API shape is rehearsed locally over fixtures only: no live API is built, no underwriter is served, and no insurer system is touched.)
- Load-bearing disclosure (SPEC §11.1, verbatim): the evidence pack is insured-side disclosure tooling; underwriting reliance is the insurer's process, not Insurepack's claim. Insurepack is evidence assembly only. It does not underwrite, is not an insurer, broker, MGA, or underwriting tool, does not price or bind coverage, does not adjust or pay claims, and does not act for any carrier.
- Bench path: v0.1.0 bench (wave4/bench-insurepack.md, DEFECT-1..3) + v0.1.1 delta re-bench (wave4/rebench-insurepack.md: DEFECT-1..3 all CLOSED, Condition 1 amended to Condition 1′ by the bench, builder suite 28/28 reproduced, no new defect).
- Amended Condition 1′ (verbatim, named by the bench): a single-pack VERIFY_PASS attests the pack, its own transition, and the internal integrity of the presented stream; it must NOT be relied on as proof of completeness of transitions earlier than the pack's immediate predecessor (a fully re-signed, re-linked rewritten stream is indistinguishable there); full-history reliance requires per-pack chain verification (which the export transcript now performs) or an external anchor.
- Change receipts are issued for premium-relevant CHANGES only (verdict/insured-tool-set/control/incident-summary/named-field changes), never for re-assembly, verification, export, or same-state refresh — the change-receipt stream cannot be flooded into meaningless noise by re-running assembly. Absence of evidence is shown as absence: an input class with no registered fixture records is named in gaps[] (INPUT_ABSENT), never fabricated or silently omitted. Herald (signing pattern), Meter (metering grammar), and Docket (pack grammar) are consumed by reference only.
Tools
insurepack_profile_register · insurepack_input_present · insurepack_assemble · insurepack_pack_get · insurepack_verify · insurepack_changes_list · insurepack_export
Platforms
- MCP over stdio
Certification
Bench verdict: PASS-CONDITIONAL (local/simulator)
Certified scope: Eclipse Insurepack — PASS-CONDITIONAL (local/simulator) — Verity bench of v0.1.0 (2026-10-27, argus101-program-20261027/wave4/bench-insurepack.md) + delta re-bench of v0.1.1 (argus101-program-20261027/wave4/rebench-insurepack.md: DEFECT-1..3 all CLOSED, Condition 1 amended to Condition 1′ by the bench, builder suite 28/28 reproduced). PASS-CONDITIONAL (local/simulator) is not CERTIFIED — certified is false, and nothing beyond that verdict at its exact scope is claimed. Scope is exactly: local stdio, evidence assembly over fixture verdict/incident/control records only, value_class "test"; no live API is built, no underwriter is served, no insurer system is touched, and no real insured, real incident, or real policy enters a pack. Load-bearing disclosure (SPEC §11.1): the evidence pack is insured-side disclosure tooling; underwriting reliance is the insurer's process, not Insurepack's claim. Amended Condition 1′ binds verbatim: a single-pack VERIFY_PASS attests the pack, its own transition, and the internal integrity of the presented stream; it must NOT be relied on as proof of completeness of transitions earlier than the pack's immediate predecessor (a fully re-signed, re-linked rewritten stream is indistinguishable there); full-history reliance requires per-pack chain verification (which the export transcript now performs) or an external anchor. Rollback fence and the SPEC §10 counsel gate (named, unbuilt) also bind.
Not tested:
- Underwriting, pricing, binding, claims, or any insurer-side reliance — Insurepack is evidence assembly only (evidence assembly only; no underwriting): it does not underwrite, is not an insurer, broker, MGA, or underwriting tool, does not price or bind coverage, does not adjust or pay claims, and does not act for any carrier; underwriting reliance is the insurer's process, not Insurepack's claim (SPEC §11.1)
- Any live phase — serving real insureds, real incident records, real policies, a live underwriter-facing API, or any insurer/carrier/regulator integration is SPEC §10 counsel-gated and UNBUILT; there is no dormant live path in v0.1.1
- Full-history completeness from a single pack — per amended Condition 1′, a single-pack VERIFY_PASS must NOT be relied on as proof of completeness of transitions earlier than the pack's immediate predecessor; full-history reliance requires per-pack chain verification (which the export transcript performs) or an external anchor
- External anchoring / multi-party reliance — the pure local file store caps any verdict at PASS-CONDITIONAL (local/simulator); an external anchor is required before live or multi-party reliance
- Production key custody — signing is an HMAC fixture stand-in for Herald RS256 (fixture keys in keys/, gitignored, mode 600); a live phase would need real Herald signing and a re-bench
Live state note: Bench evidence: argus101-program-20261027/wave4/bench-insurepack.md (Verity bench of v0.1.0, PASS-CONDITIONAL (local/simulator), DEFECT-1..3) + argus101-program-20261027/wave4/rebench-insurepack.md (Verity delta re-bench of v0.1.1 fix commit 440c3cc: DEFECT-1..3 all CLOSED, Condition 1 amended to Condition 1′, builder suite 28/28 reproduced, no new defect). No test-bench scorecard was issued for this verdict and none is claimed (scorecard_ref/card_url null).
Pricing
PRICED — $149/mo (evidence assembly only; no underwriting), via the Eclipse Bazaar bench-order/intake path only. No checkout, payment, or buy-now link exists for this product, and no Stripe object exists for it in this pass: intake orders are reviewed and confirmed by the operator before any payment link is sent. Metering shape per SPEC §9 (metering points only in v0.1.1, no charge path built): packs assembled / change receipts issued at the $149/mo shape. No charge path is built, no payment is taken, and no live Meter ingest is claimed. The local package is the reference implementation. Repository is PRIVATE.
Install / verify
No install command is published for this product in the catalog or its registry record.
Official MCP Registry name: io.github.CYAN-ECLIPSE-TECHNOLOGIES-LLC/eclipse-insurepack-mcp
Registry listing: https://registry.modelcontextprotocol.io/v0.1/servers/io.github.CYAN-ECLIPSE-TECHNOLOGIES-LLC%2Feclipse-insurepack-mcp/versions/0.1.1
Repository: https://github.com/CYAN-ECLIPSE-TECHNOLOGIES-LLC/eclipse-insurepack-mcp
Verify any MCP server in your client configs against this catalog with bazaar check (Eclipse Bazaar MCP / CLI — see llms.txt).
Verification
Issued by Verity (Cyan Eclipse Technologies) — a role-separated internal desk of the same company that publishes this catalog. Issuer relationship: first-party. The bench is not an external third-party evaluator.
Availability
Catalog status: in-development
Distribution: MCP over stdio
Live-state note (from the catalog record): Bench evidence: argus101-program-20261027/wave4/bench-insurepack.md (Verity bench of v0.1.0, PASS-CONDITIONAL (local/simulator), DEFECT-1..3) + argus101-program-20261027/wave4/rebench-insurepack.md (Verity delta re-bench of v0.1.1 fix commit 440c3cc: DEFECT-1..3 all CLOSED, Condition 1 amended to Condition 1′, builder suite 28/28 reproduced, no new defect). No test-bench scorecard was issued for this verdict and none is claimed (scorecard_ref/card_url null).
Test verdict
Bench verdict: PASS-CONDITIONAL (local/simulator)
Certified scope: Eclipse Insurepack — PASS-CONDITIONAL (local/simulator) — Verity bench of v0.1.0 (2026-10-27, argus101-program-20261027/wave4/bench-insurepack.md) + delta re-bench of v0.1.1 (argus101-program-20261027/wave4/rebench-insurepack.md: DEFECT-1..3 all CLOSED, Condition 1 amended to Condition 1′ by the bench, builder suite 28/28 reproduced). PASS-CONDITIONAL (local/simulator) is not CERTIFIED — certified is false, and nothing beyond that verdict at its exact scope is claimed. Scope is exactly: local stdio, evidence assembly over fixture verdict/incident/control records only, value_class "test"; no live API is built, no underwriter is served, no insurer system is touched, and no real insured, real incident, or real policy enters a pack. Load-bearing disclosure (SPEC §11.1): the evidence pack is insured-side disclosure tooling; underwriting reliance is the insurer's process, not Insurepack's claim. Amended Condition 1′ binds verbatim: a single-pack VERIFY_PASS attests the pack, its own transition, and the internal integrity of the presented stream; it must NOT be relied on as proof of completeness of transitions earlier than the pack's immediate predecessor (a fully re-signed, re-linked rewritten stream is indistinguishable there); full-history reliance requires per-pack chain verification (which the export transcript now performs) or an external anchor. Rollback fence and the SPEC §10 counsel gate (named, unbuilt) also bind.
Publication integrity
Receipt hash: none published — no receipt is linked to this record in the current records
Anchor state: NOT_ANCHORED No receipt hash is linked to this record in the published records; verdict anchoring ships with Phase-1 D2 of the Eclipse Anchor program.
Full verification view — integrity result, digests, and evidence for this listing.
Operational status
Trust state: UNVERIFIED · Drift: UNKNOWN
Benched version: — · Latest seen: 0.1.1
Verify it yourself
- Cross-check the verdict and scope against this product's record in the append-only verdict feed (/verdicts.json) — corrections arrive only as superseding records.
- On-chain: not yet available for this verdict — no receipt is linked to it in the published records (per-verdict anchoring arrives with Phase-1 D2). The scorecard and the verdict feed are the complete published record until then.