Circuitarium MCP
NPM · CIRCUITARIUM-MCP · SCANNED SEP 20
MCP tools for CRUMB artifacts and Logisim-evolution analysis and non-interactive simulation.
Available components
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 Security98
- No malware found by supply-chain analysis.Pass
- No known CVEs affecting this package version or its production dependencies.Pass
- No install/post-install scripts declared.Pass
- 33 of 106 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 52 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 Management87
- Stability observed for 26 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
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
claude mcp add craftiee-circuitarium -- npx -y circuitarium-mcp
{
"mcpServers": {
"craftiee-circuitarium": {
"command": "npx",
"args": [
"-y",
"circuitarium-mcp"
]
}
}
} {
"servers": {
"craftiee-circuitarium": {
"command": "npx",
"args": [
"-y",
"circuitarium-mcp"
]
}
}
} codex mcp add craftiee-circuitarium -- npx -y circuitarium-mcp
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"craftiee-circuitarium": {
"type": "local",
"command": [
"npx",
"-y",
"circuitarium-mcp"
],
"enabled": true
}
}
} openclaw mcp add craftiee-circuitarium --command npx --arg -y --arg circuitarium-mcp
mcp_servers:
craftiee-circuitarium:
command: "npx"
args: ["-y", "circuitarium-mcp"] {
"McpServers": {
"craftiee-circuitarium": {
"Transport": "stdio",
"Command": "npx",
"Arguments": [
"-y",
"circuitarium-mcp"
]
}
}
} assistant mcp add craftiee-circuitarium -t stdio -c npx -a -y circuitarium-mcp
{
"mcpServers": {
"craftiee-circuitarium": {
"command": "npx",
"args": [
"-y",
"circuitarium-mcp"
]
}
}
} 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.
- 20 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 83 to 87. That category is still filling its 30-day observation window: 25 days of observed history at the previous scan, 26 at this one. The score rises as the window fills, whether or not the server changes.
- 18 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 77 to 80. That category is still filling its 30-day observation window: 23 days of observed history at the previous scan, 24 at this one. The score rises as the window fills, whether or not the server changes.
- 17 Sept 26 −4
- Stability: pass → 0.77 functional
- 16 Sept 26 +1
- Stability: 0.97 → pass security
- 14 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 90 to 93. That category is still filling its 30-day observation window: 27 days of observed history at the previous scan, 28 at this one. The score rises as the window fills, whether or not the server changes.
- 12 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 83 to 87. That category is still filling its 30-day observation window: 25 days of observed history at the previous scan, 26 at this one. The score rises as the window fills, whether or not the server changes.
- 10 Sept 26 −3
- Stability: pass → 0.80 functional
- 9 Sept 26 +1
- Stability: 0.97 → 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 20 Sept 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 | https://slsa.dev/provenance/v1 |
| Subject digest | sha512:833ddfebd22071fa8a899dd6258fc0fd2e49445c897bf8301058696dade42ca0a84aa885dcaa25e4d5ccc29d22efeac272db956865d63d6d916319946 |
Background: How many MCP packages publish verified provenance →
Dependencies 106 packages
| Packages resolved | 106 |
|---|---|
| Stale | 33 |
| 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 →
crumb_analyze_design Analyze a CRUMB design semantically ~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.
| Name | Type | Req | Description |
|---|---|---|---|
| cursor | string | – | – |
| expectedProjectDigest | string | – | Optional sha256: digest from a prior cross-model handoff |
| includeGeometry | boolean | – | – |
| includeSourceCode | boolean | – | – |
| limit | integer | – | – |
| path | string | yes | Workspace-relative .cru project ref |
| topologyMode | string | – | – |
| view | string | – | – |
| Name | Type | Req | Description |
|---|---|---|---|
| context | object | yes | – |
| contractVersion | string | yes | – |
| data | object | – | – |
| diagnostics | array | yes | – |
| error | object | – | – |
| nextActions | array | yes | – |
| ok | boolean | yes | – |
| summary | string | yes | – |
No examples provided.
crumb_bom Build a bill of materials ~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.
| Name | Type | Req | Description |
|---|---|---|---|
| expectedProjectDigest | string | – | – |
| limit | integer | – | – |
| path | string | yes | Workspace-relative .cru project ref |
| Name | Type | Req | Description |
|---|---|---|---|
| context | object | yes | – |
| contractVersion | string | yes | – |
| data | object | – | – |
| diagnostics | array | yes | – |
| error | object | – | – |
| nextActions | array | yes | – |
| ok | boolean | yes | – |
| summary | string | yes | – |
No examples provided.
crumb_check_design Run electrical rule checks ~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.
| Name | Type | Req | Description |
|---|---|---|---|
| applySwitchStates | boolean | – | – |
| expectedProjectDigest | string | – | – |
| path | string | yes | Workspace-relative .cru project ref |
| topologyMode | string | – | – |
| Name | Type | Req | Description |
|---|---|---|---|
| context | object | yes | – |
| contractVersion | string | yes | – |
| data | object | – | – |
| diagnostics | array | yes | – |
| error | object | – | – |
| nextActions | array | yes | – |
| ok | boolean | yes | – |
| summary | string | yes | – |
No examples provided.
crumb_compare_designs Compare CRUMB files under the Unity profile ~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.
| Name | Type | Req | Description |
|---|---|---|---|
| baselinePath | string | yes | Workspace-relative baseline .cru project ref |
| candidatePath | string | yes | Workspace-relative candidate .cru project ref |
| compatibilityProfile | string | – | – |
| cursor | string | – | – |
| expectedBaselineDigest | string | – | Optional sha256: digest previously recorded for the baseline |
| expectedCandidateDigest | string | – | Optional sha256: digest previously recorded for the candidate |
| includeGeometry | boolean | – | – |
| limit | integer | – | – |
| topologyMode | string | – | – |
| view | string | – | – |
| Name | Type | Req | Description |
|---|---|---|---|
| context | object | yes | – |
| contractVersion | string | yes | – |
| data | object | – | – |
| diagnostics | array | yes | – |
| error | object | – | – |
| nextActions | array | yes | – |
| ok | boolean | yes | – |
| summary | string | yes | – |
No examples provided.
crumb_component_catalog List recognized CRUMB component schemas ~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.
| Name | Type | Req | Description |
|---|---|---|---|
| toolId | integer | – | – |
| Name | Type | Req | Description |
|---|---|---|---|
| context | object | yes | – |
| contractVersion | string | yes | – |
| data | object | – | – |
| diagnostics | array | yes | – |
| error | object | – | – |
| nextActions | array | yes | – |
| ok | boolean | yes | – |
| summary | string | yes | – |
No examples provided.
crumb_export_netlist Export named electrical nets ~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.
| Name | Type | Req | Description |
|---|---|---|---|
| applySwitchStates | boolean | – | Merge nets across saved switch positions using installed-build semantics |
| cursor | string | – | – |
| expectedProjectDigest | string | – | – |
| limit | integer | – | – |
| path | string | yes | Workspace-relative .cru project ref |
| topologyMode | string | – | – |
| Name | Type | Req | Description |
|---|---|---|---|
| context | object | yes | – |
| contractVersion | string | yes | – |
| data | object | – | – |
| diagnostics | array | yes | – |
| error | object | – | – |
| nextActions | array | yes | – |
| ok | boolean | yes | – |
| summary | string | yes | – |
No examples provided.
crumb_generate_fixture Generate a synthetic CRUMB fixture ~65
Creates one known fixture without overwriting. Provide outputPath for a file artifact; raw XML is returned only when includeXml=true.
| Name | Type | Req | Description |
|---|---|---|---|
| includeXml | boolean | – | – |
| kind | string | yes | – |
| name | string | – | – |
| outputPath | string | – | – |
| Name | Type | Req | Description |
|---|---|---|---|
| context | object | yes | – |
| contractVersion | string | yes | – |
| data | object | – | – |
| diagnostics | array | yes | – |
| error | object | – | – |
| nextActions | array | yes | – |
| ok | boolean | yes | – |
| summary | string | yes | – |
No examples provided.
crumb_get_component Fetch one CRUMB component in full detail ~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.
| Name | Type | Req | Description |
|---|---|---|---|
| componentId | string | yes | Component id from analyze/netlist output; matching is case-insensitive |
| expectedProjectDigest | string | – | Optional sha256: digest from a prior cross-model handoff |
| includeGeometry | boolean | – | – |
| includeSourceCode | boolean | – | – |
| path | string | yes | Workspace-relative .cru project ref |
| sourceOffset | integer | – | Character offset into embedded firmware source for continued reads |
| topologyMode | string | – | – |
| Name | Type | Req | Description |
|---|---|---|---|
| context | object | yes | – |
| contractVersion | string | yes | – |
| data | object | – | – |
| diagnostics | array | yes | – |
| error | object | – | – |
| nextActions | array | yes | – |
| ok | boolean | yes | – |
| summary | string | yes | – |
No examples provided.
crumb_ic_reference Look up CRUMB IC packages and pinouts ~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.
| Name | Type | Req | Description |
|---|---|---|---|
| prefabId | integer | – | – |
| query | string | – | Case-insensitive substring matched against IC label and package name |
| Name | Type | Req | Description |
|---|---|---|---|
| context | object | yes | – |
| contractVersion | string | yes | – |
| data | object | – | – |
| diagnostics | array | yes | – |
| error | object | – | – |
| nextActions | array | yes | – |
| ok | boolean | yes | – |
| summary | string | yes | – |
No examples provided.
crumb_inspect_design Inspect compact CRUMB metadata ~69
Returns a bounded save summary and tool-ID counts. Use crumb_analyze_design for paginated semantic component and connection details.
| Name | Type | Req | Description |
|---|---|---|---|
| expectedProjectDigest | string | – | Optional sha256: digest from a prior cross-model handoff |
| path | string | yes | Workspace-relative .cru project ref |
| Name | Type | Req | Description |
|---|---|---|---|
| context | object | yes | – |
| contractVersion | string | yes | – |
| data | object | – | – |
| diagnostics | array | yes | – |
| error | object | – | – |
| nextActions | array | yes | – |
| ok | boolean | yes | – |
| summary | string | yes | – |
No examples provided.
crumb_list_projects List CRUMB projects in the workspace ~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.
| Name | Type | Req | Description |
|---|---|---|---|
| dir | string | – | Workspace-relative directory ref to list |
| includeDigests | boolean | – | – |
| limit | integer | – | – |
| recursive | boolean | – | – |
| Name | Type | Req | Description |
|---|---|---|---|
| context | object | yes | – |
| contractVersion | string | yes | – |
| data | object | – | – |
| diagnostics | array | yes | – |
| error | object | – | – |
| nextActions | array | yes | – |
| ok | boolean | yes | – |
| summary | string | yes | – |
No examples provided.
crumb_trace_net Trace one inferred CRUMB electrical 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.
| Name | Type | Req | Description |
|---|---|---|---|
| applySwitchStates | boolean | – | Apply persisted switch closures as conditional installed-build evidence |
| componentId | string | yes | Case-insensitive component id from CRUMB analysis |
| cursor | string | – | – |
| expectedProjectDigest | string | – | – |
| expectedTerminalName | string | – | Optional exact-name guard for cross-model handoff |
| limit | integer | – | – |
| path | string | yes | Workspace-relative .cru project ref |
| terminalIndex | integer | yes | Zero-based terminal index; canonical within the exact project bytes |
| topologyMode | string | – | – |
| Name | Type | Req | Description |
|---|---|---|---|
| context | object | yes | – |
| contractVersion | string | yes | – |
| data | object | – | – |
| diagnostics | array | yes | – |
| error | object | – | – |
| nextActions | array | yes | – |
| ok | boolean | yes | – |
| summary | string | yes | – |
No examples provided.
crumb_validate_design Validate a CRUMB design ~67
Performs XML and CRUMB structural checks without launching the game. A bad design returns ok=true and data.valid=false.
| Name | Type | Req | Description |
|---|---|---|---|
| expectedProjectDigest | string | – | Optional sha256: digest from a prior cross-model handoff |
| path | string | yes | Workspace-relative .cru project ref |
| Name | Type | Req | Description |
|---|---|---|---|
| context | object | yes | – |
| contractVersion | string | yes | – |
| data | object | – | – |
| diagnostics | array | yes | – |
| error | object | – | – |
| nextActions | array | yes | – |
| ok | boolean | yes | – |
| summary | string | yes | – |
No examples provided.
electronics_capabilities Orient to Circuitarium MCP ~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.
| Name | Type | Req | Description |
|---|---|---|---|
| context | object | yes | – |
| contractVersion | string | yes | – |
| data | object | – | – |
| diagnostics | array | yes | – |
| error | object | – | – |
| nextActions | array | yes | – |
| ok | boolean | yes | – |
| summary | string | yes | – |
No examples provided.
electronics_plan_verification Plan evidence-aware electronics 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.
| Name | Type | Req | Description |
|---|---|---|---|
| claims | array | yes | – |
| declaredInterface | object | – | – |
| evidence | array | – | – |
| target | – | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| context | object | yes | – |
| contractVersion | string | yes | – |
| data | object | – | – |
| diagnostics | array | yes | – |
| error | object | – | – |
| nextActions | array | yes | – |
| ok | boolean | yes | – |
| summary | string | yes | – |
No examples provided.
electronics_validate_experiment Validate a portable electronics 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.
| Name | Type | Req | Description |
|---|---|---|---|
| experiment | – | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| context | object | yes | – |
| contractVersion | string | yes | – |
| data | object | – | – |
| diagnostics | array | yes | – |
| error | object | – | – |
| nextActions | array | yes | – |
| ok | boolean | yes | – |
| summary | string | yes | – |
No examples provided.
logisim_analyze_design Analyze a Logisim-evolution project ~90
Parses bounded .circ XML into project, circuit, pin, clock, component, and explicit conversion-loss summaries. Static parsing is not simulation evidence.
| Name | Type | Req | Description |
|---|---|---|---|
| circuit | string | – | Circuit name; defaults to the declared main circuit |
| expectedProjectDigest | string | – | Optional sha256: digest from a prior cross-model handoff |
| path | string | yes | Workspace-relative .circ project ref |
| Name | Type | Req | Description |
|---|---|---|---|
| context | object | yes | – |
| contractVersion | string | yes | – |
| data | object | – | – |
| diagnostics | array | yes | – |
| error | object | – | – |
| nextActions | array | yes | – |
| ok | boolean | yes | – |
| summary | string | yes | – |
No examples provided.
logisim_component_stats Load a project and count Logisim components ~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.
| Name | Type | Req | Description |
|---|---|---|---|
| circuit | string | – | Circuit name; defaults to the declared main circuit |
| expectedProjectDigest | string | – | Optional sha256: digest from a prior cross-model handoff |
| limit | integer | – | – |
| path | string | yes | Workspace-relative .circ project ref |
| timeoutMs | integer | – | – |
| Name | Type | Req | Description |
|---|---|---|---|
| context | object | yes | – |
| contractVersion | string | yes | – |
| data | object | – | – |
| diagnostics | array | yes | – |
| error | object | – | – |
| nextActions | array | yes | – |
| ok | boolean | yes | – |
| summary | string | yes | – |
No examples provided.
logisim_export_netlist Export a partial Logisim netlist ~107
Exports simulator-neutral coordinate-endpoint nets with explicit loss markers. It does not infer unmodeled gate geometry, mid-segment junctions, or behavior.
| Name | Type | Req | Description |
|---|---|---|---|
| circuit | string | – | Circuit name; defaults to the declared main circuit |
| cursor | string | – | – |
| expectedProjectDigest | string | – | Optional sha256: digest from a prior cross-model handoff |
| limit | integer | – | – |
| path | string | yes | Workspace-relative .circ project ref |
| Name | Type | Req | Description |
|---|---|---|---|
| context | object | yes | – |
| contractVersion | string | yes | – |
| data | object | – | – |
| diagnostics | array | yes | – |
| error | object | – | – |
| nextActions | array | yes | – |
| ok | boolean | yes | – |
| summary | string | yes | – |
No examples provided.
logisim_list_projects List Logisim-evolution projects ~62
Discovers workspace .circ projects with stable raw-byte digests. This is static file discovery and does not launch Logisim.
| Name | Type | Req | Description |
|---|---|---|---|
| dir | string | – | Workspace-relative directory ref to list |
| limit | integer | – | – |
| recursive | boolean | – | – |
| Name | Type | Req | Description |
|---|---|---|---|
| context | object | yes | – |
| contractVersion | string | yes | – |
| data | object | – | – |
| diagnostics | array | yes | – |
| error | object | – | – |
| nextActions | array | yes | – |
| ok | boolean | yes | – |
| summary | string | yes | – |
No examples provided.
logisim_run_test_vector Run a Logisim 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.
| Name | Type | Req | Description |
|---|---|---|---|
| circuit | string | – | Circuit name; defaults to the declared main circuit |
| expectedProjectDigest | string | – | Optional sha256: digest from a prior cross-model handoff |
| expectedVectorDigest | string | – | – |
| maxFailures | integer | – | – |
| path | string | yes | Workspace-relative .circ project ref |
| timeoutMs | integer | – | – |
| vectorPath | string | yes | Workspace-relative .vec or .txt test-vector ref |
| Name | Type | Req | Description |
|---|---|---|---|
| context | object | yes | – |
| contractVersion | string | yes | – |
| data | object | – | – |
| diagnostics | array | yes | – |
| error | object | – | – |
| nextActions | array | yes | – |
| ok | boolean | yes | – |
| summary | string | yes | – |
No examples provided.
logisim_truth_table Simulate a bounded 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.
| Name | Type | Req | Description |
|---|---|---|---|
| circuit | string | – | Circuit name; defaults to the declared main circuit |
| expectedProjectDigest | string | – | Optional sha256: digest from a prior cross-model handoff |
| limit | integer | – | – |
| maxInputBits | integer | – | – |
| path | string | yes | Workspace-relative .circ project ref |
| timeoutMs | integer | – | – |
| Name | Type | Req | Description |
|---|---|---|---|
| context | object | yes | – |
| contractVersion | string | yes | – |
| data | object | – | – |
| diagnostics | array | yes | – |
| error | object | – | – |
| nextActions | array | yes | – |
| ok | boolean | yes | – |
| summary | string | yes | – |
No examples provided.
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 94 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 20 September 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 20 September 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.