mind-meld (redaphid/mind-meld) is an MCP server listed on the M8ven Trust Index. It scores 73 out of 100, grade C. It declares 13 tools. No publisher has claimed this listing.

Warning. Serious findings were identified. Review the full report before connecting. 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

redaphid

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 →

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
🚨
Secret credentials may flow to a network call
3 flows detected: INGEST_SPOOL_CLIENT_SECRET. We can’t prove the destination matches the brand the credential belongs to.
🚨
Code appears obfuscated
1 file are unreadable to a human reviewer. Cannot audit what they do.
🚨
Known vulnerabilities in dependencies: 1 critical
Affects packages this MCP installs at runtime. Upgrade or remove the affected dependency.
🔐
You'll be asked for 2 credentials: INGEST_SPOOL_CLIENT_SECRET, POSTGRES_PASSWORD
These are read from process.env at runtime. Make sure you trust where they’ll be sent.
// tools this server exposes13 tools

These names and descriptions are the publisher's own, read from the source code. We print them as written. Our assessment is the findings above, not this list.

search

Search past AI conversations. Returns TERSE ranked hits — one line each, no full summaries — so you can triage cheaply, then drill in. Each hit carries: - session_id, title, date, score - matched_tier: which rung matched (session | chunk | message) - snippet: the query-highlighted lead of the match

getSession

Get a session's DIGEST — summary + chunk map. NO raw messages. BREAKING CHANGE: getSession no longer dumps messages. It returns the middle rung of disclosure: the session summary plus a manifest of its chunks, each with a one-line summary and a { start_message_id, end_message_id } range. Read the r

getSessionTranscript

Resolve a session by external ID or title and return its DIGEST. Despite the name, this aliases getSession (digest, not raw transcript) — it just resolves the session differently: exact external_id match first, then ILIKE title search. Use getMessages to read raw messages once you have the session.

getMessages

Read RAW messages, windowed. Two modes: - Browse a window: { sessionId, offset?, limit? } — default limit 30 (never the whole thread). Page with offset. - Read a chunk's region: { startMessageId, endMessageId } — the id range straight off a getSession chunk-manifest entry. sessionId is inferred

getMessage

Read ONE message in full by id, uncapped. The escape hatch for an oversized message that getMessages returned TRUNCATED — reaching its full content requires this deliberate call, so a huge payload can never arrive by accident.

getChunk

Get one chunk's full summary by { sessionId, chunkIndex } — the middle step between a getSession manifest line and reading raw messages, when the one-line manifest summary isn't enough to decide. Includes the message-id range to hand to getMessages.

stats

Get statistics about your conversation history

health

Report mindmeld's own indexing health so silent degradation is visible. Surfaces three areas; "unhealthy" cues are documented inline in the output: SUMMARY COVERAGE - total sessions; sessions with a non-NULL summary (excluding deleted + 'Warmup') - coverage % = summarized / (summarized + real NULL

reportUselessSession

Flag a session that pollutes search results. REVERSIBLE — nothing is deleted. Use this when search returns results that are clearly noise — automated runs, monitoring jobs, notification stubs, sentinel results, tool-call spam, repeated boilerplate, or anything that isn't a real conversation. WHAT

unreportUselessSession

Undo reportUselessSession. Removes the "useless" tag AND takes the session back out of the noise corpus, so it stops dragging similar sessions down. Agents over-flag — that is expected, and it is why this exists. If a session was reported as noise and it turns out to be real, undo it here; there is

addTag
removeTag

Remove tags from a session or a message — the inverse of addTag, and the reason tagging is safe to do freely: nothing about it is permanent. Removing "useless" from a session returns it to normal search results. Pass exactly one of sessionId / messageId. Removing a tag that was not there is report

writeNote
// known CVEs in dependencies1 critical

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

criticalvitest@2.1.9GHSA-5xrq-8626-4rwp

When Vitest UI server is listening, arbitrary file can be read and executed

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.
configALLOWED_HOSTS
configINGEST_SPOOL_CLIENT_ID
🔐 secretINGEST_SPOOL_CLIENT_SECRET
configINGEST_SPOOL_URL
configMCP_PORT
configMINDMELD_DEFAULT_EXCLUDED_TAGS
configPOSTGRES_DBMust match across every machine feeding one index
configPOSTGRES_HOSTNon-standard port to avoid clashing with a local Postgres
🔐 secretPOSTGRES_PASSWORDMust match across every machine feeding one index
configPOSTGRES_PORTNon-standard port to avoid clashing with a local Postgres
configPOSTGRES_USERMust match across every machine feeding one index
configUI_PORT
configUPSTREAM_URL
configWSL_DISTRO_NAME
// 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

13/13 tools missing one or more hints — search (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint); getSession (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint); getSessionTranscript (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint), +10 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.

License file

No license file

Add a LICENSE file (MIT, Apache-2.0, etc.).

Readable source code

1 file are minified or bundled, which is usually build output rather than concealment

Ship unminified, readable source.

Secrets stay with their owner

3 secrets sent to a request target we could not resolve (INGEST_SPOOL_CLIENT_SECRET → dynamic, INGEST_SPOOL_CLIENT_SECRET → dynamic) — often a configured endpoint, not necessarily third-party

Audit where credentials are sent. A NOTION_TOKEN should only reach api.notion.com — never a third-party host.

No arbitrary install scripts

Has postinstall/preinstall script — runs arbitrary code on npm install

Remove postinstall/preinstall hooks unless they’re essential.

Dev dependencies

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

Upgrade dev dependencies when convenient.

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/redaphid/mind-meld?variant=verified)](https://m8ven.ai/mcp/redaphid/mind-meld)
Shows verification status without the grade. Want the grade badge instead? Remove ?variant=verified from the URL.
commit: 409875275a61163880a5c41adc29c633972d193c
code hash: d224b066e3f349beaf9279dd5458dab444aaa8508e5dac805f79e6da065d5bed
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