Memory Bank MCP (spideynolove/memory) is an MCP server listed on the M8ven Trust Index. It scores 54 out of 100, grade D. It declares 27 tools. No publisher has claimed this listing.

D
Caution
54/100

Memory Bank MCP

An MCP server that enables persistent memory, structured thinking sessions, and project-based knowledge management for Claude. It includes specialized coding tools for package discovery and reinvention prevention by validating code against existing libraries and APIs.

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

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

spideynolove

Source: Glama

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
No credential exfiltration, no sensitive file access, no obfuscation
Static analysis found nothing flowing your secrets to unexpected places.
// tools this server exposes27 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.

create_memory_session
store_memory
revise_memory
create_collection
merge_collection
analyze_memories
export_session_to_file
export_memories_to_file
create_project_structure
load_project_context
update_project_index
discover_packages
validate_package_usage
explore_existing_apis
store_codebase_pattern
load_codebase_context
prevent_reinvention_check
extract_tool_errors
get_tool_errors
resolve_tool_error
get_frequent_errors
get_attention_state
boost_memory_attention
reset_attention_state
analyze_corrections
get_rule_violations
resolve_rule_violation
// 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

27/27 tools missing one or more hints — create_memory_session (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint); store_memory (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint); revise_memory (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint), +24 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

1 tool perform destructive updates without destructiveHint — reset_attention_state deletes at line 1569 (state_file.unlink())

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.

Tool inputs are validated

23/27 tool handlers declare input schemas (85%)

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

Tool handlers catch errors

21/27 tool handlers wrap calls in try/catch (78%)

Wrap each tool handler body in try/catch and return a structured error response.

README present

No README found

Add a README.md describing the server and its tools.

Tests exist

No test files found

Add tests that exercise each declared tool.

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/spideynolove/memory?variant=verified)](https://m8ven.ai/mcp/spideynolove/memory)
Shows verification status without the grade. Want the grade badge instead? Remove ?variant=verified from the URL.
commit: 17151223446b566849c53ac251d9bafd4f535614
code hash: c15439a9f83efbba5985e965f99cc2fb0cd76d34164deb3589d0c378642da1d8
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