Back to MCP Trust Indexm8ven
D
Caution
52/100
14 days ago

lmstudio-agent-mcp

Local LM Studio agent stack: MCP tools, OpenClaw bridge, GitHub integration, one-script macOS bootstrap

→ priyansh19/lmstudio-agent-mcp· listed on github_code

Caution. Specific findings reduced this grade. They are listed on the page. 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

priyansh19

Source: github_code

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

GitHub

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 4 credentials: GITHUB_PERSONAL_ACCESS_TOKEN, GITHUB_TOKEN, ANTHROPIC_API_KEY, OPENAI_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.
configWORKSPACE_ROOTS
🔐 secretGITHUB_PERSONAL_ACCESS_TOKEN
🔐 secretGITHUB_TOKEN
configLMSTUDIO_URL
configEMBEDDING_MODEL
configTRIAGE_ENABLED
configBRIDGE_PORT
configMEMORY_FILE_PATH
configPROCEDURAL_ENABLED
configSKILLS_DIR
configTRIAGE_THRESHOLD
configVECTOR_MEMORY_DB
configRAG_ENABLED
configSUMMARIZER_ENABLED
configSANDBOX_ROOT
configTHINK_PROVIDER
configTHINK_DEEP_MODEL
configTHINK_MODEL
configCLAUDE_CLI
configTHINK_USE_SUBSCRIPTION
configCLAUDE_CLI_TIMEOUT
configCLAUDE_CLI_CWD
configCLAUDE_CLI_OUTPUT
configTHINK_EFFORT
configTHINK_DEEP_EFFORT
🔐 secretANTHROPIC_API_KEY
🔐 secretOPENAI_API_KEY
configOPENAI_BASE_URL
configOPENAI_MODEL
// 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

58/58 tools missing one or more hints — list_allowed_roots (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint); list_directory (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint); read_file (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint), +55 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.

Destructive tools are labelled

1 tool perform destructive updates without destructiveHint — delete_path deletes at line 204 (target.unlink())

Add destructiveHint:true to any tool whose handler calls .delete(), .upsert(), .update(), unlink, rm, DELETE, DROP, REPLACE INTO, or any operation that overwrites existing data.

Tool inputs are validated

48/58 tool handlers declare input schemas (83%)

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

Tool handlers catch errors

Only 8/58 tool handlers wrap calls in try/catch (14%)

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

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 7 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/priyansh19-lmstudio-agent-mcp-1hw7um?variant=verified)](https://m8ven.ai/mcp/priyansh19-lmstudio-agent-mcp-1hw7um)
Shows verification status without the grade. Want the grade badge instead? Remove ?variant=verified from the URL.
commit: 1c17f66f34783cf52e73ba0c95d136a4c96a9da3
code hash: cc339162315548853e9100c830ab606dedaa14f4335c75be9e4d51b56addb215
verified: 8/8/2026, 8:22:54 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