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.

Multisim MCP

PYPI · MULTISIM-MCP

Generate Multisim circuits, run simulations, export data, and create experiment reports.

Available components

+18 this week 88 Trust /100

Last scanned (20 hours ago)

Scores higher than 91% of PyPI 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 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
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.

  • 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
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 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 →

MCP tools · 78 exposed · ~5,376 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
analyze_bode_response ~62

Use the Bode Plotter adapter on an AC-sweep experiment.

NameTypeReqDescription
experiment_idstringyes–
frequency_signal–––
input_signalstringyes–
max_pointsinteger––
output_signalstringyes–

Structured output declared, but exposes no named fields.

No examples provided.

analyze_logic_signals ~59

Use the Logic Analyzer adapter to digitize traces and list edges.

NameTypeReqDescription
experiment_idstringyes–
max_eventsinteger––
signalsarrayyes–
thresholdnumber––
time_signal–––

Structured output declared, but exposes no named fields.

No examples provided.

approve_component_resolution ~85

Record explicit human approval for a complete component resolution. This is still a review artifact. It does not generate SPICE, create a CircuitDesign, write a file, render a schematic, or start a simulation; those actions require a later compiler and separate approval gates.

NameTypeReqDescription
approvalobjectyes–
draftobjectyes–
resolutionobjectyes–

Structured output declared, but exposes no named fields.

No examples provided.

approve_executable_netlist ~79

Record explicit human approval for one immutable netlist preview. The approval binds the compiled CircuitDesign and SPICE digest. It does not write a schematic, create a project file, add stimuli, or start a simulation; those remain separate downstream gates.

NameTypeReqDescription
approvalobjectyes–
executable_netlistobjectyes–

Structured output declared, but exposes no named fields.

No examples provided.

approve_simulation_plan ~112

Record explicit approval for one safe simulation plan. The artifact binds the approved executable-netlist preview to the exact analysis commands, measurement requirements, and theoretical values in an ``ExperimentSpec``. It does not create a schematic, write files, or start a simulation; ``run_verified_circuit_experiment`` must validate it again.

NameTypeReqDescription
approvalobjectyes–
executable_netlistobjectyes–
experiment_specobjectyes–
netlist_approvalobjectyes–

Structured output declared, but exposes no named fields.

No examples provided.

audit_spice_compatibility ~55

Audit SPICE dialect, model hashes/licenses, and static backend risks.

NameTypeReqDescription
backendstring––
declared_dialect–––
model_references–––
netliststringyes–

Structured output declared, but exposes no named fields.

No examples provided.

autonomous_correct_design ~149

Autonomously diagnose, propose, simulate, and select a repair candidate. The configured model may propose bounded parameter or topology patches, but every candidate is revalidated and simulated locally. The final all-pass candidate is returned as one reversible patch against the original design; applying it remains a separate explicit approval operation.

NameTypeReqDescription
allow_failoverboolean––
designobjectyes–
fallback_providers–––
max_pointsinteger––
model_timeoutnumber––
output_dirstringyes–
provider–––
provider_config_path–––
specobjectyes–
timeout_per_experimentnumber––

Structured output declared, but exposes no named fields.

No examples provided.

build_behavioral_reference ~141

Convert supported native DFF carriers into an explicit ngspice reference. The returned netlist is not run automatically and never replaces the source design. It maps native ``D, ~PR, ~CLR, CLK, Q, ~Q, GND, VCC`` pins to the portable ``@DFF`` adapter, inserts explicit control inverters for active-low ``~PR/~CLR``, and records the behavioral-only claim. Pass the returned ``netlist`` explicitly to ``run_spice_netlist`` with ``backend='ngspice'`` when a reference run is desired.

NameTypeReqDescription
netliststringyes–

Structured output declared, but exposes no named fields.

No examples provided.

build_course_waveform_demo ~116

Return the bilingual five-waveform course-design contract. With no arguments this returns the safe behavioral reference model. A caller may provide a native Multisim-compatible netlist and analysis commands to keep the same explicit requirement gates while changing the implementation. This tool only builds/validates the contract; use ``run_verified_circuit_experiment`` for measured evidence.

