MeshCue Forge (Meshcue/meshcue-forge) is an MCP server listed on the M8ven Trust Index. M8ven has not graded it: there is no public source to read and no endpoint we can reach, so there is nothing for us to inspect. No publisher has claimed this listing.

Back to MCP Trust Indexm8ven
C
Emerging
74/100
2 months ago

MeshCue Forge

An open-source MCP server that turns natural language hardware descriptions into complete, buildable projects including circuits, firmware, 3D-printable enclosures, PCB files, and documentation.

→ Meshcue/meshcue-forge· 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

Meshcue

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.
✅
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 6 credentials: MESHCUE_AT_API_KEY, MESHCUE_MESH_SECRET, MESHCUE_TWILIO_TOKEN, MESHCUE_WA_TOKEN, MESHCUE_WA_VERIFY_TOKEN, ZOO_CAD_API_KEY
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.
configCOSMOS_ENDPOINT
configFORGE_ENABLE_GPU
configFORGE_ENCLOSURE_BACKENDEnclosure openscad cadquery, zoo-cad, llama-mesh OpenSCAD: none (generates .scad). CadQuery: Python 3 + cadquery pip package. Zoo: ZOO_CAD_API_KEY. LLaMA-Mesh: LLAMA_MESH_ENDPOINT.
configFORGE_PCB_BACKENDPCB skidl kicad SKiDL: generates Python script (execution needs Python + skidl). KiCad: KICAD_PATH pointing to kicad-cli.
configFORGE_VIZ_BACKENDVisualization hunyuan3d cosmos, llama-mesh All generate placeholders in offline mode. Online mode requires the respective _ENDPOINT env var.
configHUNYUAN3D_ENDPOINT
configKICAD_PATHPCB FORGE_PCB_BACKEND skidl kicad SKiDL: generates Python script (execution needs Python + skidl). KiCad: pointing to kicad-cli.
configLLAMA_MESH_ENDPOINTEnclosure FORGE_ENCLOSURE_BACKEND openscad cadquery, zoo-cad, llama-mesh OpenSCAD: none (generates .scad). CadQuery: Python 3 + cadquery pip package. Zoo: ZOO_CAD_API_KEY. LLaMA-Mesh: .
🔐 secretMESHCUE_AT_API_KEY
configMESHCUE_AT_SHORTCODE
configMESHCUE_AT_USERNAME
configMESHCUE_CORS_ORIGIN
configMESHCUE_DB_PATH
configMESHCUE_DEFAULT_CHANNELPlatform default delivery channel (sms, whatsapp, voice)
configMESHCUE_DEFAULT_LANGUAGEPlatform default language code (en, fr, sw, rw, ln, rn, pt, ar, es)
configMESHCUE_ESCALATION_PHONEPlatform-level fallback phone number for critical alerts when all clinic contacts fail
configMESHCUE_HEALTH_PORT
configMESHCUE_MAX_RETRIESNumber of delivery retries before escalation
configMESHCUE_MESH_ENDPOINT
🔐 secretMESHCUE_MESH_SECRET
configMESHCUE_TWILIO_PHONE
configMESHCUE_TWILIO_SID
🔐 secretMESHCUE_TWILIO_TOKEN
configMESHCUE_VOICE_PROVIDER
configMESHCUE_WA_PHONE_ID
🔐 secretMESHCUE_WA_TOKEN
🔐 secretMESHCUE_WA_VERIFY_TOKEN
configMESHCUE_WEBHOOK_PORT
configOPENSCAD_PATHOpenSCAD .scad files are generated instantly. Rendering to STL requires OpenSCAD installed locally ().
configPYTHON_PATHSet to your Python 3 interpreter (e.g., PYTHON_PATH=/usr/local/bin/python3).
🔐 secretZOO_CAD_API_KEYEnclosure FORGE_ENCLOSURE_BACKEND openscad cadquery, zoo-cad, llama-mesh OpenSCAD: none (generates .scad). CadQuery: Python 3 + cadquery pip package. Zoo: . LLaMA-Mesh: LLAMA_MESH_ENDPOINT.
configZOO_CAD_ENDPOINTCheck that is set correctly (default: https://api.zoo.dev).
// 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

28/28 tools missing one or more hints — meshcue-clinic-register (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint); meshcue-clinic-setup-sms (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint); meshcue-clinic-setup-whatsapp (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint), +25 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.

Tool inputs are validated

23/28 tool handlers declare input schemas (82%)

Declare an inputSchema with zod/joi/yup on every tool definition.

Tool handlers catch errors

27/28 tool handlers wrap calls in try/catch (96%)

Wrap each tool handler body in try/catch and return a structured error response.

Tool test coverage

Only 4/28 tools referenced in tests (14%)

Write tests that reference each tool by name so every tool has at least one test.

Shell command execution

2 child_process calls — runs shell commands

Prefer library functions over shell-outs. If you must shell out, ensure all inputs are properly escaped.

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 6 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/meshcue-meshcue-forge-u23jnw)](https://m8ven.ai/mcp/meshcue-meshcue-forge-u23jnw)
Shows your grade and updates automatically. Prefer no grade? Append ?variant=verified to the badge URL.
commit: 98c40731c7608e43bc1ad0f0aa84131b6030b6ac
code hash: d67109928004a36668ea196cf94eec9b78cad21fd8e043b5c9a716a604988fcc
verified: 6/22/2026, 12:26:39 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