RTL Lint MCP
PYPI · RTL-LINT-MCP
Lint Verilog and SystemVerilog files and projects with structured diagnostics.
Available components
Last scanned (20 hours ago)
Scores higher than 56% of PyPI servers
Category Testing and QA
How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score → Why this is hard to score →
Supply Chain Security50
- Malware scan not yet available for this package.Unverified
- No known CVEs affecting this package version or its production dependencies.Pass
- Runs hatchling.build at install time, a recognised build step with no custom scripting around it. View diagnostics → Pass
- 1 of 28 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency19
- Repository check failed: no source repository is declared. See how to fix → View diagnostics → Fail
- Provenance check failed: no build-provenance attestation is published. See how to fix → View diagnostics → Fail
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 78 days ago).Pass
- Security-disclosure policy not yet verified: we couldn't inspect the source repository.Unverified
Schema Quality & AI Usability58
- AI-judged instruction clarity (fair).Partial
- Tool/resource definitions use about 277 tokens (~69/item across 4 items; 4 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management67
- Stability observed for 20 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage71
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 0% of tool parameters carry a description.Fail
- Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 4 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 5 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a current MCP spec version (2026-07-28).Pass
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 4 Nov 26 −15
- Malware scan: pass → unverified ▼ security
- 3 Nov 26 +10
- Malware scan: unverified → pass ▲ security
- Stability: pass → 0.63 functional
- 26 Oct 26 −15
- Malware scan: pass → unverified ▼ security
- 24 Oct 26 +15
- Malware scan: unverified → pass ▲ security
- 23 Oct 26 −15
- Malware scan: pass → unverified ▼ security
- 22 Oct 26 0
- Stability: 0.97 → pass security
- 21 Oct 26 0
- Stability: pass → 0.97 functional
- 17 Oct 26 +18
- Malware scan: unverified → pass ▲ security
- Stability: 0.80 → pass security
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 4 Nov 2026 · Analysed pypi/rtl-lint-mcp@0.2.0
Provenance No attestation
The registry publishes no build provenance for this version, so there is nothing to verify.
| Result | No attestation |
|---|---|
| Ecosystem | pypi |
| Reason | No attestation published |
Background: How many MCP packages publish verified provenance →
Install scripts 1 script
| Hook | Tier | Command |
|---|---|---|
| build_backend | allowlisted | hatchling.build |
Background: Why install scripts are a supply-chain risk →
Dependencies 28 packages
| Packages resolved | 28 |
|---|---|
| No linked repository | 1 |
| Tree resolution | Complete |
Background: SBOMs and build attestations, explained →
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
lint_rtl_file ~71
Lint one .v, .vh, .sv, or .svh file inside an allowed root.
| Name | Type | Req | Description |
|---|---|---|---|
| allow_testbench_constructs | boolean | – | – |
| disabled_rules | – | – | – |
| enabled_rules | – | – | – |
| max_issues | integer | – | – |
| path | string | yes | – |
Structured output declared, but exposes no named fields.
No examples provided.
lint_rtl_project ~82
Discover and lint RTL files below an allowed project directory.
| Name | Type | Req | Description |
|---|---|---|---|
| allow_testbench_constructs | boolean | – | – |
| disabled_rules | – | – | – |
| enabled_rules | – | – | – |
| exclude_dirs | – | – | – |
| globs | – | – | – |
| max_files | integer | – | – |
| max_issues_per_file | integer | – | – |
| root | string | yes | – |
Structured output declared, but exposes no named fields.
No examples provided.
lint_rtl_text ~70
Lint Verilog/SystemVerilog source text without reading a file.
| Name | Type | Req | Description |
|---|---|---|---|
| allow_testbench_constructs | boolean | – | – |
| disabled_rules | – | – | – |
| enabled_rules | – | – | – |
| filename | string | – | – |
| max_issues | integer | – | – |
| text | string | yes | – |
Structured output declared, but exposes no named fields.
No examples provided.
list_rtl_lint_rules ~21
List all lightweight RTL lint rules and recommendations.
Input schema present but exposes no named parameters.
Structured output declared, but exposes no named fields.
No examples provided.
How do I install the RTL Lint MCP server?
RTL Lint MCP runs locally as a PyPI package, launched with uvx rtl-lint-mcp. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
pypi · rtl-lint-mcp
claude mcp add jaspresi-rtl-lint-mcp -- uvx rtl-lint-mcp
What is the RTL Lint MCP server?
RTL Lint MCP is listed in the public MCP registry as io.github.jaspresi/rtl-lint-mcp. Lint Verilog and SystemVerilog files and projects with structured diagnostics. This page covers its PyPI package (rtl-lint-mcp).
Is the RTL Lint MCP server safe to use?
RTL Lint MCP scores 54 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 4 November 2026. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the RTL Lint MCP server expose?
RTL Lint MCP exposes 4 tools: list_rtl_lint_rules, lint_rtl_text, lint_rtl_file, lint_rtl_project. Their descriptions and schemas cost roughly 244 tokens of context every time the server is loaded.
Is the RTL Lint MCP server still maintained?
RTL Lint MCP is still listed as active in the MCP registry. We last reached this channel on 4 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.
What licence is the RTL Lint MCP server under?
RTL Lint MCP declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.