NameTypeReqDescription
commandsstring––
component_evidence–––
experiment_evidence–––
netliststring––

Structured output declared, but exposes no named fields.

No examples provided.

cancel_experiment_job ~30

Cancel a queued job or safely stop its isolated worker process.

NameTypeReqDescription
job_idstringyes–

Structured output declared, but exposes no named fields.

No examples provided.

circuit_info ~24

Return name, file, simulation state, and last error for the open circuit.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

clear_input_data ~25

Clear injected data from a simulation input.

NameTypeReqDescription
input_namestringyes–

No output schema declared.

No examples provided.

compare_design_variants ~103

Rank 2-16 complete designs using one evidence-backed experiment contract. Each item must contain exactly ``variant_id`` and ``design``. All requirements are hard constraints, only finite measured passes are ranked, and no source design is modified or automatically adopted.

NameTypeReqDescription
max_pointsinteger––
output_dirstringyes–
specobjectyes–
timeout_per_experimentnumber––
variantsarrayyes–

Structured output declared, but exposes no named fields.

No examples provided.

compare_experiment_backends ~75

Numerically compare common signals from two registered EDA experiments.

NameTypeReqDescription
absolute_tolerancenumber––
candidate_experiment_idstringyes–
max_pointsinteger––
reference_experiment_idstringyes–
relative_tolerance_percentnumber––
signals–––

Structured output declared, but exposes no named fields.

No examples provided.

compile_executable_netlist ~97

Compile an approved logical draft into a bounded pin-level preview. Only options in the compiler support matrix are accepted. External model bytes, when present, are re-hashed beneath ``MULTISIM_MCP_MODEL_ROOT``. The result stays in memory and does not write files, create a schematic, start Multisim, or run a simulation.

NameTypeReqDescription
component_approvalobjectyes–
draftobjectyes–

Structured output declared, but exposes no named fields.

No examples provided.

component_adapter_catalog ~20

List portable built-in and local declarative component adapters.

Input schema present but exposes no named parameters.

Structured output declared, but exposes no named fields.

No examples provided.

connect ~16

Connect to the local Multisim Automation API.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

create_schematic_from_netlist ~303

Create an editable Multisim schematic from a supported SPICE netlist. Supports RLC components, scalar/waveform voltage and current sources, B/E/F/G/H/T primitives, modeled semiconductors and switches, OPAMP5, and user-local verified TIMER8/LM555CN and DFF8/7474N native carriers, generic two-to-sixteen-terminal X subcircuits, digital devices, ground, named nets, wiring, and deterministic layout. Compatible inline subcircuits are recursively expanded into editable primitives; unsupported macro-model constructs remain explicit carrier-only evidence. Generated schematic probes remain experimental. The high-level experiment tool obtains authoritative data from the same source netlist through Multisim's command engine. When ``executable_netlist`` and ``netlist_approval`` are both supplied, the approval is revalidated against the immutable compiled preview before any schematic work begins. The supplied ``netlist`` must exactly match the approved preview's bound SPICE text. This path opens schematic generation only; it does not approve or start a simulation.

NameTypeReqDescription
executable_netlist–––
image_path–––
include_experimental_probesboolean––
netliststringyes–
netlist_approval–––
open_after_buildboolean––
output_ms14stringyes–
overwriteboolean––
probe_nets–––

No output schema declared.

No examples provided.

decode_ms14 ~35

Decode a .ms14 file to editable XML using ewd.

NameTypeReqDescription
output_xml–––
pathstringyes–

No output schema declared.

No examples provided.

diagnose_design ~110

Diagnose a circuit without modifying it or silently guessing repairs. Structural checks require only ``design``. When ``experiment_dir`` is supplied, its artifact integrity manifest and canonical netlist are verified before requirement, convergence, BJT, or op-amp evidence is used. An optional bounded ``simulation_failure`` object may contain code, type, stage, and message fields from a failed run.

NameTypeReqDescription
designobjectyes–
experiment_dirstring––
simulation_failure–––

