Eclipse Bazaar · products.json · verdicts.json · llms.txt

Eclipse Voiceprint

Per-call voice continuity tokens over fixture call records — per-call continuity tokens seal the speaker model + voice fingerprint, so a voice agent cannot silently swap voices mid-relationship. PASS-CONDITIONAL(local, fixture call records) — fixture call records only; the claim is provable only at identifier granularity and same-model re-voicing behind unchanged identifiers is not detectable; never 'same voice verified', no biometric identity.

status: in-developmentclass: mcpIdentity & AttestationTrust & Receipts

Vendor: Cyan Eclipse Technologies

What it does

Tools

relationship_enrol · call_seal · relationship_rebaseline · relationship_close · relationship_status · continuity_pack_get · chain_verify · token_verify

Platforms

Certification

Bench verdict: PASS-CONDITIONAL(local, fixture call records)

Certified scope: PASS-CONDITIONAL(local, fixture call records) — Verity bench of v0.1.0 (2026-10-27, argus101-program-20261027/wave3/bench-voiceprint.md): builder suite 32/32 re-run clean by bencher; decisive fixture F-V14 independently reproduced on all three branches from the exported pack + pinned keys alone in a fresh process; bencher battery 82/82 after 3 probe-artifact corrections (F-1) — swap/drift exactness (drift never returned as SWAP_DETECTED; binary-exact 0.25 at threshold CONTINUOUS, 0.375 SUSPECT), claim-surface audit (narrowed claim verbatim on README/server.json/statements/verify results; forbidden §11.4 strings zero hits outside SPEC's own enumeration), 14-point delta law, refusal/gap battery, tamper battery (downgrade-never-upgrade on every path), metering exactness, disjoint surfaces, §7.3 fence, privacy fence (no audio capture/playback, telephony, speech, or biometric code path in the tree). Sole condition C1 (verbatim): external anchor required before live/multi-party use (cross-artifact coordinated rollback fenced; local SET anchor binds head + record_count within one pack only). Advisories F-2/F-3/F-4 (non-blocking, disclosed): fixture feature vectors are retained in attestation objects carried in the pack (token artifacts store the hash only; accepted at fixture scope, re-bench required for any real feature data); the §11.2 legend's '(§3.5)' parenthetical appears in README only; token_verify accepts a sealed token's SUSPECT_FEATURE_DRIFT on its identifier aspect only (full drift recompute lives in chain_verify). Scope is exactly: local stdio MCP, fixture call-record metadata only, value_class 'test' on all artifacts; no real audio is captured, processed, or stored, no human speaker is identified, and no live call platform is touched. Novel mechanism (SPEC §2.1, verbatim): per-call continuity tokens seal the speaker model + voice fingerprint, so a voice agent cannot silently swap voices mid-relationship.. Narrowed claim (verbatim): The 'cannot silently swap' claim is provable only at identifier granularity: a swap is proven only by a change in the attested model_id/voice_id (or a chain break); same-model re-voicing behind unchanged identifiers is not detectable.

Not tested:

  • Live call-platform integration (real audio / live attestations / human-voice feature data) — counsel gate (SPEC §10, named, unbuilt/unclaimed): processing real call audio, real provider attestations from live calls, or any feature data derived from a real human's voice requires counsel clearance (biometric-identifier law exposure, call-recording/wiretap consent regimes, provider terms on attestation reuse, counterparty disclosure duties, retention limits) before any build toward it; fixture audio metadata only in v0.1.0, no real voice biometrics stored, and there is no dormant live path to flip — live mode is a post-gate, re-benched code change
  • Same-model re-voicing behind unchanged identifiers — NOT detectable by this product, by design (SPEC §11.2): The 'cannot silently swap' claim is provable only at identifier granularity: a swap is proven only by a change in the attested model_id/voice_id (or a chain break); same-model re-voicing behind unchanged identifiers is not detectable. A CONTINUOUS result proves only that no attested identifier changed; it is never stated as 'same voice verified' and no biometric-identity claim is made — the fingerprint is the attested model/voice identifier set plus an audio-feature hash where available, and the product does not identify human speakers. Never claimed for v0.1.0 are 'voice authentication', 'speaker verification', 'fraud prevention', 'fraud-proof', 'deepfake detection', 'the same voice, guaranteed', or 'voice verified' (SPEC §11.4 strings named here only as never claimed)
  • Cross-artifact coordinated rollback — CONDITION C1 (bench, verbatim): external anchor required before live/multi-party use (cross-artifact coordinated rollback fenced; local SET anchor binds head + record_count within one pack only). Within one pack the signed SET anchor binds head + record_count and the §6.4 recompute detects tampering; a coordinated rollback across artifacts is fenced, not claimed detected, in the local model
  • Intra-call voice changes and unattested calls — any voice change inside a single call is outside v0.1 detection (per-call granularity, SPEC §3.5; segment identifier sets are refused as malformed), and any change on a call for which no attestation exists is recorded as a chained gap, not a detection
  • Production signing — v0.1.0 signing is a fixture HMAC stand-in for the Herald RS256 pattern (disclosed on every face; fixture keys in keys/fixture-keys.json, chmod 600, gitignored, never committed); a live phase requires real Herald signing and a re-bench; a fresh clone generates its own fixture keys to run the full suite
  • Hosted or live operation / charge path — local stdio only; metering points only per SPEC §9: exactly three Meter-grammar points — call_sealed, chain_verify, continuity_pack_exported — at the $0.03/call price shape attaching to call_sealed; the chain_verify metering point is emitted in the verifier result, not persisted (verifier surface is stateless/pure; counts remain recomputable from the stream + emitted records); no charge path is built, no payment is taken, and no live Meter ingest is claimed

Live state note: Bench evidence: argus101-program-20261027/wave3/bench-voiceprint.md (Verity bench of v0.1.0, 2026-10-27; builder suite re-run clean-state 32/32, decisive F-V14 reproduced independently on all three branches, bencher battery 82/82 after probe-artifact corrections, scope audit confirming the §10 counsel gate genuinely unbuilt; PASS-CONDITIONAL on sole condition C1, F-2/F-3/F-4 advisory only). PASS-CONDITIONAL is not CERTIFIED — certified: false. No test-bench scorecard was issued for this verdict and none is claimed (scorecard_ref/card_url null).

Pricing

PRICED — $0.03/call, 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.0, no charge path built): exactly three Meter-grammar points — call_sealed (per sealed continuity token, the $0.03/call shape attaches here), chain_verify (per verifier-surface verification; the point is emitted in the verifier result, not persisted), continuity_pack_exported (per pack); counts are recomputable from the record stream; per-call charging waits a hosted endpoint. The local package is the reference implementation. Repository is PRIVATE (priced-product policy).

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-voiceprint-mcp

Registry listing: https://registry.modelcontextprotocol.io/v0.1/servers/io.github.CYAN-ECLIPSE-TECHNOLOGIES-LLC%2Feclipse-voiceprint-mcp/versions/0.1.0

Repository: https://github.com/CYAN-ECLIPSE-TECHNOLOGIES-LLC/eclipse-voiceprint-mcp

Verify any MCP server in your client configs against this catalog with bazaar check (Eclipse Bazaar MCP / CLI — see llms.txt).