A persistent memory MCP server specialized for Japanese, featuring hybrid search, Ebbinghaus forgetting curve, entity knowledge graphs, and a web dashboard for memory visualization.
Limited view. Automated analysis covers part of this stack. Findings reflect what we verified. Grades reflect the full trust pyramid: code, verification depth, and reputation. New projects cap at C until adoption is earned.
Limited view: static analysis for Python is partially covered.
How we verified
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
solidlime
Source: Glama
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
M8ven verifies MCPs across every public registry — install directly from whichever one you prefer.
MEMORY_INJECT_ONMEMORY_MCP_API_KEYMEMORY_MCP_PERSONAMEMORY_MCP_URLNOUS_DATA_ROOTNOUS_TOOL_DESCRIPTION_OVERRIDEPERSONAPersona の指定方法: 優先順位は Bearer トークン > X-Persona ヘッダー > 環境変数 > デフォルト "default"。NOUS_DEFAULT_PERSONADependencies
1 dependencies, 1 flagged: playwright
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
12/12 tools missing one or more hints — get_context (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint); memory_create (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint); memory_read (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint), +9 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.
Tool inputs are validated
11/12 tool handlers declare input schemas (92%)
Declare an inputSchema with zod/joi/yup on every tool definition.
Tool handlers catch errors
Only 0/12 tool handlers wrap calls in try/catch (0%)
Wrap each tool handler body in try/catch and return a structured error response.
License file
No license file
Add a LICENSE file (MIT, Apache-2.0, etc.).
Tool test coverage
Only 0/12 tools referenced in tests (0%)
Write tests that reference each tool by name so every tool has at least one test.
No eval / new Function
5 eval() or new Function() calls — dynamic code execution
Replace eval / Function with explicit parsing or safer alternatives.
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.
[](https://m8ven.ai/mcp/solidlime-nous-13p7nb)?variant=verified to the badge URL.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