Skip to main content
Glama
nomatic163

silicon_truth_bridge

by nomatic163

Related Servers

Alternatives to silicon_truth_bridge

No user-submitted related servers found.

    Related Servers

    • A
      license
      Not graded
      quality
      C
      maintenance
      An MCP server for reading and querying FSDB waveform files, enabling AI assistants to browse hierarchy, search signals, and extract waveform data with value changes.
      14
      MIT
    • F
      license
      A
      quality
      B
      maintenance
      A read-only MCP server that gives AI coding agents structured access to a project's source code, architecture, documentation, and Git context through 16 tools for searching, reading, and comparing evidence without modifying files.
      16
      -
    • F
      license
      Not graded
      quality
      B
      maintenance
      An MCP server that provides AI assistants with a persistent, sandboxed Python environment for waveform analysis, enabling loading and manipulation of VCD/FST/FSDB files and temporal pattern matching.
      9
      -
    • A
      license
      A
      quality
      C
      maintenance
      Read-only MCP server exposing a W3C PROV knowledge graph of verified facts with provenance, enabling AI agents to list, search, and check facts while enforcing that writes remain CLI-only.
      5
      MIT
    • A
      license
      Not graded
      quality
      A
      maintenance
      MCP server for fast, bounded, read-only Git evidence, enabling AI agents to query commit history, diffs, status, and snapshots by parsing repository storage directly.
      345 npm
      MIT

    TDQS

    C2.9/5.0

    Scored across 17 tools

    Disambiguation4/5

    Most tools are clearly distinct, especially with object_* and wave_* prefixes. The only potential overlap is between trace and connectivity_direct, but the descriptions differentiate a general graph from a one-hop direct query. Specialized trace tools like trace_active_driver and trace_value_origin have specific purposes, reducing ambiguity.

    Naming Consistency3/5

    Snake_case is used consistently, but the verb/noun arrangement is mixed: some are verb-first (trace, catalog), some are noun-verb (context_manage, object_resolve), and some are noun-noun (wave_value, source_context). There is structure via prefixes like object_ and wave_, but no uniform pattern across all tools.

    Tool Count4/5

    The 17 tools are slightly above the ideal range but each addresses a distinct aspect of hardware design analysis, such as context lifecycle, object querying, tracing, waveform data access, and mapping. The count is justified by the breadth of the domain and does not feel bloated.

    Completeness4/5

    The toolset provides strong coverage for a read-only analysis bridge: lifecycle management for contexts and waveforms, object resolution/query/traversal, multiple trace types, waveform value/changes/compute, source context, and mapping. Minor gaps like an explicit list-scopes tool are likely covered by catalog, but overall the surface is comprehensive.

    Maintenance

    ActivitySlowing
    ResponsivenessNo issues