Structured output declared, but exposes no named fields.

No examples provided.

disconnect ~17

Disconnect from Multisim and release the open circuit.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

do_command_line ~60

Run an unrestricted Multisim command file when explicitly enabled. This advanced tool is disabled by default because command files can access the filesystem and may expose engine-specific command execution features.

NameTypeReqDescription
command_filestringyes–
log_filestringyes–

No output schema declared.

No examples provided.

encode_ms14 ~36

Encode an XML design back to .ms14 using ewe.

NameTypeReqDescription
output_ms14–––
source_xmlstringyes–

No output schema declared.

No examples provided.

enum_components ~27

List component reference designators. 0 returns all.

NameTypeReqDescription
component_typeinteger––

No output schema declared.

No examples provided.

enum_inputs ~25

List simulation inputs. 0 returns all.

NameTypeReqDescription
input_typeinteger––

No output schema declared.

No examples provided.

enum_outputs ~25

List simulation outputs. 0 returns all.

NameTypeReqDescription
output_typeinteger––

No output schema declared.

No examples provided.

evaluate_design_patch ~126

Retest one explicit reversible patch against its unchanged baseline. The service runs exactly two verified experiments under the same hard requirements, writes before/after deterministic diagnoses and an inverse patch, and never persists the candidate as the source design. A passing result remains subject to the separate local approval workflow.

NameTypeReqDescription
designobjectyes–
max_pointsinteger––
output_dirstringyes–
patchobjectyes–
regenerate_source_netlistboolean––
specobjectyes–
timeout_per_experimentnumber––

Structured output declared, but exposes no named fields.

No examples provided.

export_experiment_artifact ~57

Export an artifact beneath MULTISIM_MCP_ARTIFACT_EXPORT_DIR.

NameTypeReqDescription
destination_subdirstring––
experiment_idstringyes–
namestringyes–
overwriteboolean––

Structured output declared, but exposes no named fields.

No examples provided.

export_formal_experiment_report ~32

Export bilingual HTML/PDF reports and a reproducibility manifest.

NameTypeReqDescription
experiment_idstringyes–

Structured output declared, but exposes no named fields.

No examples provided.

generate_report ~66

Write a Markdown report for the open circuit and analysis results.

NameTypeReqDescription
analyses–––
include_bomboolean––
include_imageboolean––
include_netlistboolean––
output_pathstringyes–
titlestring––

No output schema declared.

No examples provided.

get_circuit_image ~33

Export the circuit schematic as an image.

NameTypeReqDescription
image_formatinteger––
pathstringyes–

No output schema declared.

No examples provided.

get_experiment_job ~30

Return durable progress, failure diagnostics, or the completed result.

NameTypeReqDescription
job_idstringyes–

Structured output declared, but exposes no named fields.

No examples provided.

get_experiment_summary ~31

Return a compact report, verification, and artifact summary for agents.

NameTypeReqDescription
experiment_idstringyes–

Structured output declared, but exposes no named fields.

No examples provided.

get_output_data ~40

Fetch data for an output that is ready; shape depends on analysis type.

NameTypeReqDescription
max_pointsinteger––
output_namestringyes–

No output schema declared.

No examples provided.

get_rlc_value ~33

Read the current value of an R/L/C component through RLCValue.

NameTypeReqDescription
component_namestringyes–

No output schema declared.

No examples provided.

global_optimize_design ~110

Run auditable mixed topology/value multi-objective global optimization. Small declared domains are exhaustive; larger domains use deterministic Halton space filling. Every candidate runs a real verified experiment, failed hard constraints are excluded, and the result contains an epsilon-aware Pareto front. No candidate is persisted automatically.

NameTypeReqDescription
designobjectyes–
max_pointsinteger––
output_dirstringyes–
specobjectyes–
timeout_per_experimentnumber––

Structured output declared, but exposes no named fields.

No examples provided.

list_experiment_artifacts ~33

List artifact metadata, hashes, MIME types, and safe access capabilities.

NameTypeReqDescription
experiment_idstringyes–

