Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

MemoryLayer

NPM · @RAAJVAMSY/MEMORYLAYER · SCANNED SEP 20

Local-first persistent memory for AI agents, with reasoning and formal verification.

Available components

npm · @raajvamsy/memorylayer 31
31 Trust /100
Trust breakdown (7 categories)

How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score → Why this is hard to score →

Supply Chain Security92
  • No malware found by supply-chain analysis.Pass
  • No known CVEs affecting this package version or its production dependencies.Pass
  • Runs a script at install time (preinstall,postinstall) that we could not recognise. It may be perfectly ordinary, but we do not read the published tarball, so we cannot say what it does. View diagnostics → Partial
  • 69 of 231 dependencies flagged as unhealthy (1 deprecated). View diagnostics → Partial
Provenance & Transparency19
Schema Quality & AI Usability0
  • Schema quality not yet verified: this server's registry entry declares environment variables (an API key or similar) that our sandbox does not supply, so we have no schema to assess.Unverified
Stability & Change Management0
  • Stability not yet verified: this server's registry entry declares environment variables (an API key or similar) that our sandbox does not supply, so we have no schema to compare.Unverified
Tool Coverage0
  • Tool coverage not yet verified: this server's registry entry declares environment variables (an API key or similar) that our sandbox does not supply, so we have no tool definitions to assess.Unverified
Tool Safety0
  • Tool safety not yet verified: this server's registry entry declares environment variables (an API key or similar) that our sandbox does not supply, so we have no tool text to scan.Unverified
Capabilities0
  • Protocol version not yet verified: this server's registry entry declares environment variables (an API key or similar) that our sandbox does not supply, so we never saw its MCP handshake.Unverified

Unverified: 5 categories

Categories scored 0 because our sandbox run of this package has not given us the schema these checks need to read. That is a gap on our side rather than a finding about the package, and we only credit what we can confirm, so the score stands at 0 until the capture succeeds. We are working through the fleet, so this normally clears without any action from you. How we score packages →

Install

How do I install the MemoryLayer MCP server?

MemoryLayer runs locally as an npm package, launched with npx -y @raajvamsy/memorylayer. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

npm · @raajvamsy/memorylayer

# add to Claude Code
claude mcp add in-memorylayer-memorylayer -- npx -y @raajvamsy/memorylayer
// .cursor/mcp.json
{
  "mcpServers": {
    "in-memorylayer-memorylayer": {
      "command": "npx",
      "args": [
        "-y",
        "@raajvamsy/memorylayer"
      ]
    }
  }
}
// .vscode/mcp.json
{
  "servers": {
    "in-memorylayer-memorylayer": {
      "command": "npx",
      "args": [
        "-y",
        "@raajvamsy/memorylayer"
      ]
    }
  }
}
# add to Codex CLI
codex mcp add in-memorylayer-memorylayer -- npx -y @raajvamsy/memorylayer
// opencode.json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "in-memorylayer-memorylayer": {
      "type": "local",
      "command": [
        "npx",
        "-y",
        "@raajvamsy/memorylayer"
      ],
      "enabled": true
    }
  }
}
# add to OpenClaw
openclaw mcp add in-memorylayer-memorylayer --command npx --arg -y --arg @raajvamsy/memorylayer
# ~/.hermes/config.yaml
mcp_servers:
  in-memorylayer-memorylayer:
    command: "npx"
    args: ["-y", "@raajvamsy/memorylayer"]
// ~/.netclaw/config/netclaw.json
{
  "McpServers": {
    "in-memorylayer-memorylayer": {
      "Transport": "stdio",
      "Command": "npx",
      "Arguments": [
        "-y",
        "@raajvamsy/memorylayer"
      ]
    }
  }
}
# add to Vellum
assistant mcp add in-memorylayer-memorylayer -t stdio -c npx -a -y @raajvamsy/memorylayer
// mcp.json
{
  "mcpServers": {
    "in-memorylayer-memorylayer": {
      "command": "npx",
      "args": [
        "-y",
        "@raajvamsy/memorylayer"
      ]
    }
  }
}
Changelog

Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.

  • 20 Sept 26 31

    First indexed and scored.

Diagnostics

Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.

Captured 20 Sept 2026 · Analysed npm/@raajvamsy/memorylayer@1.7.1

Provenance No attestation

The registry publishes no build provenance for this version, so there is nothing to verify.

Result No attestation
Ecosystem npm

Background: How many MCP packages publish verified provenance →

Install scripts 2 scripts
Hook Tier Command
preinstall unreviewed node scripts/preinstall.mjs
postinstall unreviewed node scripts/postinstall.mjs

Background: Why install scripts are a supply-chain risk →

Dependencies 231 packages
Packages resolved 231
Deprecated 1
Stale 68
Tree resolution Complete

Background: SBOMs and build attestations, explained →

MCP tools

The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →

Tools for package channels are captured by running the package in an isolated sandbox. The most recent sandbox run could not capture a tool list from this package.

Common questions

What is the MemoryLayer MCP server?

MemoryLayer is an MCP server listed in the public MCP registry as in.memorylayer/memorylayer. Local-first persistent memory for AI agents, with reasoning and formal verification. This page covers its npm package (@raajvamsy/memorylayer).

Is the MemoryLayer MCP server safe to use?

MemoryLayer scores 31 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 20 September 2026. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

Is the MemoryLayer MCP server still maintained?

MemoryLayer is still listed as active in the MCP registry. We last reached this channel on 20 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

What licence is the MemoryLayer MCP server under?

MemoryLayer declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.