@nawwal/mymind
npm
v1.0.4
Source verified
Published by nawwwal — publish provenance cryptographically ties this package to that repository. That is proof of origin, not an official vendor package.
Unofficial CLI and MCP bridge for the mymind API (agents-first).
The grade answers one question — how safe is this server for you to adopt — so it is computed in two auditable stages. Nothing below is an opinion or an LLM's guess; every line is a real term the deterministic engine applied, and the same input always yields the same number.
1. Threat score — 100 − 0 = 100. What the published surface and source actually contain:
The deterministic scan raised no scored threat in the surface it inspected — the threat score stayed at 100. Capability observations and advisory notes are recorded but never lower it.
2. Client adoption risk — 100 − 6 = 94. Three small, subtract-only factors that reflect your risk in adopting it — a clean scan proves less on a powerful, unverified or barely-inspectable package, so the grade says so plainly:
| Points | Adoption-risk factor |
|---|---|
| −6 | capability blast radius (high) — client exposure if the model is manipulated |
Capability observations and info notes are shown under Findings but never scored.
Open any row's finding below for the file, line and evidence behind a deduction.
In the server's implementation (`dist/cli.js:123`): Spawning a shell/process is command-execution capability; with unsanitized tool input it is command injection / RCE. This is read from the code itself — not from the tool description — so a poisoned server cannot hide it behind honest-looking metadata.
Evidence: ort { spawnSync } from "child_process"; var KEYCHAIN_SERVICE = "com.nawwal.mymind"; var KEYCHAIN_ACCOUNT = "credentials"
Fix: Review this call path: confirm it never receives unsanitized tool input, constrain it, or remove it. Treat a server whose code reaches these sinks as high-capability regardless of what its tools claim.
Location: server dist/cli.js
In the server's implementation (`dist/index.js:67`): Spawning a shell/process is command-execution capability; with unsanitized tool input it is command injection / RCE. This is read from the code itself — not from the tool description — so a poisoned server cannot hide it behind honest-looking metadata.
Evidence: ort { spawnSync } from "child_process"; var KEYCHAIN_SERVICE = "com.nawwal.mymind"; var KEYCHAIN_ACCOUNT = "credentials"
Fix: Review this call path: confirm it never receives unsanitized tool input, constrain it, or remove it. Treat a server whose code reaches these sinks as high-capability regardless of what its tools claim.
Location: server dist/index.js
In the server's implementation (`dist/mcp.js:37`): Spawning a shell/process is command-execution capability; with unsanitized tool input it is command injection / RCE. This is read from the code itself — not from the tool description — so a poisoned server cannot hide it behind honest-looking metadata.
Evidence: ort { spawnSync } from "child_process"; var KEYCHAIN_SERVICE = "com.nawwal.mymind"; var KEYCHAIN_ACCOUNT = "credentials"
Fix: Review this call path: confirm it never receives unsanitized tool input, constrain it, or remove it. Treat a server whose code reaches these sinks as high-capability regardless of what its tools claim.
Location: server dist/mcp.js
Each tool and what it can reach — statically extracted from the published source.
mymind_download_objectingests untrusted inputmymind_list_objectsingests untrusted inputmymind_add_object_spacesno sensitive capabilitymymind_add_object_tagsno sensitive capabilitymymind_add_object_to_spaceno sensitive capabilitymymind_convert_contentno sensitive capabilitymymind_create_objectno sensitive capabilitymymind_create_spaceno sensitive capabilitymymind_delete_objectno sensitive capabilitymymind_delete_spaceno sensitive capabilitymymind_find_related_objectsno sensitive capabilitymymind_get_objectno sensitive capabilitymymind_get_object_contentno sensitive capabilitymymind_get_spaceno sensitive capabilitymymind_list_spacesno sensitive capabilitymymind_list_tagsno sensitive capabilitymymind_pin_objectno sensitive capabilitymymind_remove_object_from_spaceno sensitive capabilitymymind_replace_note_contentno sensitive capabilitymymind_restore_objectno sensitive capabilitymymind_search_objectsno sensitive capabilitymymind_unpin_objectno sensitive capabilitymymind_update_objectno sensitive capabilitymymind_update_spaceno sensitive capabilityScan history per published version. The engine is deterministic — the same version always yields the same score, so a changed score means the package itself changed.
| Version | Score | Findings | Engine | Scanned |
|---|---|---|---|---|
v1.0.4 latest |
A 94/100 | 3 | 1.13.0 | 2026-09-07 |
Show this server's live Trust Score in your README, docs or website. The badge is served straight from the registry and updates automatically after every rescan — no API key needed. It links back to this page, so anyone who sees the grade can also read the findings behind it instead of taking a number on faith.
The score above is reproducible: the same package version always yields the same result. Run it locally or over the free API — no account, no LLM, fully deterministic.
npx mcptrustchecker scan @nawwal/mymind --online
Adapters for the FrontMCP framework
Transcend MCP Server — Admin tools.
Transcend MCP Server — Assessments tools.
MCP Server for Bling
MCP Server for Blogger API
Official MCP server for Brilliant Directories — manage members, posts, leads, reviews, and more.