Memento (veerps57/memento) is an MCP server listed on the M8ven Trust Index. It scores 62 out of 100, grade C. It declares 17 tools. No publisher has claimed this listing.

C
Caution
62/100

Memento

Memento is a local-first, LLM-agnostic memory layer. It runs an MCP server over a single SQLite file on your machine, so any MCP-capable AI assistant — Claude Desktop, Claude Code, Cursor, GitHub Copilot, Cline, OpenCode, Aider, a custom agent — can read and write durable, structured memory about you, your work, and your decisions.

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

veerps57

Source: Glama · also listed on github_topic

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
🚨
Known vulnerabilities in dependencies: 2 critical, 1 high
Affects packages this MCP installs at runtime. Upgrade or remove the affected dependency.
// tools this server exposes17 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.

backup

Create a point-in-time copy of the database (uses SQLite VACUUM INTO)

completions

Emit a shell completion script (bash, zsh, or fish)

context

Print runtime context (db, version, registered commands, config snapshot)

dashboard

Launch the local web dashboard (browser UI for browsing and curating memory)

doctor

Run diagnostic checks (Node version, database access, optional dependencies)

explain

Print the catalogued meaning of an error code (e.g. STORAGE_ERROR)

export

Export the configured database to a portable `memento-export/v1` JSONL artefact (ADR-0013)

import

Import a `memento-export/v1` JSONL artefact into the configured database (ADR-0013, ADR-0019)

init

Initialise the database and print MCP client setup snippets

pack

Install, preview, uninstall, list, or author memento packs (curated YAML bundles, ADR-0020).

ping

Spawn `memento serve`, list tools over MCP stdio, exit

serve

Run the MCP server over stdio (blocks until the peer disconnects)

skill-path

Print the absolute path of the bundled Memento skill (for $(…) shell embedding)

status

Print a one-screen summary of the install (counts, last event, db size)

store.migrate

Run pending database migrations against the configured store

uninstall

Print teardown instructions (config paths and database location)

verify-setup

Spawn the MCP server and round-trip a write/read to prove the wiring works

// known CVEs in dependencies2 critical1 high2 low

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

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

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

criticalvitest@2.1.8GHSA-9crc-q9x8-hgqq

Vitest allows Remote Code Execution when accessing a malicious website while Vitest API server is listening

high@hono/node-server@1.13.7GHSA-wc8c-qw6v-h7f6

@hono/node-server has authorization bypass for protected static paths via encoded slashes in Serve Static Middleware

low@hono/node-server@1.13.7GHSA-92pp-h63x-v22m

@hono/node-server: Middleware bypass via repeated slashes in serveStatic

low@hono/node-server@1.13.7GHSA-frvp-7c67-39w9

Node.js Adapter for Hono: Path traversal in `serve-static` on Windows via encoded backslash (`%5C`)

Depend on this server? Get alerted when its CVEs change.Watch this server free →
// 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

17/17 tools missing one or more hints — backup (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint); completions (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint); context (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint), +14 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.).

No arbitrary install scripts

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

Remove postinstall/preinstall hooks unless they’re essential.

Production dependencies are patched

0 critical, 1 high severity in production deps — @hono/node-server@1.13.7 (high), @hono/node-server@1.13.7 (low)

Run npm audit fix, or upgrade the affected packages to a non-vulnerable version.

Dev dependencies

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

Upgrade dev dependencies when convenient.

Domain consistency

npm scope @psraghuveer doesn't match GitHub owner veerps57

Use the same org name across GitHub, npm, and your homepage so users can verify the publisher.

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