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.

agentic-recall

NPM · AGENTIC-RECALL · SCANNED SEP 22

Long-term memory for agentic tasks. It tells you when it doesn't know.

Available components

npm · agentic-recall 0
0 this week 0 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 Security73
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 agentic-recall MCP server?

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

npm · agentic-recall

# add to Claude Code
claude mcp add dfrancislyondflabc-tech-agentic-recall -- npx -y agentic-recall
// .cursor/mcp.json
{
  "mcpServers": {
    "dfrancislyondflabc-tech-agentic-recall": {
      "command": "npx",
      "args": [
        "-y",
        "agentic-recall"
      ]
    }
  }
}
// .vscode/mcp.json
{
  "servers": {
    "dfrancislyondflabc-tech-agentic-recall": {
      "command": "npx",
      "args": [
        "-y",
        "agentic-recall"
      ]
    }
  }
}
# add to Codex CLI
codex mcp add dfrancislyondflabc-tech-agentic-recall -- npx -y agentic-recall
// opencode.json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "dfrancislyondflabc-tech-agentic-recall": {
      "type": "local",
      "command": [
        "npx",
        "-y",
        "agentic-recall"
      ],
      "enabled": true
    }
  }
}
# add to OpenClaw
openclaw mcp add dfrancislyondflabc-tech-agentic-recall --command npx --arg -y --arg agentic-recall
# ~/.hermes/config.yaml
mcp_servers:
  dfrancislyondflabc-tech-agentic-recall:
    command: "npx"
    args: ["-y", "agentic-recall"]
// ~/.netclaw/config/netclaw.json
{
  "McpServers": {
    "dfrancislyondflabc-tech-agentic-recall": {
      "Transport": "stdio",
      "Command": "npx",
      "Arguments": [
        "-y",
        "agentic-recall"
      ]
    }
  }
}
# add to Vellum
assistant mcp add dfrancislyondflabc-tech-agentic-recall -t stdio -c npx -a -y agentic-recall
// mcp.json
{
  "mcpServers": {
    "dfrancislyondflabc-tech-agentic-recall": {
      "command": "npx",
      "args": [
        "-y",
        "agentic-recall"
      ]
    }
  }
}
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.

  • 12 Sept 26 0
    • Malware scan: unverified → pass ▲ security
    • Stability: 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. security
    • Tool safety: 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. security
    • Schema quality: 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. functional
    • Capabilities: 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. functional
    • Tool coverage: 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. functional
  • 11 Sept 26 0
    • Malware scan: pass → unverified ▼ security
    • Package version: 2.0.0 → 2.0.2 functional
  • 10 Sept 26 0
    • Tool safety: Tool safety not yet verified: we do not have a sandbox capture of the tool definitions this version of the package serves yet. security
    • Stability: Stability not yet verified: we do not have a sandbox capture of the MCP schema this version of the package serves yet. security
    • Capabilities: Protocol version not yet verified: we do not have a sandbox capture of the MCP handshake this version of the package performs yet. functional
    • Tool coverage: Tool coverage not yet verified: we do not have a sandbox capture of the tool definitions this version of the package serves yet. functional
    • Schema quality: Schema quality not yet verified: we do not have a sandbox capture of the MCP schema this version of the package serves yet. functional
    • Package version: 1.8.2 → 2.0.0 functional
  • 9 Sept 26 0

    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 22 Sept 2026 · Analysed npm/agentic-recall@2.0.2

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 →

Vulnerabilities 13 findings
ID CVE Severity Vector Fix available
GHSA-2pr8-phx7-x9h3 CVE-2026-44294 medium CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L yes
GHSA-66ff-xgx4-vchm CVE-2026-44293 high yes
GHSA-685m-2w69-288q CVE-2026-44289 high CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H yes
GHSA-75px-5xx7-5xc7 CVE-2026-44291 high CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H yes
GHSA-f38q-mgvj-vph7 CVE-2026-54269 medium CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L yes
GHSA-fx83-v9x8-x52w CVE-2026-44292 medium CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N yes
GHSA-jggg-4jg4-v7c6 CVE-2026-45740 medium CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L yes
GHSA-jvwf-75h9-cwgg CVE-2026-44290 high CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H yes
GHSA-q6x5-8v7m-xcrf CVE-2026-44288 medium CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N yes
GHSA-wcpc-wj8m-hjx6 CVE-2026-48712 high CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H yes
GHSA-xq3m-2v4x-88gg CVE-2026-41242 critical CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H yes
GHSA-f88m-g3jw-g9cj high yes
GHSA-rgj7-g3m4-5g8c high yes

Background: What a vulnerability scan can and cannot prove →

Dependencies 173 packages
Packages resolved 173
Deprecated 1
Stale 61
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 agentic-recall MCP server?

agentic-recall is an MCP server listed in the public MCP registry as io.github.dfrancislyondflabc-tech/agentic-recall. Long-term memory for agentic tasks. It tells you when it doesn't know. This page covers its npm package (agentic-recall).

Is the agentic-recall MCP server still maintained?

agentic-recall is still listed as active in the MCP registry. We last reached this channel on 22 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 agentic-recall MCP server under?

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