mcp-server-basic-memory

Provides an MCP server that implements a basic in-memory memory store for tools/agents to persist ephemeral conversation/task state during the lifetime of the server process.

Evaluated Apr 04, 2026 (25d ago)
Homepage ↗ Repo ↗ Ai Ml mcp memory agents in-memory state-management tooling
⚙ Agent Friendliness
31
/ 100
Can an agent use this?
🔒 Security
22
/ 100
Is it safe for agents?
⚡ Reliability
24
/ 100
Does it work consistently?

Score Breakdown

⚙ Agent Friendliness

MCP Quality
55
Documentation
30
Error Messages
0
Auth Simplicity
30
Rate Limits
0

🔒 Security

TLS Enforcement
20
Auth Strength
20
Scope Granularity
0
Dep. Hygiene
30
Secret Handling
40

Without provided repo/manifest details, security posture is uncertain. In-memory memory services can still leak data through logs or unintended access if the MCP endpoint is exposed; auth/TLS and safe logging should be verified in the actual code.

⚡ Reliability

Uptime/SLA
0
Version Stability
35
Breaking Changes
35
Error Recovery
25
AF Security Reliability

Best When

You want fast, minimal MCP integration for ephemeral memory and can tolerate data loss on restart or scaling.

Avoid When

You need persistence, compliance-grade logging controls, or safe handling of highly sensitive data.

Use Cases

  • Agent scratchpad/state management during a session
  • Lightweight conversational memory for prototypes
  • Testing MCP tool calling flows that require a memory primitive
  • Short-lived context caching for multi-step agent workflows

Not For

  • Durable storage or long-term memory across restarts
  • Sensitive data storage without additional controls
  • Production systems needing persistence, backups, or cross-instance consistency

Interface

REST API
No
GraphQL
No
gRPC
No
MCP Server
Yes
SDK
No
Webhooks
No

Authentication

OAuth: No Scopes: No

No authentication details were provided in the supplied package information; many basic MCP examples run without auth, but this cannot be confirmed here.

Pricing

Free tier: No
Requires CC: No

Pricing not provided; assuming self-hosted open-source-style package.

Agent Metadata

Pagination
none
Idempotent
False
Retry Guidance
Not documented

Known Gotchas

  • In-memory state is typically lost on server restart and is not shared across replicas/instances.
  • Concurrent tool calls may race unless the implementation includes synchronization/atomic operations.
  • If no auth is implemented, exposing the MCP server publicly can be risky.

Alternatives

Full Evaluation Report

Comprehensive deep-dive: security analysis, reliability audit, agent experience review, cost modeling, competitive positioning, and improvement roadmap for mcp-server-basic-memory.

AI-powered analysis · PDF + markdown · Delivered within 30 minutes

$99

Package Brief

Quick verdict, integration guide, cost projections, gotchas with workarounds, and alternatives comparison.

Delivered within 10 minutes

$3

Score Monitoring

Get alerted when this package's AF, security, or reliability scores change significantly. Stay ahead of regressions.

Continuous monitoring

$3/mo

Scores are editorial opinions as of 2026-04-04.

8642
Packages Evaluated
17761
Need Evaluation
586
Need Re-evaluation
Community Powered