@sigasi/magic-hdl

MCPcommunity
v0.1.2026092115com.sigasiSEE LICENSE IN license.txtUpdated 1d agonpm

Analyze and verify Verilog, SystemVerilog, and VHDL projects from AI agents over MCP.

Works in
ClaudeCursorCopilotGemini

Inferred from the transports this listing declares (stdio). A client not listed here hasn’t been ruled out — it just isn’t something Forge can confirm.

Automatically indexed from public sources. Not yet verified by the developer on Forge.Claim this listing →
3Downloads/wk
1d agoLast update
Reads these credentials
  • MAGIC_HDL_LICENSE_KEYAPI keyoptional

    License key from the Magic HDL dashboard. Only needed when this machine has no stored key yet. Use `magic-hdl login` and `magic-hdl setup` to initialize.

Declared by the author in the official MCP registry. Forge does not store, broker, or ever see these values — the config below is scaffolded with placeholders you fill in locally.

Package
Authorcom.sigasi
LicenseSEE LICENSE IN license.txt
Version0.1.2026092115
Sourcenpm+mcp-registry
Trust Status
B
60/100Good
Listed in Forge index+10/10
Publisher identity verified+0/20
Publisher: run `forge publish` from the package repo to claim ownership
Ed25519 publish signature+0/5
Included automatically when the publisher runs `forge publish`
Domain verification+0/5
Publisher: host /.well-known/forge.json on the package homepage with { "publisher": "<github-login>" }
npm Trusted Publishing (Sigstore)+0/5
Publish from GitHub Actions with --provenance so the attestation binds this package to this repo
npm maintainer match+0/5
Earned once your identity is verified above and that login is an npm maintainer of this package
CVE scan · clean+30/30
Static analysis · clean+20/20
Paste into Claude Code, Cursor, or any AI assistant to fix all gaps
StatusCommunity-indexed
PublisherUnverified
SignatureUnsigned
Domain
Provenance
Dependencies✓ 0 resolved · none vulnerable
Tool surface
Security scan✓ Cleanv0.1.2026091708 · 5d agoHow well does this scan work?
EvalsNone
IndexedSep 18, 2026

Verification confirms publisher identity (repo ownership), not code safety. The security scan covers known CVEs and suspicious install scripts.

Tools

Source not readable5d ago

The published package tarball could not be read at scan time (tarball exceeds 15MB cap), so no tool declarations could be extracted from it. Nothing here is a statement about what this exposes.

About

Analyze and verify Verilog, SystemVerilog, and VHDL projects from AI agents over MCP.

Keywords
mcp
Alternatives
Comparing tool surfaces…

Dependency tree

What one Forge scan resolved from npm metadata on 2026-09-18 — observed resolution, not a publisher declaration.

0 packages resolved · 0 direct · none carrying advisories Resolution stops at depth 4 and 60 packages.

This package declares no runtime dependencies.