SkillFoxx

xverif MCP

Xverif gives chip-verification agents deterministic tools for RTL, waveform, coverage and SVA debug through one MCP server.

  • 118 ★ on the repository
  • Last commit
  • MIT
MCP server

Extended access

Why this level

  • The agent gets file writes and control of live simulator sessions.
  • Some features need licensed third-party software.
All reasons and checks

blank2077/xverifAuthor:BLANK2077

Install

Manual install

python -m xverif_mcp.server

Runs from the repository clone as a stdio MCP server; dependencies are described in the README.

Access and checks

How we review

Extended accessThe tool runs code or makes network calls and only reads external data.

  • The agent gets file writes and control of live simulator sessions.
  • Some features need licensed third-party software.

This is third-party code. Review the repository files before installing.

What it does

Xverif, a local toolkit for chip-verification debug agents, collects exact tools instead of model guesses. `xdebug` answers questions about a design and its waveforms, `xbit` computes SystemVerilog values, `xcov` reads VCS and Verdi coverage databases, `xsva` explains SVA assertions and `xsimdebug` drives a live VCS or Xcelium session. The unified MCP entry `tools/xverif-mcp` runs over stdio. Only `xdebug` and `xcov` keep state; the other tools are stateless adapters. Default output is the compact `xout` text format.

Who it is for. ASIC and FPGA verification engineers who debug simulations alongside an AI agent.

Good fit when

  • An agent traces where a signal value came from at a given time in a waveform.
  • A list of uncovered objects with source links is needed from a coverage database.
  • Multi-beat byte fragments are decoded into fields from a description.
  • An SVA assertion must be explained through a structured form.

Not a fit when

  • You have no Synopsys Verdi and VCS licenses.
  • You need only an RTL generator, not debugging of an existing project.
  • The environment cannot build the C++ NPI wrapper.

Example request

Open the waveform database, find the last edge of `valid` before the error and explain where its value came from.

MCP

Transport
stdio
Authentication
not required

Environment variables

VERDI_HOME
Path to your own licensed Synopsys Verdi install for xdebug and xcov features

Limitations

Some `xdebug` and `xcov` features need separately purchased Synopsys rights and a local Verdi install. The repository contains no NPI or FSDB libraries and they must not be redistributed with it. The build depends on compiler version and library ABI, and not every combination is supported. MCP gives the agent file writes and session state changes. Python 3.11 or newer is required. The user manages Synopsys software rights alone; the project grants none.

How to disable. Remove the `xverif` entry from the MCP client configuration, end `xdebug` and `xcov` sessions and delete the repository clone. Clean `~/.xdebug` and the test cache separately.

FAQ

What works without a Synopsys license?

`xbit`, `xentry`, `xloc` and `xsva` do not read Verdi databases. Only `xdebug` and `xcov` need NPI, FSDB and coverage access.

How do I start the MCP server?

Through `tools/xverif-mcp`, a stdio server also reachable as `python -m xverif_mcp.server`.

How do I connect an agent to a remote EDA machine?

Configure `mcp_ssh`: the client starts it locally and the server process runs on the EDA host over ssh. Parameters come from `XVERIF_MCP_SSH_HOST` and `XVERIF_MCP_SSH_REMOTE_ROOT`.

What is xwiki for?

It keeps persistent verification project knowledge so an agent does not lose context between sessions.

What is the xout format?

A compact structured text format in which xverif commands emit results by default, except explicit machine protocols.

Discussion

No questions or reviews yet.

MCP servers
Editors’ pick

The official MCP server debugger: web UI, automation CLI and terminal UI in one package

CLIExtended access11.3K
Official

UI Verify's remote MCP server: the agent reviews pull request UI changes, inspects diffs and accepts the intended baselines

MCP serverExtended access27

MCP Interviewer checks an MCP server before an agent connects: provider limits, tool tests and a Markdown report.

CLIExtended access158

METR

METR (MCP 1C:Enterprise Test Runner)

Russian stack

An MCP server that lets an agent update a 1C infobase, run YaXUnit tests and check syntax

MCP serverBroad access123

An MCP server that checks whether the agent is really done: drives the real app and returns pass, fail or couldn't tell with the file and line

MCP serverExtended access1.3K

Electron debugging MCP server: 111 tools let an agent see the window, click buttons, read console and network and audit security.

MCP serverExtended access102

README in short

The README lists ten toolkit tools, explains the boundary between open source and Synopsys proprietary dependencies, and describes the build, tests and ssh connection.

README badge

Report a problem