Multisim MCP
PYPI · MULTISIM-MCP
Generate Multisim circuits, run simulations, export data, and create experiment reports.
Available components
Last scanned (21 hours ago)
Scores higher than 91% 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 Security82
- No malware found by supply-chain analysis.Pass
- CVE check failed: a known high-severity CVE affects cryptography 48.0.1, a direct dependency. A fixed version is available. View diagnostics → Fail
- Runs setuptools.build_meta at install time, a recognised build step with no custom scripting around it. View diagnostics → Pass
- 1 of 31 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 yxy050208/multisim-mcp). View diagnostics → Pass
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 7 days ago).Pass
- Publishes a security disclosure policy (SECURITY.md).Pass
Schema Quality & AI Usability77
- 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
- AI-judged instruction clarity (good).Pass
- Tool/resource definitions use about 5667 tokens (~72/item across 78 items; 78 tools + 0 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 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 (59% 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 78 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 79 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.
- 16 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 93 to 97. That category is still filling its 30-day observation window: 28 days of observed history at the previous scan, 29 at this one. The score rises as the window fills, whether or not the server changes.
- 14 Oct 26 +16
- Malware scan: unverified → pass ▲ security
- 12 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 80 to 83. That category is still filling its 30-day observation window: 24 days of observed history at the previous scan, 25 at this one. The score rises as the window fills, whether or not the server changes.
- 4 Oct 26 −3
- Stability: pass → 0.80 functional
- 3 Oct 26 0
- Stability: 0.97 → pass security
- 2 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 93 to 97. That category is still filling its 30-day observation window: 28 days of observed history at the previous scan, 29 at this one. The score rises as the window fills, whether or not the server changes.
- 30 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 87 to 90. That category is still filling its 30-day observation window: 26 days of observed history at the previous scan, 27 at this one. The score rises as the window fills, whether or not the server changes.
- 29 Sept 26 +11
- Provenance: unverified → pass ▲ security
- The attested source repository moved: yxy050208/multisim-mcp 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 16 Oct 2026 · Analysed pypi/multisim-mcp@1.2.0
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 | pypi |
| Reason | Verified |
| Discovered via | Registry attestation endpoint |
| Source repo | yxy050208/multisim-mcp |
| Certificate issuer | https://token.actions.githubusercontent.com |
| Certificate SAN | https://github.com/yxy050208/multisim-mcp/.github/workflows/publish-pypi.yml@refs/tags/v1.2.0 |
| Rekor log index | 2698787646 |
| Predicate type | PyPI publish attestation https://docs.pypi.org/attestations/publish/v1 |
| Subject digest | sha256:701f40c7c8625a4377e67de471cf6e071fb9d2b0ae897ad64f1554838bc1e256 |
Background: How many MCP packages publish verified provenance →
Install scripts 1 script
| Hook | Tier | Command |
|---|---|---|
| build_backend | allowlisted | setuptools.build_meta |
Background: Why install scripts are a supply-chain risk →
Vulnerabilities 6 findings
| ID | CVE | Severity | Vector | Fix available |
|---|---|---|---|---|
| GHSA-g6cj-pr64-35w5 | CVE-2026-69247 | high | yes | |
| GHSA-jwv3-5hgf-82ww | CVE-2026-69249 | high | yes | |
| GHSA-m2h6-j472-rp4c | CVE-2026-69248 | medium | yes | |
| PYSEC-2026-3552 | CVE-2026-69247 | none | yes | |
| PYSEC-2026-3553 | CVE-2026-69249 | none | yes | |
| PYSEC-2026-3554 | CVE-2026-69248 | none | yes |
Background: What a vulnerability scan can and cannot prove →
Dependencies 31 packages
| Packages resolved | 31 |
|---|---|
| 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 →
report_bom ~41
Export the bill of materials to a text file.
| Name | Type | Req | Description |
|---|---|---|---|
| fmt | integer | – | – |
| path | string | yes | – |
| real_flag | boolean | – | – |
No output schema declared.
No examples provided.
report_netlist ~42
Export the SPICE netlist to a text file.
| Name | Type | Req | Description |
|---|---|---|---|
| fmt | integer | – | – |
| path | string | yes | – |
| probes_flag | boolean | – | – |
No output schema declared.
No examples provided.
resolve_component_requirements ~92
Resolve logical roles into reviewable component candidates and rating gates. This remains a read-only planning step. It does not choose a silent part number, create a CircuitDesign, generate SPICE, write a file, or start a simulation. A later stage must provide model provenance and explicit human approval before compiling an executable netlist.
| Name | Type | Req | Description |
|---|---|---|---|
| draft | object | yes | – |
| selections | – | – | – |
Structured output declared, but exposes no named fields.
No examples provided.
retry_experiment_job ~34
Queue a fresh attempt using a failed, cancelled, or timed-out job spec.
| Name | Type | Req | Description |
|---|---|---|---|
| job_id | string | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| job_id | string | yes | – |
| output_dir | string | yes | – |
| state | string | yes | – |
| status_uri | string | yes | – |
| success | boolean | yes | – |
No examples provided.
run_ac_single_frequency ~48
Run AC analysis at a single frequency.
| Name | Type | Req | Description |
|---|---|---|---|
| frequency | number | – | – |
| max_points | integer | – | – |
| output_names | array | yes | – |
| timeout | number | – | – |
No output schema declared.
No examples provided.
run_ac_sweep ~77
Run AC sweep and return frequency/real/imag rows.
| Name | Type | Req | Description |
|---|---|---|---|
| max_points | integer | – | – |
| num_points | integer | – | – |
| output_names | array | yes | – |
| start_frequency | number | – | – |
| stop_frequency | number | – | – |
| sweep_type | integer | – | – |
| timeout | number | – | – |
No output schema declared.
No examples provided.
run_behavioral_reference ~161
Build and run an explicit ngspice behavioral reference in one call. This workflow is intentionally opt-in: it only accepts a netlist containing a supported native ``DFF8``/``7474N``-family carrier, converts that carrier to the portable ``@DFF`` reference, and then runs the converted netlist through the explicitly selected ngspice backend. The source design is not modified, and the result must not be interpreted as native Multisim 74LS74 timing or electrical-equivalence evidence.
| Name | Type | Req | Description |
|---|---|---|---|
| commands | string | yes | – |
| max_points | integer | – | – |
| netlist | string | yes | – |
| output_dir | – | – | – |
| overwrite | boolean | – | – |
| timeout | number | – | – |
Structured output declared, but exposes no named fields.
No examples provided.
run_circuit_experiment ~111
Create a schematic, run a safe Multisim analysis, and export a report. This synchronous compatibility tool blocks until completion. For queueing, progress, cancellation, persisted state, and worker recovery, prefer ``submit_circuit_experiment``.
| Name | Type | Req | Description |
|---|---|---|---|
| commands | string | yes | – |
| max_points | integer | – | – |
| netlist | string | yes | – |
| output_dir | string | yes | – |
| overwrite | boolean | – | – |
| timeout | number | – | – |
| title | string | – | – |
| Name | Type | Req | Description |
|---|---|---|---|
| experiment_id | string | yes | – |
| output_dir | string | yes | – |
| plot | string | yes | – |
| report | string | yes | – |
| resources | object | yes | – |
| schematic | object | yes | – |
| simulation | object | yes | – |
| success | boolean | yes | – |
No examples provided.
run_dc_operating_point ~44
Run DC operating point analysis for the given outputs.
| Name | Type | Req | Description |
|---|---|---|---|
| max_points | integer | – | – |
| output_names | array | yes | – |
| timeout | number | – | – |
No output schema declared.
No examples provided.
run_experiment_sweep ~64
Run a transactional parameter, tolerance, temperature, or Monte Carlo sweep.
| Name | Type | Req | Description |
|---|---|---|---|
| max_points | integer | – | – |
| output_dir | string | yes | – |
| overwrite | boolean | – | – |
| spec | object | yes | – |
| timeout_per_run | number | – | – |
Structured output declared, but exposes no named fields.
No examples provided.
run_spice_netlist ~124
Run SPICE through Multisim or ngspice with safe analysis commands. The default path rejects scripting, shell escapes, file commands, and arbitrary command sourcing. Unrestricted engine commands require both the ``unsafe_commands`` argument and an explicit server-side environment flag.
| Name | Type | Req | Description |
|---|---|---|---|
| backend | string | – | – |
| commands | string | yes | – |
| max_points | integer | – | – |
| netlist | string | yes | – |
| output_dir | – | – | – |
| overwrite | boolean | – | – |
| timeout | number | – | – |
| unsafe_commands | boolean | – | – |
No output schema declared.
No examples provided.
run_transient ~77
Run a transient simulation and return downsampled time/real data.
| Name | Type | Req | Description |
|---|---|---|---|
| duration | number | – | – |
| max_points | integer | – | – |
| num_samples | integer | – | – |
| output_name | string | yes | – |
| repeat_flag | boolean | – | – |
| sample_rate | number | – | – |
| timeout | number | – | – |
No output schema declared.
No examples provided.
run_verified_circuit_experiment ~134
Run an ExperimentSpec and persist evidence-backed requirement verdicts. When the three approval inputs are supplied, the exact executable-netlist and simulation-plan handoff is revalidated before any schematic or simulation work begins. The legacy direct-spec path remains available for compatibility; it does not claim this additional approval provenance.
| Name | Type | Req | Description |
|---|---|---|---|
| executable_netlist | – | – | – |
| max_points | integer | – | – |
| netlist_approval | – | – | – |
| output_dir | string | yes | – |
| overwrite | boolean | – | – |
| simulation_plan_approval | – | – | – |
| spec | – | yes | – |
| timeout | number | – | – |
| Name | Type | Req | Description |
|---|---|---|---|
| experiment_id | string | yes | – |
| output_dir | string | yes | – |
| plot | string | yes | – |
| report | string | yes | – |
| resources | object | yes | – |
| schematic | object | yes | – |
| simulation | object | yes | – |
| success | boolean | yes | – |
| verification | object | yes | – |
| verification_path | string | yes | – |
No examples provided.
runtime_status ~19
Check local EDA runtime compatibility without starting Multisim.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
save_circuit ~24
Save the circuit, optionally to a new path.
| Name | Type | Req | Description |
|---|---|---|---|
| path | – | – | – |
No output schema declared.
No examples provided.
schematic_component_catalog ~19
List native component families available to the schematic generator.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
select_design_option ~73
Lock one planning option without generating or executing a circuit. The input plan digest is checked before selection. The returned envelope binds the source and selected digests so a later generator can require an explicit, untampered handoff.
| Name | Type | Req | Description |
|---|---|---|---|
| option_id | string | yes | – |
| plan | object | yes | – |
Structured output declared, but exposes no named fields.
No examples provided.
set_input_data_raw ~54
Inject a raw (time, value) waveform into a simulation input.
| Name | Type | Req | Description |
|---|---|---|---|
| input_name | string | yes | – |
| repeat_flag | boolean | – | – |
| times | array | yes | – |
| values | array | yes | – |
No output schema declared.
No examples provided.
set_input_data_sampled ~51
Inject a sampled waveform into a simulation input.
| Name | Type | Req | Description |
|---|---|---|---|
| input_name | string | yes | – |
| repeat_flag | boolean | – | – |
| sample_rate | number | yes | – |
| values | array | yes | – |
No output schema declared.
No examples provided.
set_output_request ~56
Configure an output request before RunSimulation.
| Name | Type | Req | Description |
|---|---|---|---|
| method | integer | – | – |
| num_samples | integer | – | – |
| output_name | string | yes | – |
| repeat_flag | boolean | – | – |
| sample_rate | number | – | – |
No output schema declared.
No examples provided.
set_rlc_value ~38
Set an R/L/C component value through SetRLCValue.
| Name | Type | Req | Description |
|---|---|---|---|
| component_name | string | yes | – |
| value | number | yes | – |
No output schema declared.
No examples provided.
stop_simulation ~15
Stop the currently running simulation.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
submit_autonomous_correction ~188
Queue durable model-planned correction with round-level recovery. The persisted provider configuration is validated and secret-free: it contains only endpoint/model metadata and environment-variable names. API keys are resolved by the isolated worker and are never written to job state. Completed rounds are evidence-revalidated; an incomplete planning round is replanned in a new attempt directory. No patch is applied automatically.
| Name | Type | Req | Description |
|---|---|---|---|
| allow_failover | boolean | – | – |
| design | object | yes | – |
| fallback_providers | – | – | – |
| heartbeat_timeout | number | – | – |
| job_timeout | number | – | – |
| max_points | integer | – | – |
| model_timeout | number | – | – |
| output_dir | string | yes | – |
| provider | – | – | – |
| provider_config_path | – | – | – |
| resume_existing | boolean | – | – |
| spec | object | yes | – |
| timeout_per_experiment | number | – | – |
| Name | Type | Req | Description |
|---|---|---|---|
| job_id | string | yes | – |
| output_dir | string | yes | – |
| state | string | yes | – |
| status_uri | string | yes | – |
| success | boolean | yes | – |
No examples provided.
submit_circuit_experiment ~200
Queue a durable, cancellable experiment in an isolated worker process. Prefer this tool for long experiments. Poll ``multisim://jobs/{job_id}`` or call ``get_experiment_job``. Completed jobs return the same experiment result and resource handles as ``run_circuit_experiment``. When approval artifacts are supplied, all three are persisted with the job and verified again inside the isolated worker before execution.
| Name | Type | Req | Description |
|---|---|---|---|
| commands | string | yes | – |
| executable_netlist | – | – | – |
| heartbeat_timeout | number | – | – |
| job_timeout | number | – | – |
| max_points | integer | – | – |
| netlist | string | yes | – |
| netlist_approval | – | – | – |
| output_dir | string | yes | – |
| overwrite | boolean | – | – |
| requirements | – | – | – |
| simulation_plan_approval | – | – | – |
| theoretical_values | – | – | – |
| timeout | number | – | – |
| title | string | – | – |
| Name | Type | Req | Description |
|---|---|---|---|
| job_id | string | yes | – |
| output_dir | string | yes | – |
| state | string | yes | – |
| status_uri | string | yes | – |
| success | boolean | yes | – |
No examples provided.
submit_design_optimization ~141
Queue a durable optimization with candidate-level crash recovery. Completed candidates are evidence-verified and reused after a worker or MCP restart. An interrupted candidate is rerun in a new attempt directory. The result still returns only a proposed patch and never modifies the design. Set ``resume_existing`` only to adopt a matching interrupted output folder.
| Name | Type | Req | Description |
|---|---|---|---|
| design | object | yes | – |
| heartbeat_timeout | number | – | – |
| job_timeout | number | – | – |
| max_points | integer | – | – |
| output_dir | string | yes | – |
| resume_existing | boolean | – | – |
| spec | object | yes | – |
| timeout_per_experiment | number | – | – |
| Name | Type | Req | Description |
|---|---|---|---|
| job_id | string | yes | – |
| output_dir | string | yes | – |
| state | string | yes | – |
| status_uri | string | yes | – |
| success | boolean | yes | – |
No examples provided.
submit_experiment_sweep ~80
Queue a durable sweep in the same isolated, cancellable worker system.
| Name | Type | Req | Description |
|---|---|---|---|
| heartbeat_timeout | number | – | – |
| job_timeout | number | – | – |
| max_points | integer | – | – |
| output_dir | string | yes | – |
| overwrite | boolean | – | – |
| spec | object | yes | – |
| timeout_per_run | number | – | – |
| Name | Type | Req | Description |
|---|---|---|---|
| job_id | string | yes | – |
| output_dir | string | yes | – |
| state | string | yes | – |
| status_uri | string | yes | – |
| success | boolean | yes | – |
No examples provided.
submit_global_optimization ~120
Queue durable mixed topology/value Pareto optimization. Completed candidates are integrity-checked and reused after restart. An interrupted candidate is rerun in a new attempt directory. No recommended patch is persisted into the source design automatically.
| Name | Type | Req | Description |
|---|---|---|---|
| design | object | yes | – |
| heartbeat_timeout | number | – | – |
| job_timeout | number | – | – |
| max_points | integer | – | – |
| output_dir | string | yes | – |
| resume_existing | boolean | – | – |
| spec | object | yes | – |
| timeout_per_experiment | number | – | – |
| Name | Type | Req | Description |
|---|---|---|---|
| job_id | string | yes | – |
| output_dir | string | yes | – |
| state | string | yes | – |
| status_uri | string | yes | – |
| success | boolean | yes | – |
No examples provided.
verify_experiment_requirements ~43
Evaluate explicit design requirements; unsupported evidence stays unverified.
| Name | Type | Req | Description |
|---|---|---|---|
| experiment_id | string | yes | – |
| requirements | array | yes | – |
| theoretical_values | – | – | – |
Structured output declared, but exposes no named fields.
No examples provided.
How do I install the Multisim MCP server?
Multisim MCP runs locally as a PyPI package, launched with uvx multisim-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 · multisim-mcp
claude mcp add yxy050208-multisim-mcp -- uvx multisim-mcp
What is the Multisim MCP server?
Multisim MCP is listed in the public MCP registry as io.github.yxy050208/multisim-mcp. Generate Multisim circuits, run simulations, export data, and create experiment reports. This page covers its PyPI package (multisim-mcp).
Is the Multisim MCP server safe to use?
Multisim MCP scores 88 out of 100 on VerifyMCP. We recorded 6 known advisories against it as of 16 October 2026. 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 Multisim MCP server expose?
Multisim MCP exposes 78 tools: connect, runtime_status, register_experiment_artifacts, list_experiment_artifacts, read_experiment_artifact, and 73 more. Their descriptions and schemas cost roughly 5,376 tokens of context every time the server is loaded.
Is the Multisim MCP server still maintained?
Multisim MCP is still listed as active in the MCP registry. We last reached this channel on 16 October 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 Multisim MCP server under?
Multisim 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.