Sentinel DV

io.github.kiranreddiPublished by GitHub account kiranreddiv2.3.1Updated Oct 25, 2026

MCP tools for UVM/cocotb logs, coverage, regressions, and waveform triage.

VerifiedSTDIODesktop onlyDeveloper ToolsData & Analytics

Overview

AI-generated overview

A read-only MCP server that indexes exported UVM, cocotb, coverage, regression and waveform artifacts into DuckDB so an assistant can triage verification runs.

What you can do
List, summarize, diff and compare simulation runs, and generate dry-run submit commands for review. Browse tests with history, topology, clustering and replay-command generation. Inspect failures, assertion failures, SVA status and vacuity. Review functional, code, toggle and FSM coverage, gaps, trends and constraint candidates. Check regression health and live simulation status. Read bounded waveform signal lists and summaries from precomputed wave JSON and VCD files.
When to use it
Useful for design-verification engineers who already export logs, coverage and waveform summaries from simulators and want an assistant to help with regression triage, single-test failure debugging or coverage closure without hand-parsing vendor output.
Requirements
Local Python 3.10 or newer, run via uvx or a pip install of sentinel-dv. A config.yaml path supplied through the SENTINEL_DV_CONFIG environment variable or the --config flag, with absolute artifact roots defined. The index must be built with the indexing command before the server starts. No authentication is declared.
Before you install
The server is read-only and does not run simulations or modify RTL or testbench files; runs.submit and tests.replay only return dry-run commands for engineer review. It reads artifacts from configured roots, so point those roots only at intended directories. Redaction of emails, paths and common secrets is configurable and should be reviewed before indexing production artifacts.

Installation

In SourceWeft

  1. Open Sentinel DV in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.

Other MCP clients

Follow the launch instructions in the repository.

README

Sentinel DV

[PyPI] [MCP Registry] [CI] [Documentation] [License]

Sentinel DV v2.3.1 is a read-only Model Context Protocol server for design verification evidence. It indexes exported SystemVerilog, UVM, cocotb, assertion, coverage, regression, and waveform artifacts into DuckDB and exposes 28 bounded, schema-driven tools to AI agents.

Documentation | Quick start | Video walkthrough | All tools | Agent skills

What it provides

  • Run and test intelligence: discovery, summaries, history, topology, diffs, replay-command generation, and live-status snapshots.
  • Failure analysis: normalized categories, stable signatures, bounded evidence, assertion failures, and failure clustering.
  • Coverage closure: functional, code, toggle, and FSM metrics; trends; gaps; vacuity; SVA status; and protocol-aware constraint candidates.
  • Waveform context: precomputed *.wave.json and bounded VCD summaries. Native FSDB/WLF streaming is intentionally out of scope.
  • Agent workflows: regression triage, single-test failure debugging, and coverage closure skills for Codex, Claude Code, and GitHub Copilot.

Sentinel DV does not execute simulations, modify RTL or testbench files, or stream unrestricted raw artifacts. runs.submit and tests.replay return dry-run commands for engineer review.

Quick start

Python 3.10 or newer is required. This example indexes the checked-in demo corpus:

For a persistent environment, install sentinel-dv>=2.3.1. The commands below use uvx to run the same release without a persistent install.

bash
git clone https://github.com/kiranreddi/sentinel-dv.gitcd sentinel-dvcp demo/config.example.yaml demo/config.yaml
uvx --from [email protected] \  sentinel-dv-index --config "$PWD/demo/config.yaml" --index-all

Connect one agent:

Codex

bash
codex mcp add sentinel-dv \  --env SENTINEL_DV_CONFIG="$PWD/demo/config.yaml" \  -- uvx --from [email protected] sentinel-dv-server

Claude Code

bash
claude mcp add \  --env SENTINEL_DV_CONFIG="$PWD/demo/config.yaml" \  --transport stdio --scope local sentinel-dv \  -- uvx --from [email protected] sentinel-dv-server

GitHub Copilot CLI

bash
copilot mcp add sentinel-dv \  --env SENTINEL_DV_CONFIG="$PWD/demo/config.yaml" \  -- uvx --from [email protected] sentinel-dv-server

Use an absolute SENTINEL_DV_CONFIG path. Verify the connection in the client's MCP status view, then call runs.list.

See Agent setup for configuration-file examples, project scope, skill discovery, and troubleshooting.

Production configuration

