# Fidelis Memory (pypi · fidelis-memory)

Recall locally stored agent memories through an MCP-compatible host.

- Trust score: 32/100 (low)
- Change this week: +16
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-09-21

## Components

- pypi · `fidelis-memory`: 32/100 (this document), [markdown](https://verifymcp.io/servers/hermes-labs-ai-fidelis-memory/fidelis-memory.md), [page](https://verifymcp.io/servers/hermes-labs-ai-fidelis-memory/fidelis-memory)

## Channel facts

- Registry: `pypi`
- Package: `fidelis-memory`
- Version: `0.2.0`
- Transport: `stdio`

## Trust breakdown

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. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-09-21.

- **Supply Chain Security**: 74/100
  - No malware found by supply-chain analysis.
  - A critical CVE affects chromadb, and no fixed version has been published yet.
  - Runs hatchling.build at install time, a recognised native-build step with no shell scripting around it.
  - 13 of 104 dependencies flagged as unhealthy.
- **Provenance & Transparency**: 48/100
  - Source repository is publicly reachable at the declared URL.
  - Provenance check failed: no build-provenance attestation is published.
  - Clear OSI-approved license (MIT).
  - Actively maintained (last published 0 days ago).
  - Publishes a security disclosure policy (SECURITY.md).
- **Schema Quality & AI Usability**: 0/100
  - 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.
- **Stability & Change Management**: 0/100
  - 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.
- **Tool Coverage**: 0/100
  - 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.
- **Tool Safety**: 0/100
  - 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.
- **Capabilities**: 0/100
  - 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: 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.

## Install

### How do I install the Fidelis Memory MCP server?

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

### Claude

```bash
claude mcp add hermes-labs-ai-fidelis-memory -- uvx fidelis-memory
```

### Cursor

```json
{
  "mcpServers": {
    "hermes-labs-ai-fidelis-memory": {
      "command": "uvx",
      "args": [
        "fidelis-memory"
      ]
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "hermes-labs-ai-fidelis-memory": {
      "command": "uvx",
      "args": [
        "fidelis-memory"
      ]
    }
  }
}
```

### Codex

```bash
codex mcp add hermes-labs-ai-fidelis-memory -- uvx fidelis-memory
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "hermes-labs-ai-fidelis-memory": {
      "type": "local",
      "command": [
        "uvx",
        "fidelis-memory"
      ],
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add hermes-labs-ai-fidelis-memory --command uvx --arg fidelis-memory
```

### Hermes

```yaml
mcp_servers:
  hermes-labs-ai-fidelis-memory:
    command: "uvx"
    args: ["fidelis-memory"]
```

### Netclaw

```json
{
  "McpServers": {
    "hermes-labs-ai-fidelis-memory": {
      "Transport": "stdio",
      "Command": "uvx",
      "Arguments": [
        "fidelis-memory"
      ]
    }
  }
}
```

### Vellum

```bash
assistant mcp add hermes-labs-ai-fidelis-memory -t stdio -c uvx -a fidelis-memory
```

### Other

```json
{
  "mcpServers": {
    "hermes-labs-ai-fidelis-memory": {
      "command": "uvx",
      "args": [
        "fidelis-memory"
      ]
    }
  }
}
```

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-09-21 (score 32, 0)

- [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.
- [functional] 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.

### 2026-09-20 (score 32, 0)

- [security] 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.
- [functional] 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: 0.1.0 → 0.2.0

### 2026-09-16 (score 32, +1)

- [functional improvement] Security disclosure: fail → pass

### 2026-09-15 (score 31, +15)

- [security improvement] Malware scan: unverified → pass

### 2026-09-14 (score 16, −15)

- [security regression] Malware scan: pass → unverified

### 2026-09-13 (score 31, 0)

- [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.
- [functional] 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] Package version: 0.0.96 → 0.1.0
- [functional] Package version: 0.0.96 → 0.0.97

### 2026-09-12 (score 31, 0)

- [security] 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.
- [functional] 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: 0.0.95 → 0.0.96

### 2026-09-03 (score 31, +15)

- [security improvement] Malware scan: unverified → pass

## MCP tools (0)

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.

## Diagnostics

Captured diagnostic sections: Provenance, Install scripts, Vulnerabilities, Dependencies. The full working is on the page: https://verifymcp.io/servers/hermes-labs-ai-fidelis-memory/fidelis-memory#diagnostics

## Score history

- 2026-09-21: 32
- 2026-09-20: 32
- 2026-09-19: 32
- 2026-09-18: 32
- 2026-09-17: 32
- 2026-09-16: 32
- 2026-09-15: 31
- 2026-09-14: 16
- 2026-09-13: 31
- 2026-09-12: 31
- 2026-09-11: 31
- 2026-09-10: 31
- 2026-09-09: 31
- 2026-09-08: 31
- 2026-09-07: 31
- 2026-09-06: 31
- 2026-09-05: 31
- 2026-09-04: 31
- 2026-09-03: 31
- 2026-09-02: 16

## Common questions

### What is the Fidelis Memory MCP server?

Fidelis Memory is an MCP server listed in the public MCP registry as io.github.hermes-labs-ai/fidelis-memory. Recall locally stored agent memories through an MCP-compatible host. This page covers its PyPI package (fidelis-memory).

### Is the Fidelis Memory MCP server safe to use?

Fidelis Memory scores 32 out of 100 on VerifyMCP. We recorded 8 known advisories against it as of 21 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 Fidelis Memory MCP server still maintained?

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

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

## Links

- PyPI project: https://pypi.org/project/fidelis-memory/
- Socket report: https://socket.dev/pypi/package/fidelis-memory
- Repository: https://github.com/hermes-labs-ai/fidelis
- Changelog RSS feed: https://verifymcp.io/servers/hermes-labs-ai-fidelis-memory/fidelis-memory.xml
- Changelog JSON feed: https://verifymcp.io/servers/hermes-labs-ai-fidelis-memory/fidelis-memory.json
- HTML version of this page: https://verifymcp.io/servers/hermes-labs-ai-fidelis-memory/fidelis-memory