Eclipse Agesure
Band-only age attestation sealer/verifier over fixture attestations; local/fixture only. PASS-CONDITIONAL (local/fixture) — band-only attestation (18+ / 21+) that reveals nothing else — no birthdate, no document — sealed to the requesting service's mandate. It is not an identity claim. Rollback fence (C1): external anchor required before live/multi-party use. Counsel gate (C2, SPEC §10) named and unbuilt: any use involving real people.
status: in-developmentclass: mcpIdentity & AttestationTrust & Receipts
Vendor: Cyan Eclipse Technologies
What it does
- Novel mechanism (SPEC §2.1, verbatim) — band-only attestation (18+ / 21+) that reveals nothing else — no birthdate, no document — sealed to the requesting service's mandate.
- A proof states that an issuer attested a band for a pseudonymous subject ref, sealed to one mandate. It is not an identity claim: it does not prove who the subject is, that the presenter of a proof is the subject, or that the issuer's underlying band determination was correct. Agesure does not verify age: how a band was established is the issuer's attestation, consumed as an input. Two proofs for the same subject ref are linkable by a verifier holding both (inherent to the proof schema, spec Q-A4) — no unlinkability is claimed.
- Bench path: v0.1.0 bench (wave4/bench-agesure.md, defects D1–D8, conditions C1–C7; 150 bencher checks) + v0.1.1 delta re-bench (wave4/rebench-agesure.md: D1–D8 all CLOSED, new defect D9 + condition C8) + v0.1.2 spot re-bench (wave4/spot-agesure-012.md: D9 substring-embedding subject_ref screen CLOSED at all three enforcement sites, C8 DISCHARGED — reliance on the enforced band-only subject_ref hygiene is permitted within the local/fixture scope only; builder suite 35/35 reproduced).
- Standing condition C1 — rollback fence (verbatim): pure local file store caps verdict at PASS-CONDITIONAL — external anchor required before live/multi-party use. (The store replays an earlier signed snapshot undetected locally; the cap is structural, not discretionary.)
- Standing condition C2 — §10 counsel gate (named, unbuilt): any use involving real people — issuing proofs a real service relies on to gate access, processing real subjects' attestations, or any handling of data relating to minors (including the below-band verdict path) — is out of v0.1, hard, until counsel clears that use. No real issuer onboarding, no real service integration, no marketing addressed to live age-gating; there is no dormant live path in v0.1.2 to flip.
- Standing condition C5 — issuer key separation: the v0.1 issuer counter-signature is applied by the service process from a co-located fixture key file and is not evidence of an independent issuer act; before any scope beyond local/fixture the issuer key must be held by the issuer, separate from service custody. Standing condition C7 — name screen: "Agesure" remains a working name pending the house trademark/brand screen; no public claim attaches to the name.
- Signing is a fixture HMAC stand-in for Herald RS256, disclosed on every artifact face as signature_scheme; verification keys are pinned out-of-band by fixed key ref and never accepted from the record under verification. Till (mandates), Herald (signing pattern), Meter (metering grammar), and Docket (pack shape) are consumed by grammar/reference only.
Tools
proof_request · proof_verify · proof_status · revocation_present · issuance_pack_get · attestation_register
Platforms
- MCP over stdio
Certification
Bench verdict: PASS-CONDITIONAL (local/fixture)
Certified scope: Eclipse Agesure — PASS-CONDITIONAL (local/fixture) — Verity bench of v0.1.0 (2026-10-27, argus101-program-20261027/wave4/bench-agesure.md) PASS-CONDITIONAL with conditions C1–C7, + delta re-bench of v0.1.1 (argus101-program-20261027/wave4/rebench-agesure.md: D1–D8 all CLOSED, new defect D9 + condition C8), + spot re-bench of v0.1.2 (argus101-program-20261027/wave4/spot-agesure-012.md: D9 CLOSED, C8 DISCHARGED, builder suite 35/35 reproduced). PASS-CONDITIONAL (local/fixture) is not CERTIFIED — certified is false, and nothing beyond that verdict at its exact scope is claimed. Scope is exactly: local stdio, fixture attestations only, value_class "test"; no real person is checked and no real age-verification capability is claimed. A proof states that an issuer attested a band for a pseudonymous subject ref, sealed to one mandate; it is not an identity claim and does not prove the issuer's underlying band determination was correct. Standing conditions: C1 rollback fence (pure local file store caps the verdict at PASS-CONDITIONAL — external anchor required before live/multi-party use), C2 §10 counsel gate (named, unbuilt — any use involving real people), C5 issuer key separation, C7 name screen still bind.
Not tested:
- Any use involving real people — issuing proofs a real service relies on to gate access, processing real subjects' attestations, or any handling of data relating to minors (including the below-band verdict path) is SPEC §10 counsel-gated and UNBUILT; there is no dormant live path in v0.1.2
- Age verification itself — Agesure never determines age; the band is the issuer's attestation, consumed as an input, and a proof does not prove the issuer's underlying band determination was correct, who the subject is, or that the presenter is the subject
- Issuer independence at this scope — the issuer counter-signature is applied by the service process from a co-located fixture key file (condition C5); it is not evidence of an independent issuer act in v0.1.2
- External anchoring / multi-party reliance — the pure local file store caps any verdict at PASS-CONDITIONAL (local/fixture) (condition C1); 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-agesure.md (Verity bench of v0.1.0, PASS-CONDITIONAL (local/fixture), 150 bencher checks, defects D1–D8, conditions C1–C7) + argus101-program-20261027/wave4/rebench-agesure.md (Verity delta re-bench of v0.1.1: D1–D8 all CLOSED, new D9 + C8) + argus101-program-20261027/wave4/spot-agesure-012.md (Verity spot re-bench of v0.1.2: D9 CLOSED, C8 DISCHARGED, builder suite 35/35 reproduced). No test-bench scorecard was issued for this verdict and none is claimed (scorecard_ref/card_url null).
Pricing
PRICED — $0.05/proof, 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.2, no charge path built): proof_issued / proof_verified / pack_exported at the $0.05/proof price 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-agesure-mcp
Registry listing: https://registry.modelcontextprotocol.io/v0.1/servers/io.github.CYAN-ECLIPSE-TECHNOLOGIES-LLC%2Feclipse-agesure-mcp/versions/0.1.2
Repository: https://github.com/CYAN-ECLIPSE-TECHNOLOGIES-LLC/eclipse-agesure-mcp
Verify any MCP server in your client configs against this catalog with bazaar check (Eclipse Bazaar MCP / CLI — see llms.txt).