Skip to main content
Glama
nickharris808

hw-verify-mcp

by nickharris808
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Related Servers

Alternatives to hw-verify-mcp

No user-submitted related servers found.

    Related Servers

    • VLSI Formal Verification MCP

      rahulbalhotra
      F
      license
      Not graded
      quality
      D
      maintenance
      Enables LLMs to interact with hardware designs (Verilog/SystemVerilog), formal verification tools, waveform logs, protocol specifications, and bug databases through 34 structured tools.
      -

    • easy-crypt-mcp

      davidscode404
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables AI agents to load, inspect, test, and repair machine-checked cryptographic proof files by wrapping EasyCrypt's batch CLI in six tools that report open goals and diagnostics. Agents can try tactic snippets on temporary copies, then commit only the steps that check, while the file itself holds all proof state.
      MIT

    • Verilator MCP Server

      ssql2014
      A
      license
      C
      quality
      F
      maintenance
      Enables RTL simulation and hardware verification with Verilator through automatic testbench generation, natural language queries about simulations, waveform analysis, and protocol-aware testing for Verilog/SystemVerilog designs.
      4
      4
      MIT

    • CHASE MCP Server

      chase-cps
      A
      license
      C
      quality
      A
      maintenance
      Enables AI agents to write, compose, and check assume-guarantee contracts, including refinement, consistency, compatibility, realizability, and LTL checks, and to use returned counterexamples to fix specifications.
      34
      BSD 3-Clause
    Deploy Server
    One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

    TDQS

    A3.8/5.0

    Scored across 12 tools

    Disambiguation4/5

    Most tools have clearly distinct purposes (e.g., list vs. get, check vs. replay), but check_constant_time and find_leak both analyze timing leaks, with check_constant_time already naming leaking secrets, making their boundaries slightly blurred. Descriptions mitigate confusion, but the overlap is present.

    Naming Consistency5/5

    All 12 tools follow a consistent verb_noun pattern with underscores (check_*, list_*, get_*, score_*, run_*, replay_*, prove_*). No mixed conventions or camelCase appear, making the naming highly predictable.

    Tool Count5/5

    With 12 tools spanning constant-time verification, benchmark handling, masking certification, and patch completeness, the count is well within the ideal 3-15 range. Each tool serves a distinct function, and none feel redundant or excessive.

    Completeness4/5

    The tool set covers the main workflows: checking constant-time, localizing leaks, running benchmarks, scoring submissions, certifying masking, and validating patches. A notable gap is prove_confidential, which is explicitly unavailable in open-source, leaving that functionality as a placeholder rather than a usable tool. Aside from this, the surface is comprehensive for the stated purpose.

    Maintenance

    ActivityStale
    ResponsivenessNo issues

    Resources