Is Myc MCP server safe?
Probably. Read the findings first.
Use with care. Some checks failed or could not be verified.
How Myc compares
Against every graded Databases MCP server, from our own scans and uptime checks. Updated after each scan run.
- Safety score
- 66/100
- higher than 18% of 802 Databases servers
- Tools that change things
- 15%
- typical: 10%. Fewer write tools means less an agent can break
What its tools let an agent do: 11 read · 2 change
Public scan report
scanner v0.1.10 · 2026-10-15 · same rubric, same numbers if you re-run it
3 medium
- Code scan6 source files scanned10/25
- –Live reliabilityno gateway calls yet and no remote to proben/a
- –Tool poisoningtools not inspected (local package is not executed); not countedn/a
- Auth qualitylocal package, no credentials required12/15
- Maintenancelast push 1 days ago15/15
- Maintainer identityregistry namespace matches repository owner6/10
Findings (3)
- mediumnpm install lifecycle script present
install.script - mediumeval / new Function used
exec.evaldist/myc.js: …gs}) => { ${body} };`;ASM_CONSTS[start]=eval(func)}if("__start_em_asm"in moduleExport… - mediumnpm install lifecycle script present
install.scriptpackage.json: …": "bin/myc.js" }, "scripts": { "postinstall": "node bin/preflight.js" }, "engines…
Overall 66/100. Components that don't apply are left out of the denominator. Any critical finding is an F.RubricAppeal a findingJSON
Other servers that do what Myc does
- open-memexLocal-first memory for AI coding agents — Markdown + SQLite FTS5, shared across editors via MCP.not reviewedGrowingB
- GraphmemShared local memory for coding agents: SQLite, semantic recall, linked entities, code navigation.not reviewedGrowingA
SAME - Stateless Agent Memory EnginePersistent memory for AI coding agents. Local-first SQLite + vector search. 17 MCP tools.not reviewedGrowingB