Structured output declared, but exposes no named fields.

No examples provided.

list_experiment_jobs ~35

List recent durable jobs without returning their potentially large results.

NameTypeReqDescription
limitinteger––
statestring––

Structured output declared, but exposes no named fields.

No examples provided.

measure_experiment ~35

Compute explicit metrics from a registered experiment's raw data.

NameTypeReqDescription
experiment_idstringyes–
measurementsarrayyes–

Structured output declared, but exposes no named fields.

No examples provided.

new_circuit ~17

Create a new empty Multisim design.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

open_circuit ~27

Open a Multisim design file and return circuit info.

NameTypeReqDescription
pathstringyes–

No output schema declared.

No examples provided.

optimize_design ~131

Evaluate bounded component-value candidates without modifying the source design. The baseline consumes one experiment from ``spec.max_experiments``. Values may be explicit or generated from bounded E12/E24/E48/E96 ranges. Electrical, optional in-stock, and maximum variable-cost rules are hard constraints; failed/unverified candidates are never feasible, and the returned best patch still requires the separate local approval workflow before persistence.

NameTypeReqDescription
designobjectyes–
max_pointsinteger––
output_dirstringyes–
specobjectyes–
timeout_per_experimentnumber––

Structured output declared, but exposes no named fields.

No examples provided.

plan_design_options ~110

Return comparable technical方案 without generating or executing a circuit. The result is a bounded planning-only ``DesignPlan``. It contains a deterministic recommendation, alternative implementation paths, trade-offs, and explicit assumptions. Netlists, schematics, files, and simulations are intentionally deferred until a caller selects an option in a later step.

NameTypeReqDescription
constraints–––
context–––
max_optionsinteger––
objectives–––
requirementsstringyes–

Structured output declared, but exposes no named fields.

No examples provided.

plan_experiment_sweep ~32

Validate and preview parameter, tolerance, temperature, or Monte Carlo runs.

NameTypeReqDescription
specobjectyes–

Structured output declared, but exposes no named fields.

No examples provided.

prepare_design_specification ~78

Prepare a reviewable electrical specification from a selected plan. This read-only step lists required electrical parameters, planned modules, analyses, and validation gates. It requires a valid selection digest and never creates a CircuitDesign, netlist, schematic, file, or simulation.

NameTypeReqDescription
parameter_values–––
planobjectyes–

Structured output declared, but exposes no named fields.

No examples provided.

prepare_netlist_draft ~83

Prepare a logical netlist draft after explicit specification approval. The result contains block-level nets, connections, unresolved component requirements, and derived constraints. It is not executable SPICE and never creates a CircuitDesign, schematic, file, or simulation.

NameTypeReqDescription
approvalobjectyes–
planobjectyes–
specificationobjectyes–

Structured output declared, but exposes no named fields.

No examples provided.

read_experiment_artifact ~53

Read one bounded page from an allowlisted text experiment artifact.

NameTypeReqDescription
experiment_idstringyes–
max_charsinteger––
namestringyes–
offsetinteger––

Structured output declared, but exposes no named fields.

No examples provided.

read_virtual_multimeter ~45

Read DC, true RMS, AC RMS and range from experiment data.

NameTypeReqDescription
experiment_idstringyes–
reference_signal–––
signalstringyes–

Structured output declared, but exposes no named fields.

No examples provided.

register_experiment_artifacts ~53

Register an existing complete experiment directory as MCP Resources. Use this after a server restart when the experiment was generated earlier. Only the fixed high-level experiment artifact set is exposed.

NameTypeReqDescription
output_dirstringyes–
NameTypeReqDescription
experiment_idstringyes–
output_dirstringyes–
resourcesobjectyes–
successbooleanyes–

No examples provided.

register_sweep_artifacts ~30

Register a completed sweep directory and return opaque MCP Resources.

NameTypeReqDescription
output_dirstringyes–

Structured output declared, but exposes no named fields.

No examples provided.

Install

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

# add to Claude Code
claude mcp add yxy050208-multisim-mcp -- uvx multisim-mcp
Common questions

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.