Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

Circuitarium MCP

NPM · CIRCUITARIUM-MCP

MCP tools for CRUMB artifacts and Logisim-evolution analysis and non-interactive simulation.

Available components

−1 this week 90 Trust /100

Last scanned (8 hours ago)

Scores higher than 93% of npm servers

Category Testing and QA

Trust breakdown (7 categories)

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 Security81
  • No malware found by supply-chain analysis.Pass
  • CVE check failed: a known high-severity CVE affects @modelcontextprotocol/sdk 1.30.0, a direct dependency. A fixed version is available. View diagnostics → Fail
  • No install/post-install scripts declared.Pass
  • 32 of 103 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency100
  • Source repository is publicly reachable at the declared URL. View diagnostics → Pass
  • Cryptographically verified build provenance (signed, bound to Craftiee/circuitarium-mcp). View diagnostics → Pass
  • Clear OSI-approved license (Apache-2.0).Pass
  • Actively maintained (last published 98 days ago).Pass
  • Publishes a security disclosure policy (SECURITY.md).Pass
Schema Quality & AI Usability86
  • 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
  • AI-judged instruction clarity (excellent).Pass
  • Tool/resource definitions use about 2818 tokens (~90/item across 31 items; 22 tools + 9 resources), lean.Pass
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management97
  • Stability observed for 29 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage84
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 44% of tool parameters carry a description.Partial
  • 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 22 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 24 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
  • Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Changelog

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 −1
    • Stability: pass → 0.93 functional
  • 29 Oct 26 +1
    • Stability: 0.97 → pass security
  • 28 Oct 26 −1
    • GHSA-f897-62hf-6gxq affects this package: high ▼ security
    • Stability: pass → 0.97 functional
  • 24 Oct 26 0
    • CVE-2023-54404 affects this package: high ▼ security
  • 22 Oct 26 +1
    • Stability: 0.97 → pass security
  • 21 Oct 26 −1
    • CVE-2026-111771 affects this package: high ▼ security
    • CVE-2026-111768 affects this package: high ▼ security
    • CVE-2026-111769 affects this package: high ▼ security
    • CVE-2026-111767 affects this package: high ▼ security
    • Stability: pass → 0.97 functional
  • 17 Oct 26 +3
    • Stability: 0.80 → pass security
  • 16 Oct 26 −3
    • Stability: pass → 0.80 functional
Diagnostics

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 5 Nov 2026 · Analysed npm/circuitarium-mcp@0.3.1

Provenance Verified

A signed build attestation was found and verified, binding this exact artifact to the source repository it claims to come from.

Result Verified
Ecosystem npm
Reason Verified
Discovered via Registry attestation endpoint
Source repo Craftiee/circuitarium-mcp
Certificate issuer https://token.actions.githubusercontent.com
Certificate SAN https://github.com/Craftiee/circuitarium-mcp/.github/workflows/publish.yml@refs/heads/main
Rekor log index 2279379360
Predicate type SLSA build provenance https://slsa.dev/provenance/v1
Subject digest sha512:833ddfebd22071fa8a899dd6258fc0fd2e49445c897bf8301058696dade42ca0a84aa885dcaa25e4d5ccc29d22efeac272db956865d63d6d916319946

Background: How many MCP packages publish verified provenance →

Vulnerabilities 7 findings
ID CVE Severity Vector Fix available
GHSA-22jm-h49p-29qw CVE-2026-111767 high CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:L/A:L yes
GHSA-46jr-4wx8-v453 CVE-2026-111768 high CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H yes
GHSA-6prh-2h8m-c8cw CVE-2026-111769 medium CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:L/A:N yes
GHSA-6qxp-vccf-f47h CVE-2026-104850 high CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N yes
GHSA-f897-62hf-6gxq high CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H yes
GHSA-rvq5-wwqv-78pq CVE-2026-111771 medium CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:N yes
GHSA-mrhx-c7xc-m3w5 CVE-2023-54404 high CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H yes

