Eclipse Muzzle
Eclipse Muzzle — PASS (local/fixture) — Verity reduced-scope bench, secrets and PII only, ruleset muzzle-rules/0.4. A PASS verdict is scan evidence, not a guarantee of safety or non-defamation.
status: in-developmentclass: mcpTrust & ReceiptsPublishing
Vendor: Cyan Eclipse Technologies
What it does
- A PASS verdict is scan evidence, not a guarantee of safety or non-defamation.
- Classes scanned by this release: PII and secrets. Classes outside those two are not scanned, and a PASS is not evidence about them.
- This release does not scan for defamation-risk: defamation-risk detection is excluded from the certified scope of this version, and a PASS verdict is not evidence about defamation.
- Secrets detection (on seeded fixtures): private-key headers, AWS, GitHub and prefixed tokens, bearer and JWT tokens, keyword assignments including JSON and compound key names, Authorization headers in any scheme, URL userinfo passwords, standalone 32-char hex tokens, and high-entropy tokens — 100% recall and 100% precision on seeded fixtures (fresh bench corpus, rates computed from signed receipts).
- PII detection (on seeded fixtures): email addresses; Social Security numbers in dashed, dotted, spaced, and contiguous forms (SSA-validity gated); payment cards in grouped and contiguous forms (Luhn-gated); and phone numbers in domestic formats and E.164 international formats — 100% recall and 100% precision on seeded fixtures (spec thresholds ≥95% recall / ≥90% precision).
- Phone scope: international phone detection covers E.164 (`+`-prefixed) forms, grouped or contiguous. A foreign number dialled with a `00` prefix, or written in national format without a leading `+`, is not detected as an international number; however, if its trailing digits happen to form a US/Canada (NANP) number pattern, the domestic phone detector will flag that trailing pattern. National-format foreign numbers whose digits do not form a NANP pattern are not detected.
- Hex scope: standalone hex detection is capped at 32 chars — a standalone 32-char hex token is flagged; a hex string of 40 or more chars is detected only with assignment or header context, and standalone 40+ hex is not flagged.
- Every verdict is a Herald-signed receipt bound to the content hash: any one-byte change to the content fails offline verification at step 1, and a receipt signed under any keys other than the pinned Herald/scanner keys fails at step 2. Detected secrets and PII appear in receipts, exports, and persisted artifacts by span and hash only — never as raw values. Unverifiable artifacts export only as UNVERIFIED_EXPORT.
Tools
muzzle_scan · muzzle_rescan_status · muzzle_receipt_get · muzzle_receipt_verify · muzzle_require_pass · muzzle_export
Platforms
- MCP over stdio
Certification
Bench verdict: PASS-CONDITIONAL (local/fixture)
Certified scope: PASS-CONDITIONAL (local/fixture) — Verity reduced-scope bench of v0.1.3, ruleset muzzle-rules/0.4, 2026-10-27 (argus101-program-20261027/ruling-muzzle-reduced-scope.md), secrets and PII limbs ONLY: fresh bench-authored corpus (36 items, disjoint in values/shapes/phrasing from all repo fixtures and both prior Verity corpora), all rates computed from signed receipts after every receipt was independently re-verified — secrets 100% recall / 100% precision (13/13, 0 FP), PII 100% recall / 100% precision (13/13, 0 FP; spec thresholds ≥95% / ≥90%), benign controls 10/10 unflagged, verdict agreement 36/36; tamper battery, redaction invariant (zero raw-value escapes over corpus + canary sweeps), downgrade law, fail-closed fence (7/7), and exact 6-tool surface all PASS. PASS-CONDITIONAL is not CERTIFIED — certified is false, and nothing beyond the conditional verdict at its exact scope is claimed. Sole condition: the ruling §9 authorised claim block ships verbatim on every claim surface (README, this listing, server.legacy.json full manifest); the registry server.json description is the ≤100-char registry short form carrying the §11.1 sentence verbatim and claiming only secrets + PII. This release does not scan for defamation-risk: defamation-risk detection is excluded from the certified scope of this version, and a PASS verdict is not evidence about defamation. Defamation detection is not included in v0.1 — parked for a v0.2 redesign.
Not tested:
- Defamation-risk detection — not included in v0.1: Defamation detection is not included in v0.1 — parked for a v0.2 redesign; a PASS verdict is not evidence about defamation
- Any class outside PII and secrets — not scanned by this release, and a PASS is not evidence about them
- Live, publisher, or production scope — local/fixture only: no live publisher integration, hosted endpoint, network egress, or production content is certified by this ruling
- Detection rates beyond the seeded-fixture rates stated in the authorised claim block — measured on seeded shapes in a fresh fixture corpus only
- Production signing custody — fixture Herald/scanner RS256 keys are local-only in keys/ (gitignored, private keys mode 600, never committed); the v0.1.0 shipped fixture keys were burned and receipts signed under them fail verification at step 2
Live state note: Bench evidence: argus101-program-20261027/ruling-muzzle-reduced-scope.md (Verity reduced-scope bench, 2026-10-27). Prior history: bench-muzzle.md + rebench-muzzle.md + rebench-muzzle-012.md + rebench-muzzle-013.md — the defamation limb FAILed the v0.1.3 re-bench (4th unseen corpus, recall 40.0% vs ≥80% bar) and is NOT certified by this ruling; owner decision 2026-10-27 parked it to a v0.2 redesign and split the ship to secrets + PII only. Builder suite 53/53, and 53/53 with sockets denied, at bench. No test-bench scorecard was issued for this verdict and none is claimed (scorecard_ref/scorecard_url null).
Pricing
PRICED — $0.01/scan 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.1 (metering point only in v0.1.3, no charge path built): one metering point per completed scan (a scan reaching SCANNED, whatever its verdict — PASS, FINDINGS, or BLOCK); refused submissions are not a metering point; an idempotent resubmission returning the recorded scan asserts no new metering point. 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-muzzle-mcp
Registry listing: https://registry.modelcontextprotocol.io/v0.1/servers/io.github.CYAN-ECLIPSE-TECHNOLOGIES-LLC%2Feclipse-muzzle-mcp/versions/0.1.3
Repository: https://github.com/CYAN-ECLIPSE-TECHNOLOGIES-LLC/eclipse-muzzle-mcp
Verify any MCP server in your client configs against this catalog with bazaar check (Eclipse Bazaar MCP / CLI — see llms.txt).