Vendor: Cyan Eclipse Technologies · Platforms: MCP over stdio (local; enclave deployment shape)
Certification scope
CERTIFIED(simulator) — Eclipse Bazaar Test Bench 2026-10-25, 13/14 checks pass, 1 na (U1 auth: stdio process boundary). Run by W-003 (Verity), suites/thread.py.
What it does
- Ingest Jira-DC-shaped REST exports, SARIF findings, VectorCAST-shaped coverage and XMI-lite model exports into one artifact graph
- Typed trace links with lineage {source tool, version, run id, source ref} on every artifact
- Gap-first trace analysis: unlinked requirements, untested code, findings without tickets, per-layer coverage
- Deterministic, hash-chained evidence packages (same graph, same package identity)
- Standalone evidence verification: artifact substitution and link removal detected and named
Tools
ingest_fixturegraph_querytrace_gapsevidence_buildevidence_verify
Problems it addresses
- My requirements, tests and findings live in four separate tools and nothing joins them
- I need a traceability package an auditor can verify independently
- I need to know which requirements have no test and which findings have no ticket
Not tested
- Any real tool instance: no Jira Data Center, Coverity, Cameo, or VectorCAST instance was available or contacted. All targets are fixtures/mocks — the (simulator) qualifier applies to the whole v0.1 scope.
- Live bridge behavior against a real Jira Data Center (auth, per-version REST surface, rate behavior) — bridge exercised only against the bundled stdlib stub over localhost HTTP.
Bench scorecard: test-bench/results/eclipse-thread-mcp-2026-10-25.json
Evaluation-intake listing
This listing records the tool's place in the Bazaar's evaluation
and monitoring pipeline, with the evidence gathered so far printed above — verdict, scope,
and not-tested items included. It is not sold on this site, and its presence in the catalog
is not a claim beyond that evidence. The service behind every verdict is the bench:
what a bench run buys →