agent-memory-mcp (xultrax-web/agent-memory-mcp) is an MCP server listed on the M8ven Trust Index. It scores 74 out of 100, grade C. It declares 24 tools. No publisher has claimed this listing.

C
Caution
74/100

agent-memory-mcp

Guardrails for AI coding agents that enforces rules via compliance receipts, blocking destructive actions and syncing rules across all AI tools.

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

xultrax-web

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
⚠️
Known vulnerabilities in dependencies: 1 high
Affects packages this MCP installs at runtime. Upgrade or remove the affected dependency.
⚠️
Tests do not pass
Either the test suite is broken or the code regressed. Either way the published behaviour can’t be verified by the publisher’s own tests.
No credential exfiltration, no sensitive file access, no obfuscation
Static analysis found nothing flowing your secrets to unexpected places.
Open source with a license and README
Anyone can audit the code, the license is declared, and the publisher documents what it does.
// tools this server exposes24 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.

save_memory
search_memories

Fuzzy search across name, description, and body. Tolerates typos, word-order shifts, and partial matches. Returns top matches with relevance scores (0-100) and body-context snippets. Use this for human-readable browsing.

relevant_memories

Find memories relevant to a query and return their FULL content (not summaries). Designed for LLM ingestion — call this when the assistant needs context on a topic and the memory index alone isn't specific enough. Returns up to `max` memories as a markdown document.

get_memory

Fetch a single memory by name.

list_memories

List stored memories, optionally filtered by type and/or tags. Paginated.

delete_memory
restore_memory

Restore a memory from .trash/ back into the active store. Picks the most recent trash entry for the name.

doctor

Check storage integrity. Reports orphan files (on disk but not indexed), dangling index entries (no file), unreadable files, and invalid types. Pass rebuild-index=true to reconstruct MEMORY.md from disk.

stats

Dashboard of memory-store state: counts per type, total size, largest memory, audit-log size, trash count.

rotate_key

Rotate the receipt-signing key material (HMAC and/or Ed25519). Generates fresh keys and INVALIDATES every outstanding Compliance Receipt. Use after a suspected key leak — e.g. the .keyring was ever committed or synced. Optional `mode`: 'hmac' | 'ed25519' | 'both' (default 'both').

init

Install a starter guardrail pack — sensible hard/soft rules (protect main, block rm -rf, no prod data destruction, no curl|sh, flag secrets) — and emit them to every tool's companion files. Zero-config protection on day one. Pass force=true to overwrite same-named rules. Pair with `agent-memory inst

validate_receipt

Validate a CRP 1.1 (Ed25519) Compliance Receipt issued by ANOTHER agent-memory server using that server's published public key — no shared secret (the federation primitive). Checks signature, expiry, and required caveats. Pass `receipt` (object or JSON string) and `public_key` (inline PEM or a file

log_events

Read recent entries from the audit event log (.events.jsonl). Returns the last N events, optionally filtered by action.

verify_memory

Re-evaluate a memory's claims against signals in its content. Extracts URLs, dates, and file paths from the body; flags stale-date signals on project-type memories; returns type-specific verification heuristics for the LLM or operator to act on. Pairs with the audit_stale prompt.

find_backlinks

List memories that link to the given memory via [[wiki-link]] syntax in their bodies. Useful for building a 'what references this' view.

find_related

Surface memories related to a given one. Ranks by combining: outbound [[wiki-links]], inbound backlinks, shared tags, same type, and content similarity (name + description). Use this to navigate the memory graph by association rather than by exact lookup.

sync_status

Report the git-sync state of the memory store: remote URL, branch, local uncommitted files, commits ahead/behind origin. Use this before opening a new session to know if you have stale memories from another machine.

sync_push

Commit any local memory changes and push to the configured git remote. Auto-generates a timestamped commit message if none provided. Use at the end of a session to make memories available on your other machines.

sync_pull

Pull memory updates from the configured git remote (fast-forward only). Run at the start of a session to get memories saved on other machines. Refuses to pull if there are uncommitted local changes.

save_rule
list_rules

List every active rule memory with severity, scope, and staleness markers (>90 days since last_verified). Use this to audit which rules are currently constraining the agent.

audit
check_action
emit_companions
// known CVEs in dependencies1 high

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

high@modelcontextprotocol/sdk@1.0.4GHSA-w48q-cv73-mx4w

Model Context Protocol (MCP) TypeScript SDK does not enable DNS rebinding protection by default

Depend on this server? Get alerted when its CVEs change.Watch this server free →
// environment variables
To run this server yourself, you supply these values. They go in your own MCP client configuration and stay on your machine. The secret label means the value is sensitive, not that the server mishandles it.
configAGENT_MEMORY_AUTO_EMIT_DIRSet =/path/to/project and the server re-emits all four files automatically on every rule save.
configAGENT_MEMORY_COMPANION_DIR
configAGENT_MEMORY_DIR"env": { "": "/abs/path/to/memory" }
configAGENT_MEMORY_EMBED_MODEL
configAGENT_MEMORY_EMBED_URL
configAGENT_MEMORY_LOGOperational logging is separate. Set =debuginfowarnerror (default info) and structured lines stream to stderr — won't pollute the MCP stdio channel.
configAGENT_MEMORY_SCOPE"env": { "": "global" }
configCRP_SIGNING_MODECRP 1.1 · Ed25519 asymmetric signing (set =ed25519)
configEDITORe opens the highlighted memory in $ (vim/notepad/nano/whatever) — saves back to disk
configFORCE_COLORColor output is on by default in TTYs. Set NO_COLOR=1 to disable, =1 to force-enable in pipes.
configGIT_AUTHOR_EMAILCommits use the identity agent-memory <agent-memory@local> by default — set / GIT_COMMITTER_EMAIL in your environment if you want per-machine attribution.
configGIT_AUTHOR_NAME
configGIT_COMMITTER_EMAILCommits use the identity agent-memory <agent-memory@local> by default — set GIT_AUTHOR_EMAIL / in your environment if you want per-machine attribution.
configGIT_COMMITTER_NAME
configNO_COLORColor output is on by default in TTYs. Set =1 to disable, FORCE_COLOR=1 to force-enable in pipes.
// 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

24/24 tools missing one or more hints — save_memory (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint); search_memories (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint); relevant_memories (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint), +21 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.

Tests pass

npm test failed — tests do not pass

Make sure npm test runs cleanly. Common cause: missing build step or missing env vars.

Shell command execution

2 child_process calls — runs shell commands

Prefer library functions over shell-outs. If you must shell out, ensure all inputs are properly escaped.

Production dependencies are patched

0 critical, 1 high severity in production deps — @modelcontextprotocol/sdk@1.0.4 (high)

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

Dependency freshness

3/7 production deps abandoned (no release in 2+ years): proper-lockfile@2022-06-24 (4.1y), gray-matter@2023-07-12 (3y), ink-text-input@2024-05-21 (2.2y)

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 5 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/xultrax-web/agent-memory-mcp?variant=verified)](https://m8ven.ai/mcp/xultrax-web/agent-memory-mcp)
Shows verification status without the grade. Want the grade badge instead? Remove ?variant=verified from the URL.
commit: e09cfef91a2b48495c59f898598fa18d92503798
code hash: 47052e4f464526933526de38e7de4a0b01f5ec942037a1837abe9afd90c2cd61
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