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 · SCANNED AUG 20

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

Available components

+3 this week 64 Trust /100
Trust breakdown (6 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 →

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 native-build step with no shell scripting around it. View diagnostics → Pass
  • 2 of 33 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency35
Schema Quality & AI Usability72
  • 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
  • AI-judged instruction clarity (fair).Partial
  • Tool/resource definitions use about 2546 tokens (~49/item across 51 items; 51 tools + 0 resources), lean.Pass
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management40
  • Stability observed for 12 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 (37% of tools); any adoption earns full credit.Pass
Capabilities100
  • Implements a current MCP spec version (2026-07-28).Pass
Install

Add this component to your MCP client. Where a client-specific snippet is available, pick your client below and copy it straight into your config; otherwise use the connection detail shown.

pypi · multisim-mcp

# add to Claude Code
claude mcp add yxy050208-multisim-mcp -- uvx multisim-mcp
# add to Codex CLI
codex mcp add yxy050208-multisim-mcp -- uvx multisim-mcp
// opencode.json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "yxy050208-multisim-mcp": {
      "type": "local",
      "command": [
        "uvx",
        "multisim-mcp"
      ],
      "enabled": true
    }
  }
}
# add to OpenClaw
openclaw mcp add yxy050208-multisim-mcp --command uvx --arg multisim-mcp
# ~/.hermes/config.yaml
mcp_servers:
  yxy050208-multisim-mcp:
    command: "uvx"
    args: ["multisim-mcp"]
// mcp.json
{
  "mcpServers": {
    "yxy050208-multisim-mcp": {
      "command": "uvx",
      "args": [
        "multisim-mcp"
      ]
    }
  }
}
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.

  • 19 Aug 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 33 to 37. That category is still filling its 30-day observation window: 10 days of observed history at the previous scan, 11 at this one. The score rises as the window fills, whether or not the server changes.

  • 17 Aug 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 27 to 30. That category is still filling its 30-day observation window: 8 days of observed history at the previous scan, 9 at this one. The score rises as the window fills, whether or not the server changes.

  • 15 Aug 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 20 to 23. That category is still filling its 30-day observation window: 6 days of observed history at the previous scan, 7 at this one. The score rises as the window fills, whether or not the server changes.

  • 13 Aug 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 13 to 17. That category is still filling its 30-day observation window: 4 days of observed history at the previous scan, 5 at this one. The score rises as the window fills, whether or not the server changes.

  • 11 Aug 26 +2
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 9 Aug 26 −1
    • CVE-2026-69248 affects this package: high security
    • CVE-2026-69247 affects this package: high security
    • CVE-2026-69249 affects this package: high security
    • Malware scan: pass → unverified security
    • Known CVEs: pass → fail security
    • Schema quality: 1575 → 2546 functional
    • Stability: unverified → 0.03 functional
    • First check of Tool coverage: 37 functional
    • First check of Schema quality: 100 functional
    • MCP protocol: Implements a current MCP spec version (2026-07-28). functional
    • Package version: 0.1.0a2 → 1.0.0 functional
    • Package version: 0.1.0a2 → 0.1.0a3 functional
  • 8 Aug 26 59

    First indexed and scored.

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 20 Aug 2026 · Analysed pypi/multisim-mcp@1.0.0

Provenance No attestation

The registry publishes no build provenance for this version, so there is nothing to verify.

Result No attestation
Ecosystem pypi
Install scripts 1 script
Hook Tier Command
build_backend allowlisted setuptools.build_meta
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
Dependencies 33 packages
Packages resolved 33
Stale 1
No linked repository 1
Tree resolution Complete
MCP tools · 51 exposed · ~2,459 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.

Tool Tokens
verify_experiment_requirements ~43

Evaluate explicit design requirements; unsupported evidence stays unverified.

NameTypeReqDescription
experiment_idstringyes
requirementsarrayyes
theoretical_values

Structured output declared, but exposes no named fields.

No examples provided.