Silvaco Handbook MCP (zd0818/Silvaco_MCP) is an MCP server listed on the M8ven Trust Index. M8ven has not graded it: we have no way to read this server ourselves. No publisher has claimed this listing.

C
Emerging
74/100
16 days ago

Silvaco Handbook MCP

Provides AI assistants fast, bounded access to Silvaco TCAD manuals and official Deckbuild example decks via search/read tools, with full-text indexing and PDF page references.

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

zd0818

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 →

Install from

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.
🔐
You'll be asked for 1 credential: MINERU_TOKEN
These are read from process.env at runtime. Make sure you trust where they’ll be sent.
// 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.
configSILVACO_MD_DIRexport =/path/to/markdown/output
configSILVACO_CACHE_DBrepo>/.cache/handbooks_md.db SQLite FTS5 cache location
configSILVACO_EXAMPLES_DIR"": "C:/Silvaco/examples/deckbuild/5.2.40.R"
configSILVACO_PDF_DIRexport =/path/to/silvaco/handbook/pdfs
configSILVACO_MCP_CONFIG(vault layout default) mcp.json to read MINERU_TOKEN from (optional)
configMINERU_CLImineru-open-api Path/name of the MinerU CLI executable
🔐 secretMINERU_TOKENexport =<your-mineru-token>
// 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

7/7 tools missing one or more hints — handbook_list_manuals (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint); handbook_toc (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint); handbook_search (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint), +4 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.).

Tests exist

No test files found

Add tests that exercise each declared tool.

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 Score](https://m8ven.ai/badge/mcp/zd0818-silvaco-mcp-1ixj1s)](https://m8ven.ai/mcp/zd0818-silvaco-mcp-1ixj1s)
Shows your grade and updates automatically. Prefer no grade? Append ?variant=verified to the badge URL.
commit: 627c0d6df082c1e9b21e871ec7d3d329ab7678a1
code hash: eb605025c5020a63413b338c2037a098ec0cf326450ff3f67b284b6084222df5
verified: 8/14/2026, 9:58:41 AM
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