clemmy (Natebreynolds/clemmy) is an MCP server listed on the M8ven Trust Index. It scores 54 out of 100, grade D. It declares 199 tools. No publisher has claimed this listing.

D
Caution
54/100

clemmy

Local-first AI operator with persistent memory, governed tools, workflows, voice, and meetings.

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

⚡ 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

Natebreynolds

Source: github_repo_search

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

The grade above is for the source repository. Registries can serve a different version, so we mark the ones we were not able to read.

// key findings
⚠️
Tool descriptions don’t match what handlers do
2 tools describe read intent but their handlers mutate — desktop_status (line 39: spawnSync('/usr/libexec/PlistBuddy', ['-c', `Print :${key}`, plistPath], {); working_memory (line 622: unlinkSync(WORKING_MEMORY_FILE))
⚠️
Known vulnerabilities in dependencies: 2 high
Affects packages this MCP installs at runtime. Upgrade or remove the affected dependency.
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.
// known CVEs in dependencies2 high3 low

Disclosed vulnerabilities in this server's declared npm dependencies (via OSV). Whether each is reachable depends on the installed versions.

highjs-yaml@3.15.0GHSA-2883-xcg3-v3hh

js-yaml: maxTotalMergeKeys does not limit CPU use for empty merge sources

highjs-yaml@3.15.0GHSA-5p4m-2wfm-xmqj

JS-YAML: Quadratic CPU consumption in !!omap resolution (3.x and 4.x) — CVE-2026-59870 fix not backported

lowundici@6.27.0GHSA-8xcm-r25x-g524

undici vulnerable to downstream response desynchronization via retry interceptor

lowundici@6.27.0GHSA-m8rv-5g2x-5cg5

undici vulnerable to CRLF Injection via blob-like body 'type' property

lowundici@6.27.0GHSA-v3r7-h72x-cjcm

undici vulnerable to cookie attribute injection via unsanitized domain and unparsed setCookie fields

Depend on this server? Get alerted when its CVEs change.Watch this server free →
// 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.
configCLEMENTINE_HOMEStored under CLEMENTINE_HOME, which defaults to ~/.clementine-next/.
configCLEMMY_MCP_ERROR_CORRECTIVE
configCLEMMY_MCP_SCOPE_FAILOPEN
configCLEMMY_MCP_SCOPE_FAILOPEN_MAX
configCLEMMY_MCP_SEMANTIC_RANK
configCLEMMY_PROCEDURAL_OUTCOMES
configCLEMMY_SCOPED_MCP_TOOLS
configCLEMMY_SCOPE_FROM_RECALL
configCLEMMY_TOOL_CHOICE_DECAY
configMCP_ATTACH_CONNECTED_ONLY
configMCP_EAGER_CONNECT_BLOCKING
configTOOL_CHOICE_CONTEXT_INJECT
// 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

199/199 tools missing one or more hints — mcp_reconnect (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint); mcp_add (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint); mcp_configure (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint), +196 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

4 tools perform destructive updates without destructiveHint — produce_document deletes at line 145 (rmSync(htmlPath, { force: true })); working_memory deletes at line 622 (unlinkSync(WORKING_MEMORY_FILE)); space_revert_runner deletes at line 1618 (unlinkSync(path.join(histDir, latest)))

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.

Descriptions match behaviour

2 tools describe read intent but their handlers mutate — desktop_status (line 39: spawnSync('/usr/libexec/PlistBuddy', ['-c', `Print :${key}`, plistPath], {); working_memory (line 622: unlinkSync(WORKING_MEMORY_FILE))

Rename the tool, rewrite the description, or move the side-effect into a separate clearly-named tool.

Tool inputs are validated

176/185 tool handlers declare input schemas (95%)

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

Shell command execution

1 call in production code run through a shell (src/index.ts:272)

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

Dev dependencies

2 critical/high in dev-only deps (does not ship to users)

Upgrade dev dependencies when convenient.

Dependency freshness

2/24 production deps stale: gray-matter@2023-07-12 (3.2y), web-push@2024-01-16 (2.7y)

Tool description accuracy

desktop_status: description implies read-only but handler writes/deletes/executes; working_memory: description implies read-only but handler writes/deletes/executes

Update tool descriptions to accurately reflect all capabilities — especially write, delete, or execute operations.

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 8 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/natebreynolds/clemmy?variant=verified)](https://m8ven.ai/mcp/natebreynolds/clemmy)
Shows verification status without the grade. Want the grade badge instead? Remove ?variant=verified from the URL.
commit: 7c757e29c6e1e75a12bb1647ec90568708627cd9
code hash: af4878480526fe40c218bbcb38527878717ce3a9e3a0fc9e5f51d62a13f8ea5a
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