leveret (leveret-dev/leveret) is an MCP server listed on the M8ven Trust Index. It scores 74 out of 100, grade C. It declares 6 tools. The publisher has confirmed an email address for this listing, which proves an inbox rather than ownership (Claimed).

C
Emerging
74/100
9 days ago

leveret

Self-hosted MCP engine for private code reviews, providing deterministic static analysis and AST-level search over diffs, with findings passed to a review agent of your choice.

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 VerifiedSandbox 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

leveret-dev · Claimed

Source: Glama

⚡ Upgrade to Live Monitored

Connect your repo and M8ven re-verifies it on the push itself. Without it we re-check verified listings about once a day, so a fix can sit unseen. Read-only, one click, 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.
// 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.
configLEVERET_BASE
configLEVERET_CACHE
configLEVERET_CACHE_RUN
configLEVERET_CHANGE_MANIFEST
configLEVERET_CODEGRAPH_BIN
configLEVERET_DATA. Raw content never enters default stdout. See
configLEVERET_DISCOVERY_CONCURRENCY
configLEVERET_DISCOVERY_MODE
configLEVERET_DISCOVERY_SCHEDULER
configLEVERET_EVIDENCE_PACK
configLEVERET_EVIDENCE_PACK_SHA256
configLEVERET_GRAPH
configLEVERET_GRAPHIFY_BIN
configLEVERET_GRAPHIFY_EDGES
configLEVERET_GRAPHIFY_GRAPH
configLEVERET_GRAPHIFY_NODES
configLEVERET_GUIDANCE
configLEVERET_GUIDANCE_SHA256
configLEVERET_MODEL_ROUTING
configLEVERET_MODEL_ROUTING_SHA256
configLEVERET_PI_AGENT_DIR
configLEVERET_PRIOR
configLEVERET_PUBLIC_URL
configLEVERET_RELAY_BOT_LOGIN
configLEVERET_REPO
configLEVERET_REQUIRE_INDEXES0 only for an explicitly degraded run.
configLEVERET_RUNNERmetrics. A custom remains the bring-your-own-harness escape hatch.
configLEVERET_RUNNER_EFFORT
configLEVERET_RUNNER_MODEL
configLEVERET_RUNNER_PROVIDER
configLEVERET_RUNNER_TIMEOUT_MS
configLEVERET_SANDBOXED
configLEVERET_SANITIZE_CHILD_ENV
configLEVERET_SERENA_BIN
configLEVERET_SERENA_BUNDLEwith set to that path (the installed package also exposes
configLEVERET_TRUSTED_MEMORY
configLEVERET_TRUSTED_MEMORY_SHA256
configLEVERET_WORK_ITEM
configPI_OFFLINE
configPI_SKIP_VERSION_CHECK
configPI_TELEMETRY
Deployment configuration, supplied by whoever hosts the server. Users are not asked for these.
deployPORT
// 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

6/6 tools missing one or more hints — scan (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint); ast_search (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint); context (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint), +3 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.

Shell command execution

10 calls in production code run through a shell (bench/replay.mts:202, src/audit.ts:377, src/audit.ts:436)

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 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/leveret-dev/leveret)](https://m8ven.ai/mcp/leveret-dev/leveret)
Shows your grade and updates automatically. Prefer no grade? Append ?variant=verified to the badge URL.
commit: aa0c764ca7a7b29a3c9ad23b0de23febbe4c5216
code hash: 436b1f4a113849ff44299f9a308236437094887f479e89e41729bc9b80560756
verified: 9/1/2026, 8:47:42 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