Background: What a vulnerability scan can and cannot prove →

Dependencies 103 packages
Packages resolved 103
Stale 32
Tree resolution Complete

Background: SBOMs and build attestations, explained →

MCP tools · 22 exposed · ~2,166 tokens

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 →

Tool Tokens
crumb_analyze_design ~130

Recognizes version-pinned component parameters, terminal attachments, and inferred connection groups. Summary is the bounded default; components and connections use opaque cursors. Embedded firmware and geometry require explicit opt-in.

NameTypeReqDescription
cursorstring––
expectedProjectDigeststring–Optional sha256: digest from a prior cross-model handoff
includeGeometryboolean––
includeSourceCodeboolean––
limitinteger––
pathstringyesWorkspace-relative .cru project ref
topologyModestring––
viewstring––
NameTypeReqDescription
contextobjectyes–
contractVersionstringyes–
dataobject––
diagnosticsarrayyes–
errorobject––
nextActionsarrayyes–
okbooleanyes–
summarystringyes–

No examples provided.

crumb_bom ~77

Groups recognized components by kind and decoded part values into quantities. State values such as switch positions are excluded from part identity; unknown and schema-mismatched components stay visible as their own lines.

NameTypeReqDescription
expectedProjectDigeststring––
limitinteger––
pathstringyesWorkspace-relative .cru project ref
NameTypeReqDescription
contextobjectyes–
contractVersionstringyes–
dataobject––
diagnosticsarrayyes–
errorobject––
nextActionsarrayyes–
okbooleanyes–
summarystringyes–

No examples provided.

crumb_check_design ~103

Lints the inferred netlist: supply shorts, LEDs directly across the rails, shorted two-terminal parts, floating IC power pins, resistor power ratings, and floating terminals. Findings carry evidence confidence and rule basis; a rule violation returns ok=true with data.valid=false.

NameTypeReqDescription
applySwitchStatesboolean––
expectedProjectDigeststring––
pathstringyesWorkspace-relative .cru project ref
topologyModestring––
NameTypeReqDescription
contextobjectyes–
contractVersionstringyes–
dataobject––
diagnosticsarrayyes–
errorobject––
nextActionsarrayyes–
okbooleanyes–
summarystringyes–

No examples provided.

crumb_compare_designs ~185

Read-only, GUID-matched comparison of a baseline and candidate .cru under crumb.unity/1.3.5. Distinguishes exact bytes, modeled equivalence, root changes, component changes, and unverified payload signatures without returning raw XML, firmware, EEPROM bytes, or thumbnails.

NameTypeReqDescription
baselinePathstringyesWorkspace-relative baseline .cru project ref
candidatePathstringyesWorkspace-relative candidate .cru project ref
compatibilityProfilestring––
cursorstring––
expectedBaselineDigeststring–Optional sha256: digest previously recorded for the baseline
expectedCandidateDigeststring–Optional sha256: digest previously recorded for the candidate
includeGeometryboolean––
limitinteger––
topologyModestring––
viewstring––
NameTypeReqDescription
contextobjectyes–
contractVersionstringyes–
dataobject––
diagnosticsarrayyes–
errorobject––
nextActionsarrayyes–
okbooleanyes–
summarystringyes–

No examples provided.

crumb_component_catalog ~54

Returns the version-pinned CRUMB tool-ID catalog, payload signatures, typed parameters, terminal labels, confidence values, and their machine-readable evidence vocabulary. Optionally filter by toolId.

NameTypeReqDescription
toolIdinteger––
NameTypeReqDescription
contextobjectyes–
contractVersionstringyes–
dataobject––
diagnosticsarrayyes–
errorobject––
nextActionsarrayyes–
okbooleanyes–
summarystringyes–

No examples provided.

crumb_export_netlist ~119

Collapses jumper wires out of the inferred connection graph and returns paged electrical nets with component terminals, VCC/GND names inferred from DC supply terminals, and optional saved-switch-state merges. Provenance and confidence are explicit.

