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

Back to MCP Trust IndexM8ven
C
Emerging
74/100
9 days ago

ltspice-mcp

MCP server for automating LTspice on macOS, enabling simulation, schematic generation, data extraction, verification, and rendering via natural language or agents.

→ xuio/ltspice-mcp· listed on glama

Emerging. No concerning findings. Grades remain capped until the project builds reputation through adoption. 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

xuio

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

Glama

M8ven verifies MCPs across every public registry — install directly from whichever one you prefer.

// key findings
✅
No credential exfiltration, no sensitive file access, no obfuscation
Static analysis found nothing flowing your secrets to unexpected places.
// 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_TOOL_LOG_MAX_ITEMS
configLTSPICE_MCP_TOOL_LOG_MAX_CHARS
configLTSPICE_MCP_LOG_LEVEL
configLTSPICE_MCP_WORKDIR
configLTSPICE_MCP_TIMEOUT
configLTSPICE_BINARY
configLTSPICE_MCP_SYNC_TIMEOUT_MARGIN_SECONDS
configLTSPICE_MCP_SCHEMATIC_LIVE_PATH
configLTSPICE_MCP_TELEMETRY_WINDOW
configLTSPICE_MCP_JOB_HISTORY_RETENTION
configLTSPICE_MCP_DISABLE_UVICORN_NOISE_FILTERS
configLTSPICE_MCP_DAEMON_LOG_DIR
configLTSPICE_MCP_TRANSPORT
configLTSPICE_MCP_HOST
configLTSPICE_MCP_PORT
configLTSPICE_MCP_MOUNT_PATH
configLTSPICE_MCP_SSE_PATH
configLTSPICE_MCP_MESSAGE_PATH
configLTSPICE_MCP_STREAMABLE_HTTP_PATH
configLTSPICE_MCP_CAPTURE_HISTORY_LIMIT
configLTSPICE_MCP_SCK_HELPER_PATH
configLTSPICE_MCP_SCK_HELPER_DIR
configLTSPICE_MCP_AX_CLOSE_HELPER_PATH
configLTSPICE_MCP_AX_CLOSE_HELPER_DIR
configLTSPICE_MCP_AX_TEXT_HELPER_PATH
configLTSPICE_MCP_AX_TEXT_HELPER_DIR
configLTSPICE_MCP_OPEN_LAUNCH_HIDDEN
configLTSPICE_MCP_AX_CLOSE_HELPER_ENABLED
configLTSPICE_MCP_VERIFY_WINDOW_CLOSE
// quality suggestions

Tool annotations

No tools have read-only/destructive annotations

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

All four hints declared on every tool

71/71 tools missing one or more hints — readAgentGuide (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint); parseMeasResults (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint); runMeasAutomation (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint), +68 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.

License file

No license file

Add a LICENSE file (MIT, Apache-2.0, etc.).

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 3 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 Score](https://m8ven.ai/badge/mcp/xuio/ltspice-mcp)](https://m8ven.ai/mcp/xuio/ltspice-mcp)
Shows your grade and updates automatically. Prefer no grade? Append ?variant=verified to the badge URL.
commit: 91c72fb618ae628de669113f15f656b799ef21e2
code hash: 64c07e72a32d3901fc7a481d0f25f1043cf718ea2402f9e69d591e3beff099cd
verified: 9/1/2026, 6:22:37 PM
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