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.

EvolutionDB Long-Term Memory

PYPI · MCP-SERVER-EVOLUTIONDB · SCANNED AUG 6

Persistent long-term memory for Claude Desktop / Claude Code, backed by EvolutionDB.

Available components

pypi · mcp-server-evolutiondb 0
0 this week 0 Trust /100

Dead

Every channel of this server has been unreachable for long enough to be marked dead. Its trust score is pinned to 0 and does not recover automatically: even once the server responds again it stays dead until it is manually reinstated.

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 Security0
  • Malware scan not yet available for this package.Unverified
  • Known CVEs could not be checked: we could not find this package in its registry.Unverified
  • Install-script risk not yet assessed.Unverified
  • Dependency health could not be checked: we could not find this package in its registry.Unverified
Provenance & Transparency0
  • Repository check failed: the declared repository URL returned HTTP 404. See how to fix → View diagnostics → Fail
  • Provenance check failed: the registry has no such package, so there's no artefact to verify. View diagnostics → Fail
  • License check failed: the registry has no such package, so no license can be read.Fail
  • Maintenance check failed: the registry has no such package, so there's no release history to read.Fail
  • Security-disclosure policy not yet verified: we couldn't inspect the source repository.Unverified
Schema Quality & AI Usability0
  • Schema quality not yet verified: our sandbox run of this package did not complete, so we have no schema to assess.Unverified
Stability & Change Management0
  • Stability not yet verified: our sandbox run of this package did not complete, so we have no schema to compare.Unverified
Tool Coverage0
  • Tool coverage not yet verified: our sandbox run of this package did not complete, so we have no tool definitions to assess.Unverified
Tool Safety–

Not scored yet: our latest scan of this package recorded no findings here. That is usually because the category is newer than the scan, or because we have not captured the MCP schema this package serves yet. It fills in the next time we score it.

Capabilities0
  • Protocol version not yet verified: our sandbox run of this package did not complete, so we never saw its MCP handshake.Unverified

Unverified: 5 categories

Categories scored 0 because we could not verify them: a data source with nothing on this package, evidence we could not reach, or a check we could not run. We only credit what we can confirm.

Install

How do I install the EvolutionDB Long-Term Memory MCP server?

EvolutionDB Long-Term Memory runs locally as a PyPI package, launched with uvx mcp-server-evolutiondb. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

pypi · mcp-server-evolutiondb

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

  • 6 Aug 26 −15
    • Malware scan: pass → unverified ▼ security
  • 5 Aug 26 +15
    • Malware scan: unverified → pass ▲ security
  • 3 Aug 26 −15
    • Malware scan: pass → unverified ▼ security
  • 2 Aug 26 +15
    • Malware scan: unverified → pass ▲ security
  • 31 Jul 26 0
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 30 Jul 26 −18
    • Malware scan: pass → unverified ▼ security
  • 27 Jul 26 0
    • Schema quality: Schema quality not yet verified: our sandbox run of this package did not complete, so we have no schema to assess. functional
    • Tool coverage: Tool coverage not yet verified: our sandbox run of this package did not complete, so we have no tool definitions to assess. functional
  • 26 Jul 26 18

    First indexed and scored.

    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
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 6 Aug 2026 · Analysed pypi/mcp-server-evolutiondb@1.17.0

Provenance Package not found

The registry answered that no such package exists, so no provenance could be looked up.

Result Package not found
Ecosystem pypi

Background: How many MCP packages publish verified provenance →

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 EvolutionDB Long-Term Memory MCP server?

EvolutionDB Long-Term Memory is an MCP server listed in the public MCP registry as io.github.alptekin/evolutiondb-memory. Persistent long-term memory for Claude Desktop / Claude Code, backed by EvolutionDB. This page covers its PyPI package (mcp-server-evolutiondb).

Is the EvolutionDB Long-Term Memory MCP server safe to use?

EvolutionDB Long-Term Memory scores 0 out of 100 on VerifyMCP. 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 EvolutionDB Long-Term Memory MCP server still maintained?

EvolutionDB Long-Term Memory has been unreachable for long enough that we treat it as dead, and its score is pinned to zero. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.