ltspice-mcp (ossenna-hq/MCP_LTSpice) is an MCP server listed on the M8ven Trust Index. It scores 74 out of 100, grade C. It declares 36 tools. No publisher has claimed this listing.

Back to MCP Trust IndexM8ven
C
Warning
74/100

ltspice-mcp

An MCP server that connects LLM assistants to LTspice/ngspice circuit simulation, enabling design, verification, and iteration on schematics and netlists with structured numeric results.

→ ossenna-hq/MCP_LTSpice· listed on glama

Warning. Serious findings were identified. Review the full report before connecting. Grades reflect the full trust pyramid: code, verification depth, and reputation. New projects cap at C until adoption is earned.

How we verified

Code Verified⚡ Live Monitored: not connected

Verified is a snapshot. Live keeps it current, and builds your track record.

⚡ Connect GitHub → continuous verification on every pushwhy connect →

Who stands behind it

ossenna-hq

Source: Glama

Is this your MCP?

Claim it to get a verified publisher badge, a free copy of our full audit findings, and direct contact for any high-priority issues we find. Or connect your repo for our deepest verification, Live Monitored: read-only, revoke anytime. What we access →

⚡ Connect GitHub for Live Monitored

Install from

Glamanot scored here

The grade above is for the source repository. Registries can serve a different version, so we mark the ones we were not able to read.

// key findings
🚨
Code appears obfuscated
1 file are unreadable to a human reviewer. Cannot audit what they do.
// environment variables
To run this server yourself, you supply these values. They go in your own MCP client configuration and stay on your machine. The secret label means the value is sensitive, not that the server mishandles it.
configLTSPICE_MCP_SERVER_NAME
configLTSPICE_MCP_CONFIG
configLTSPICE_MCP_SIMULATOR
configLTSPICE_MCP_ENABLED_SIMULATORS
configLTSPICE_MCP_SIMULATOR_EXE
configLTSPICE_MCP_NGBEHAVIOR
configLTSPICE_MCP_WORKING_DIR
configLTSPICE_MCP_ALLOWED_PATHS
configLTSPICE_MCP_LOG_LEVEL
configLTSPICE_MCP_SYMBOL_PATHS.asy symbol paths for .asc editing are auto-detected on Windows and WSL; override with [schematic] symbol_paths or .
configLTSPICE_MCP_TOOL_PROFILE
configLTSPICE_MCP_PERSIST_JOBS
configLTSPICE_MCP_PRELOAD_RECENT_COUNT
configSPICE_LIB_DIR
configLTSPICE_MCP_HOME
configXDG_STATE_HOME
configLTSPICE_MCP_DISABLE_SIMULATOR_DETECTION
configWSL_DISTRO_NAME
// quality suggestions

Tool annotations

17/36 tools have annotations

Add readOnlyHint or destructiveHint annotations to every tool so hosts can warn users before invoking.

All four hints declared on every tool

19/36 tools missing one or more hints — operating_point (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint); simulation_summary (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint); edge_metrics (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint), +16 more. OpenAI's directory rejects tools where any of the four hints are missing or non-boolean.

For every tool, set all four hints (readOnlyHint, destructiveHint, idempotentHint, openWorldHint) to explicit true/false values that match the handler’s actual behaviour.

No eval / new Function

1 eval() or new Function() call — dynamic code execution

Replace eval / Function with explicit parsing or safer alternatives.

Readable source code

1 file are minified or bundled, which is usually build output rather than concealment

Ship unminified, readable source.

Claim the listing to review these findings one by one and send us a correction where you disagree, straight to the team. Claiming also means we tell you when the grade moves, and reach you first if we find anything urgent.

// full audit trail
The findings above are the summary. The full trail, every check we ran, each deduction, the network hosts observed and the dependency advisories, goes to verified publishers, along with an alert whenever a new one lands. Verified publishers can also review each finding and dispute it in one click. Publisher corrections have sharpened several of our checks this month, because the maintainer knows the codebase better than any scanner.
// improvement guidance — verified publishers only
We have 4 concrete improvements we can share with the publisher of this MCP. Each comes with specific guidance to raise the trust score.
// embed badge in your README
[![M8ven Verified](https://m8ven.ai/badge/mcp/ossenna-hq/mcp_ltspice?variant=verified)](https://m8ven.ai/mcp/ossenna-hq/mcp_ltspice)
Shows verification status without the grade. Want the grade badge instead? Remove ?variant=verified from the URL.
commit: 540b10e425eb4778478404d324bfc93cd3706446
code hash: c2ef8b447c08004640a26067635d0dae053ce95de784a551b18a42d1f6a43997
view raw JSON →
Check MCPs from inside your assistant
Tool Check · MCP

Vetting this one by hand? Tool Check is an MCP that scores other MCPs. Add it once and ask Claude, ChatGPT, or any MCP client to grade a server, surface CVEs, check the publisher, and suggest safer alternatives — before you install.

https://m8ven.ai/api/mcp/tool-check
check_toolsearch_toolscompare_toolsrecommend_alternativescheck_publisherreport_concern
How to add it →Free · no account needed · works in any MCP client