Verification — Eclipse Legacy Recon MCP

No on-chain commitment exists for this verdict yet. The scorecard is the published record, and its digest below lets any copy be checked byte-for-byte against the file served here — a same-host check until per-verdict anchoring ships with Phase-1 D2.

What this proves — and what it doesn't. Byte-integrity proves this record is unaltered since publication. It does not by itself prove the tool is safe: safety rests on the test verdict's scope, what was not tested, and the tool's current operational status — the other dimensions shown on this page.

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.
No signing key is published for bench scorecards: verdicts are unsigned hosted records today. The only published key identity in the chain is the Eclipse Anchor attestation key, at batch level.

Availability

Catalog status: in-development

Distribution: MCP over stdio (HTTP transport on roadmap)

Test verdict

Bench verdict: CERTIFIED(local)

Certified scope: CERTIFIED(local) at the NARROWED OBSERVED SCOPE (CLAIM-SCOPE.md): Positive DECLARED, OBSERVED, and INFERRED reports only within CLAIM-SCOPE.md, with evidence or basis carried in the output; OBSERVED is not exhaustive. Withdrawn by name — W1 JS_TS_MULTILINE_BLOCK_COMMENT_CONTINUATION_AFTER_SPLIT_NO_CLOSE_SPAN · W2 JS_TS_CHAINED_NO_CLOSING_SLASH_REGEX_SPANS_ON_ONE_LINE · W3 B_LR_14_INVALID_LINE_NONINVENTORY_IDENTIFIER_FOLLOW · W4 EXHAUSTIVE_OBSERVED_RECALL · W5 DYNAMIC_IMPORT_OBSERVATION_OR_SPECIFIC_UNKNOWN · W6 MTS_CTS_OBSERVED_EXTRACTION · W7 PERMISSION_DENIED_SUBTREE_COMPLETENESS · W8 SELF_REFERENTIAL_SYMLINK_REPORT_AND_SKIP · W9 HOSTED_AUTHENTICATED_OR_MULTI_TENANT_OPERATION. Scoped re-bench card -11 (2026-10-26): 30 pass, 0 na of 30 checks.

Bench score (scorecard check tally): 30 pass · 0 fail · 0 na — 30 checks

Bench date: 2026-10-26

Scorecard (hosted JSON): https://eclipsebazaar.com/cards/eclipse-legacy-recon-mcp-2026-10-26-11.json

Lifecycle status of this verdict record: current

Publication integrity

Digest (SHA-256): 759e2dd0fca83b21719293856b3741979547e9e25245fa3481e4d7ad526990ef

Method: SHA-256 over the scorecard file bytes exactly as served at card_url. Recompute: curl -s https://eclipsebazaar.com/cards/eclipse-legacy-recon-mcp-2026-10-26-11.json | sha256sum

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.

Network context — the one confirmed anchor batch does not cover this verdict: batch b18e97a2efad… attests sealed Herald receipts (hash-chain seq 1-4) · Base tx 0x6a69e35cbe70428f1fa97251759e2b5fa974bd422f68a076ac5de72c7b2459d4 · block 53163637 · attestation key 1adf4657a0c5684cebf52df1c8eea1b47d7778100b0a78862c7e84c6ddda19b7

A chain commitment, where present, commits to the digest of the record — it proves the record's bytes are unaltered since commitment. It does not commit to, or prove, the tool's behaviour or safety.

Operational status

Trust state: UNVERIFIED · Drift: UNKNOWN

Last checked (last verified): 2026-10-26

Benched version: 0.1.0 · Latest seen: —

Verify recipe

Open the bench scorecard (JSON) — the published record of this verdict: scope, per-check evidence, bench version and date.
Recompute its SHA-256 digest (curl the scorecard URL | sha256sum) and compare with the digest on the verify page.
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.

Downloads: verification.json · verdicts.json · trust-feed.json · scorecard JSON