mcp-formal
Related Servers
Alternatives to mcp-formal
No user-submitted related servers found.
Related Servers
- AlicenseAqualityBmaintenanceEnables AI coding agents and IDEs to synthesize Verilog/SystemVerilog designs with Yosys, inspect cell hierarchies and gate counts, and detect synthesis hazards like inferred latches and combinational loops before physical design flows.414 npmApache 2.0

LazyVerilog MCPofficial
AlicenseAqualityBmaintenanceEnables AI coding agents to run a SystemVerilog LSP for linting, formatting, navigation, rename, RTL hierarchy inspection, and automated RTL code actions on real projects.1249 npm1MIT- AlicenseAqualityBmaintenanceEnables AI coding agents and IDEs to lint, compile, syntax-check, and simulate Verilog/SystemVerilog designs through structured, token-efficient MCP tools with isolated containerized toolchains.415 npmApache 2.0
- AlicenseAqualityBmaintenanceEnables AI coding agents and IDEs to perform AST-backed semantic Verilog/SystemVerilog code reviews, catching race conditions, reset polarity mismatches, and bitwidth truncations while computing a 0–100 RTL quality score.412 npm1Apache 2.0
- FlicenseNot gradedqualityAmaintenanceEnables Claude Code, Cursor, Codex, and other AI agents to safely drive a locally installed Xilinx Vivado through 32 tools spanning GUI/Tcl/attach sessions, synthesis, implementation, timing, CDC, XDC, IP, waveforms, and device programming. It adds structured timing evidence with baseline comparison, offline VCD queries, evidence-driven workflow prompts, and read-only environment self-diagnostics.-
- AlicenseAqualityBmaintenanceEnables AI coding agents to discover, generate, and run Cocotb co-simulation testbenches against Verilog/SystemVerilog designs, returning structured pass/fail results and tracebacks without manual simulator or Makefile setup.49 npm1Apache 2.0
TDQS
Scored across 3 tools
Each tool has a clearly distinct purpose: formal_prove runs proofs, formal_lint_sva checks syntax/elaboration, and formal_toolchain_info reports environment details. No overlap or ambiguity exists even without reading full descriptions.
All tools share the formal_ prefix and use snake_case, but formal_prove and formal_lint_sva are verb-oriented while formal_toolchain_info is noun-oriented. This is a minor inconsistency rather than a serious naming problem.
Three tools is a compact, focused set that covers the core formal-verification workflow without redundancy or unnecessary bloat.
The set covers proving, linting/elaboration, and toolchain introspection, which forms a solid lifecycle. A tool for explicitly listing or managing assertions could be missing, but the current coverage is sufficient for typical formal verification tasks.