NameTypeReqDescription
applySwitchStatesboolean–Merge nets across saved switch positions using installed-build semantics
cursorstring––
expectedProjectDigeststring––
limitinteger––
pathstringyesWorkspace-relative .cru project ref
topologyModestring––
NameTypeReqDescription
contextobjectyes–
contractVersionstringyes–
dataobject––
diagnosticsarrayyes–
errorobject––
nextActionsarrayyes–
okbooleanyes–
summarystringyes–

No examples provided.

crumb_generate_fixture ~65

Creates one known fixture without overwriting. Provide outputPath for a file artifact; raw XML is returned only when includeXml=true.

NameTypeReqDescription
includeXmlboolean––
kindstringyes–
namestring––
outputPathstring––
NameTypeReqDescription
contextobjectyes–
contractVersionstringyes–
dataobject––
diagnosticsarrayyes–
errorobject––
nextActionsarrayyes–
okbooleanyes–
summarystringyes–

No examples provided.

crumb_get_component ~149

Returns a single component by id with parameters, terminals, geometry, its inferred connection groups, and windowed access to embedded firmware source past the analyze cap. The read-back companion for iterative work on one part.

NameTypeReqDescription
componentIdstringyesComponent id from analyze/netlist output; matching is case-insensitive
expectedProjectDigeststring–Optional sha256: digest from a prior cross-model handoff
includeGeometryboolean––
includeSourceCodeboolean––
pathstringyesWorkspace-relative .cru project ref
sourceOffsetinteger–Character offset into embedded firmware source for continued reads
topologyModestring––
NameTypeReqDescription
contextobjectyes–
contractVersionstringyes–
dataobject––
diagnosticsarrayyes–
errorobject––
nextActionsarrayyes–
okbooleanyes–
summarystringyes–

No examples provided.

crumb_ic_reference ~75

Queries the version-pinned tool-5 IC registry by prefabId or by a label/package substring (for example "74HC138"). Returns package labels, ordered pin names, and explicit unresolved pins.

NameTypeReqDescription
prefabIdinteger––
querystring–Case-insensitive substring matched against IC label and package name
NameTypeReqDescription
contextobjectyes–
contractVersionstringyes–
dataobject––
diagnosticsarrayyes–
errorobject––
nextActionsarrayyes–
okbooleanyes–
summarystringyes–

No examples provided.

crumb_inspect_design ~69

Returns a bounded save summary and tool-ID counts. Use crumb_analyze_design for paginated semantic component and connection details.

NameTypeReqDescription
expectedProjectDigeststring–Optional sha256: digest from a prior cross-model handoff
pathstringyesWorkspace-relative .cru project ref
NameTypeReqDescription
contextobjectyes–
contractVersionstringyes–
dataobject––
diagnosticsarrayyes–
errorobject––
nextActionsarrayyes–
okbooleanyes–
summarystringyes–

No examples provided.

crumb_list_projects ~85

Enumerates .cru files under the workspace root (or one subdirectory) with size, modification time, and SHA-256 digest, so a model can discover projects without being handed a path.

NameTypeReqDescription
dirstring–Workspace-relative directory ref to list
includeDigestsboolean––
limitinteger––
recursiveboolean––
NameTypeReqDescription
contextobjectyes–
contractVersionstringyes–
dataobject––
diagnosticsarrayyes–
errorobject––
nextActionsarrayyes–
okbooleanyes–
summarystringyes–

No examples provided.

crumb_trace_net ~172

Selects one component terminal by stable index and returns a paged deterministic connectivity witness with structured attachment, board, jumper, and optional saved-switch provenance. It is static conductive inference, not current flow, path enumeration, or simulation.

