Memory MCP server

by infoinlet-marketplace·io.github.infoinlet-marketplace/mcp-memory·v0.1.1

Persistent searchable memory for AI agents — save/get/search across sessions, tags.

C65/100grade C

What users say

No reviews yet

Safety scan

C65/100

Adoption

Not measured yet

Usage numbers are collected on the next scan

Reviews

Nobody has reviewed Memory yet.

If you have run it, two minutes of your experience saves the next person an afternoon.

write = sends, deletes, buys or posts

Read from the package source without running it. The installed server may list more.

memory_deletewrite action
Delete a memory by key.
memory_get
Fetch a memory by exact key.
memory_list
List recent memories in a namespace (newest first).
memory_save
Save a memory for later recall. Provide a stable `key` to update an existing memory, or omit it to auto-generate one. Use `namespace` to separate projects/users and `tags` for filtering.
memory_search
Search memories by relevance to a query (semantic when configured, else keyword). Mode currently: ….

scanner v0.1.9 · 2026-09-27 · same rubric, same numbers if you re-run it

no findings

Code scan6 source files scanned25/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
Maintenancerepository not readable: repo not found3/15
Maintainer identityno repository or website to verify2/10

Overall 65/100. Components that don't apply are left out of the denominator. Any critical finding is an F.Rubric Appeal a finding JSON

Against every graded Web search MCP server, from our own scans and uptime checks. Updated after each scan run.

Safety score: 65/100; higher than 20% of 3,470 Web search servers
Tools: 5; the typical Web search server has 5
Tools that change things: 20%; typical: 0%. Fewer write tools means less an agent can break

What its tools let an agent do: 4 read · 1 change

Runs npx -y @infoinlet/mcp-memory on your machine. Read the scan report first; the gateway never runs local packages.

claude mcp add mcp-memory -- npx -y @infoinlet/mcp-memory

Is Memory MCP server safe?: With care: it is graded C, so read the findings first (65/100). Read the Memory safety report
How do I install Memory?: It runs on your machine. Copy the Claude Code, Cursor, VS Code or Claude Desktop config from the install section.
Does Memory need an API key?: Not as far as the registry entry and our scan can tell: no credentials are declared or required.
Is Memory maintained?: The latest release is v0.1.1.
What can I use instead of Memory?: Servers from other publishers that do the same job: Octobrain MCP server, Jshookmcp MCP server and Sui Knowledge Base (kapa.ai) MCP server.
How does Memory compare with other Web search MCP servers?: safety score 65/100 (higher than 20% of 3,470 Web search servers); tools 5 (the typical Web search server has 5); tools that change things 20% (typical: 0%. Fewer write tools means less an agent can break). Full comparison.

Same job from other publishers: the closest match first, then the best rated.

Octobrain
Persistent memory for AI assistants with semantic search and knowledge graph relationships.
not reviewed
Growing
A
Jshookmcp
Search-first MCP server for JavaScript reverse engineering: 735 tools across 36 domains.
not reviewed
Established
C
Sui Knowledge Base (kapa.ai)
Semantic search across Sui documentation and knowledge sources, powered by kapa.ai
not reviewed
Established
A
Free Search
No-API-key web search, page fetching and document reading across many engines. Local-first.
not reviewed
Established
B
Misakanet
Failure-memory layer for coding agents: search evidence-rated failure lessons by error text.
not reviewed
Established
A