zaptrace-mcp (oaslananka/zaptrace) 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
8 days ago

zaptrace-mcp

Enables AI agents to perform electronics design automation through the ZapTrace EDA kernel, including parsing designs, running ERC, placing components, routing nets, and generating manufacturing outputs (Gerber, BOM, etc.).

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

oaslananka

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.
Open source with a license and README
Anyone can audit the code, the license is declared, and the publisher documents what it does.
🔐
You'll be asked for 3 credentials: ZAPTRACE_MCP_HTTP_TOKEN, ZAPTRACE_API_TOKEN, SONAR_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.
configZAPTRACE_WORKSPACE
configZAPTRACE_MCP_CAPABILITIES
🔐 secretZAPTRACE_MCP_HTTP_TOKEN
configZAPTRACE_MCP_TOKEN_SUBJECT
🔐 secretZAPTRACE_API_TOKEN
configZAPTRACE_API_TOKEN_AUDIENCE
configZAPTRACE_API_TOKEN_SUBJECT
configZAPTRACE_API_TOKEN_SCOPES
configZAPTRACE_API_TOKEN_SESSIONS
configZAPTRACE_CORS_ORIGINS
configGITHUB_REF
configCARGO_BUILD_TARGET
🔐 secretSONAR_TOKEN
configGITHUB_SHA
configFREEROUTING_JAR
configZAPTRACE_API_ARTIFACT_ROOT
configZAPTRACE_API_ARTIFACT_RETENTION_SECONDS
configZAPTRACE_PERSISTENCE_DISABLED
configZAPTRACE_API_MAX_ARTIFACT_BYTES
configZAPTRACE_SESSION_STORE_ROOTexport ="$HOME/.local/share/zaptrace/state"
// 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

3/3 tools missing one or more hints — session_create (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint); session_destroy (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint); session_list (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint). 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.

Secrets not written to files

2 secret values written to files

Avoid persisting secrets to disk. Keep them in memory or your secret manager.

Secrets not logged

1 secret value sent to console.log

Redact or omit secret values from log output.

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/oaslananka-zaptrace-vg5y6q)](https://m8ven.ai/mcp/oaslananka-zaptrace-vg5y6q)
Shows your grade and updates automatically. Prefer no grade? Append ?variant=verified to the badge URL.
commit: ff6202872cddf1efea7d616e46e8d7bab136f7fc
code hash: 58a0463d13c6ac9788df0af104574a042655b8b0640ca75b2c23ea86e91b7188
verified: 8/21/2026, 9:03:56 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