NameTypeReqDescription
applySwitchStatesboolean–Apply persisted switch closures as conditional installed-build evidence
componentIdstringyesCase-insensitive component id from CRUMB analysis
cursorstring––
expectedProjectDigeststring––
expectedTerminalNamestring–Optional exact-name guard for cross-model handoff
limitinteger––
pathstringyesWorkspace-relative .cru project ref
terminalIndexintegeryesZero-based terminal index; canonical within the exact project bytes
topologyModestring––
NameTypeReqDescription
contextobjectyes–
contractVersionstringyes–
dataobject––
diagnosticsarrayyes–
errorobject––
nextActionsarrayyes–
okbooleanyes–
summarystringyes–

No examples provided.

crumb_validate_design ~67

Performs XML and CRUMB structural checks without launching the game. A bad design returns ok=true and data.valid=false.

NameTypeReqDescription
expectedProjectDigeststring–Optional sha256: digest from a prior cross-model handoff
pathstringyesWorkspace-relative .cru project ref
NameTypeReqDescription
contextobjectyes–
contractVersionstringyes–
dataobject––
diagnosticsarrayyes–
errorobject––
nextActionsarrayyes–
okbooleanyes–
summarystringyes–

No examples provided.

electronics_capabilities ~35

Zero-argument onboarding for model-neutral conventions, callable backends, truthful limitations, and recommended workflows. Call this first when unsure.

Input schema present but exposes no named parameters.

NameTypeReqDescription
contextobjectyes–
contractVersionstringyes–
dataobject––
diagnosticsarrayyes–
errorobject––
nextActionsarrayyes–
okbooleanyes–
summarystringyes–

No examples provided.

electronics_plan_verification ~78

Builds a deterministic, simulator-neutral plan for explicit claims using bounded caller-reported evidence. It reads no files, runs no tools or simulators, authenticates no receipts, and never certifies physical hardware.

NameTypeReqDescription
claimsarrayyes–
declaredInterfaceobject––
evidencearray––
target–yes–
NameTypeReqDescription
contextobjectyes–
contractVersionstringyes–
dataobject––
diagnosticsarrayyes–
errorobject––
nextActionsarrayyes–
okbooleanyes–
summarystringyes–

No examples provided.

electronics_validate_experiment ~48

Checks an arbitrary JSON value against the simulator-neutral circuit, firmware, probe, assertion, and timing contract. Invalid input returns ok=true and data.valid=false with diagnostics.

NameTypeReqDescription
experiment–yes–
NameTypeReqDescription
contextobjectyes–
contractVersionstringyes–
dataobject––
diagnosticsarrayyes–
errorobject––
nextActionsarrayyes–
okbooleanyes–
summarystringyes–

No examples provided.

logisim_analyze_design ~90

Parses bounded .circ XML into project, circuit, pin, clock, component, and explicit conversion-loss summaries. Static parsing is not simulation evidence.

NameTypeReqDescription
circuitstring–Circuit name; defaults to the declared main circuit
expectedProjectDigeststring–Optional sha256: digest from a prior cross-model handoff
pathstringyesWorkspace-relative .circ project ref
NameTypeReqDescription
contextobjectyes–
contractVersionstringyes–
dataobject––
diagnosticsarrayyes–
errorobject––
nextActionsarrayyes–
okbooleanyes–
summarystringyes–

No examples provided.

logisim_component_stats ~121

Invokes the separately installed JAR, after it self-reports Logisim-evolution 4.1.0, with --tty stats. Success proves that configured process loaded the staged project, not behavioral simulation or binary authenticity.

NameTypeReqDescription
circuitstring–Circuit name; defaults to the declared main circuit
expectedProjectDigeststring–Optional sha256: digest from a prior cross-model handoff
limitinteger––
pathstringyesWorkspace-relative .circ project ref
timeoutMsinteger––
NameTypeReqDescription
contextobjectyes–
contractVersionstringyes–
dataobject––
diagnosticsarrayyes–
errorobject––
nextActionsarrayyes–
okbooleanyes–
summarystringyes–

No examples provided.

logisim_export_netlist ~107

Exports simulator-neutral coordinate-endpoint nets with explicit loss markers. It does not infer unmodeled gate geometry, mid-segment junctions, or behavior.