Copy config.example.yaml and define allowed artifact roots:

yaml
artifact_roots:  - /absolute/path/to/regression/artifacts
index:  type: duckdb  path: ./sentinel_dv.db
adapters:  uvm: true  cocotb: true  assertions: true  coverage: true  waveform_summary: true
security:  max_response_bytes: 2097152  max_page_size: 200  max_evidence_refs: 10
redaction:  enabled: true  redact_emails: true  redact_paths: true

Build the index before starting the server:

bash
sentinel-dv-index --config /absolute/path/to/config.yaml --index-allsentinel-dv-server --config /absolute/path/to/config.yaml

Relative paths inside the YAML are resolved from the config file's directory. Production startup never silently falls back to demo data.

MCP tools

The 28 tools are grouped by engineering purpose:

AreaTools
Runsruns.list, runs.get, runs.summary, runs.diff, runs.cross_sim, runs.submit
Teststests.list, tests.get, tests.history, tests.topology, tests.cluster, tests.replay
Failures and assertionsfailures.list, assertions.list, assertions.get, assertions.failures, assertions.sva_status, assertions.vacuity
Coveragecoverage.list, coverage.summary, coverage.gaps, coverage.trend, coverage.advisor
Regression and simulationregressions.summary, regression.health, sim.status
Waveformswave.signals, wave.summary

Every registered tool carries read-only MCP annotations and a versioned output schema. The MCP tools reference documents exact inputs and outputs.

Agent skills

The canonical skills live under skills/:

Deterministic mirrors support project discovery:

HostPath
Codex.agents/skills/
Claude Code.claude/skills/
GitHub Copilot.github/skills/

The repository also contains Codex and Claude plugin manifests. .mcp.json defines the bundled stdio server command; provide SENTINEL_DV_CONFIG or a config.yaml in the server working directory.

After editing a canonical skill:

bash
.venv/bin/python scripts/sync_agent_skills.py.venv/bin/python scripts/sync_agent_skills.py --check

Supported artifact sources

  • UVM logs and topology hints
  • cocotb and generic JUnit XML
  • assertion definition and failure JSON
  • SVA run-status JSON
  • supported JSON, XML, text, and HTML coverage summaries
  • *.wave.json and VCD
  • live simulation status JSON
  • exported VCS, Xcelium, Questa, and Verilator results

Adapter output is normalized into versioned schemas so clients do not need vendor-specific parsing logic.

Security model

  • Tools are read-only and operate on an index plus configured artifact roots.
  • Path resolution is sandboxed to allowed roots.
  • Evidence counts, excerpts, pages, wave signals, bins, and total response size are bounded.
  • Configurable redaction protects common secrets, email addresses, IP addresses, and local paths.
  • Tool output is deterministic; the MCP server does not generate causal conclusions.

Read Security and Production deployment before using production artifacts.

Verification

Create a development environment:

bash
python3 -m venv .venv.venv/bin/pip install -e ".[dev,docs]"

Run endpoint and workflow checks:

bash
.venv/bin/python scripts/verify_all_mcp_tools.py.venv/bin/python scripts/verify_skill_workflows.py

Run the full quality suite:

bash
.venv/bin/pytest.venv/bin/ruff check ..venv/bin/black --check ..venv/bin/mypy sentinel_dv.venv/bin/mkdocs build --strict

The all-tools verifier invokes every registered MCP endpoint. The skill verifier indexes 52 checked-in demo artifacts and executes the published regression triage, failure debugging, and coverage closure sequences.

Project layout

text
sentinel_dv/  adapters/        artifact parsers  indexing/        DuckDB indexing and queries  normalization/   signatures, taxonomy, redaction, coverage guidance  schemas/         versioned response contracts  tools/core.py    tool implementations  server.py        FastMCP registration and stdio entry point
skills/            canonical agent skillsdemo/              license-free exported verification fixturesdocs/              MkDocs documentationscripts/           verification, gallery, release, and skill-sync toolingtests/             unit and integration coverage

Contributing

See CONTRIBUTING.md. Sentinel DV is licensed under Apache-2.0.

Source: README.md at commit 0915256

Tools

0
SourceWeft has not started this package in its sandbox yet, so its tools are not known.

Version history

1
  1. v2.3.1LatestSep 16, 2026

Score

50% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 days25 pts

    Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.

  • Auth declared10 pts

    Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.

  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts
  • License10 pts