NameTypeReqDescription
circuitstring–Circuit name; defaults to the declared main circuit
cursorstring––
expectedProjectDigeststring–Optional sha256: digest from a prior cross-model handoff
limitinteger––
pathstringyesWorkspace-relative .circ project ref
NameTypeReqDescription
contextobjectyes–
contractVersionstringyes–
dataobject––
diagnosticsarrayyes–
errorobject––
nextActionsarrayyes–
okbooleanyes–
summarystringyes–

No examples provided.

logisim_list_projects ~62

Discovers workspace .circ projects with stable raw-byte digests. This is static file discovery and does not launch Logisim.

NameTypeReqDescription
dirstring–Workspace-relative directory ref to list
limitinteger––
recursiveboolean––
NameTypeReqDescription
contextobjectyes–
contractVersionstringyes–
dataobject––
diagnosticsarrayyes–
errorobject––
nextActionsarrayyes–
okbooleanyes–
summarystringyes–

No examples provided.

logisim_run_test_vector ~153

Invokes the separately installed JAR, after it self-reports Logisim-evolution 4.1.0, with staged snapshots of a workspace-contained project and .vec/.txt file. Assertion failures return ok=true with data.valid=false.

NameTypeReqDescription
circuitstring–Circuit name; defaults to the declared main circuit
expectedProjectDigeststring–Optional sha256: digest from a prior cross-model handoff
expectedVectorDigeststring––
maxFailuresinteger––
pathstringyesWorkspace-relative .circ project ref
timeoutMsinteger––
vectorPathstringyesWorkspace-relative .vec or .txt test-vector ref
NameTypeReqDescription
contextobjectyes–
contractVersionstringyes–
dataobject––
diagnosticsarrayyes–
errorobject––
nextActionsarrayyes–
okbooleanyes–
summarystringyes–

No examples provided.

logisim_truth_table ~122

Invokes the separately installed JAR, after it self-reports Logisim-evolution 4.1.0, in CSV/binary table mode after statically bounding declared input width.

NameTypeReqDescription
circuitstring–Circuit name; defaults to the declared main circuit
expectedProjectDigeststring–Optional sha256: digest from a prior cross-model handoff
limitinteger––
maxInputBitsinteger––
pathstringyesWorkspace-relative .circ project ref
timeoutMsinteger––
NameTypeReqDescription
contextobjectyes–
contractVersionstringyes–
dataobject––
diagnosticsarrayyes–
errorobject––
nextActionsarrayyes–
okbooleanyes–
summarystringyes–

No examples provided.

Install

How do I install the Circuitarium MCP server?

Circuitarium MCP runs locally as an npm package, launched with npx -y circuitarium-mcp. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

npm · circuitarium-mcp

# add to Claude Code
claude mcp add craftiee-circuitarium -- npx -y circuitarium-mcp
Common questions

What is the Circuitarium MCP server?

Circuitarium MCP is listed in the public MCP registry as io.github.Craftiee/circuitarium. MCP tools for CRUMB artifacts and Logisim-evolution analysis and non-interactive simulation. This page covers its npm package (circuitarium-mcp).

Is the Circuitarium MCP server safe to use?

Circuitarium MCP scores 90 out of 100 on VerifyMCP. We recorded 7 known advisories against it as of 5 November 2026. It declares no install or post-install scripts. Its build provenance is signed and verified. 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 Circuitarium MCP server expose?

Circuitarium MCP exposes 22 tools: electronics_capabilities, electronics_validate_experiment, electronics_plan_verification, crumb_component_catalog, crumb_analyze_design, and 17 more. Their descriptions and schemas cost roughly 2,166 tokens of context every time the server is loaded.

Is the Circuitarium MCP server still maintained?

Circuitarium MCP is still listed as active in the MCP registry. We last reached this channel on 5 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 Circuitarium MCP server under?

Circuitarium MCP declares the Apache-2.0 licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.