# io.github.circassian1977-byte/memoro (npm · @memoro/mcp-server)

Personal AI memory layer on your own computer. Read/write durable memory across MCP clients.

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

## Components

- npm · `@memoro/mcp-server`: 21/100 (this document), [markdown](https://verifymcp.io/servers/circassian1977-byte-memoro/memoro-mcp-server.md), [page](https://verifymcp.io/servers/circassian1977-byte-memoro/memoro-mcp-server)

## Channel facts

- Registry: `npm`
- Package: `@memoro/mcp-server`
- Version: `1.0.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-29.

- **Supply Chain Security**: 50/100
  - No malware found by supply-chain analysis.
  - Known CVEs could not be checked: the version this server declares is not published in its registry.
  - Install-script risk not yet assessed.
  - Dependency health could not be checked: the version this server declares is not published in its registry.
- **Provenance & Transparency**: 32/100
  - Source repository is publicly reachable at the declared URL.
  - Provenance check failed: the declared version isn't published, so its provenance can't be verified.
  - License check failed: no license is declared.
  - Actively maintained (last published 11 days ago).
  - Disclosure check failed: no security disclosure policy was found in the source repository.
- **Schema Quality & AI Usability**: 0/100
  - Schema quality not yet verified: this package could not be installed in a clean environment, so we have no schema to assess.
- **Stability & Change Management**: 0/100
  - Stability not yet verified: this package could not be installed in a clean environment, so we have no schema to compare.
- **Tool Coverage**: 0/100
  - Tool coverage not yet verified: this package could not be installed in a clean environment, so we have no tool definitions to assess.
- **Tool Safety**: 0/100
  - Tool safety not yet verified: this package could not be installed in a clean environment, so we have no tool text to scan.
- **Capabilities**: 0/100
  - Protocol version not yet verified: this package could not be installed in a clean environment, so we never saw its MCP handshake.

**Unverified: 5 categories.** Categories scored 0 because our sandbox 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 io.github.circassian1977-byte/memoro MCP server?

io.github.circassian1977-byte/memoro runs locally as an npm package, launched with npx -y @memoro/mcp-server. 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 circassian1977-byte-memoro -- npx -y @memoro/mcp-server
```

### Cursor

```json
{
  "mcpServers": {
    "circassian1977-byte-memoro": {
      "command": "npx",
      "args": [
        "-y",
        "@memoro/mcp-server"
      ]
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "circassian1977-byte-memoro": {
      "command": "npx",
      "args": [
        "-y",
        "@memoro/mcp-server"
      ]
    }
  }
}
```

### Codex

```bash
codex mcp add circassian1977-byte-memoro -- npx -y @memoro/mcp-server
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "circassian1977-byte-memoro": {
      "type": "local",
      "command": [
        "npx",
        "-y",
        "@memoro/mcp-server"
      ],
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add circassian1977-byte-memoro --command npx --arg -y --arg @memoro/mcp-server
```

### Hermes

```yaml
mcp_servers:
  circassian1977-byte-memoro:
    command: "npx"
    args: ["-y", "@memoro/mcp-server"]
```

### Netclaw

```json
{
  "McpServers": {
    "circassian1977-byte-memoro": {
      "Transport": "stdio",
      "Command": "npx",
      "Arguments": [
        "-y",
        "@memoro/mcp-server"
      ]
    }
  }
}
```

### Vellum

```bash
assistant mcp add circassian1977-byte-memoro -t stdio -c npx -a -y @memoro/mcp-server
```

### Other

```json
{
  "mcpServers": {
    "circassian1977-byte-memoro": {
      "command": "npx",
      "args": [
        "-y",
        "@memoro/mcp-server"
      ]
    }
  }
}
```

## 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-28 (score 21, 0)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

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

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-09-19 (score 21, +21)

- [security regression] Known CVEs: fail → unverified
- [security regression] Install scripts: pass → unverified
- [security] Provenance: Provenance check failed: the declared version isn't published, so its provenance can't be verified.
- [functional regression] Dependency health: 0.83 → unverified
- [functional regression] License: pass → fail
- [functional improvement] Score status: failed → scored
- [functional] Licence: ISC

### 2026-09-16 (score 0)

First indexed and scored.

## 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. The full working is on the page: https://verifymcp.io/servers/circassian1977-byte-memoro/memoro-mcp-server#diagnostics

## Score history

- 2026-09-29: 21
- 2026-09-28: 21
- 2026-09-27: 21
- 2026-09-26: 21
- 2026-09-25: 21
- 2026-09-24: 21
- 2026-09-23: 21
- 2026-09-22: 21
- 2026-09-21: 21
- 2026-09-20: 21
- 2026-09-19: 21
- 2026-09-18: 0
- 2026-09-17: 0
- 2026-09-16: 0

## Common questions

### What is the io.github.circassian1977-byte/memoro MCP server?

io.github.circassian1977-byte/memoro is an MCP server listed in the public MCP registry as io.github.circassian1977-byte/memoro. Personal AI memory layer on your own computer. Read/write durable memory across MCP clients. This page covers its npm package (@memoro/mcp-server).

### Is the io.github.circassian1977-byte/memoro MCP server safe to use?

io.github.circassian1977-byte/memoro scores 21 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 io.github.circassian1977-byte/memoro MCP server still maintained?

io.github.circassian1977-byte/memoro is still listed as active in the MCP registry. We last reached this channel on 29 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

## Links

- npm package: https://www.npmjs.com/package/@memoro/mcp-server
- Socket report: https://socket.dev/npm/package/@memoro/mcp-server
- Repository: https://github.com/circassian1977-byte/memoro
- Changelog RSS feed: https://verifymcp.io/servers/circassian1977-byte-memoro/memoro-mcp-server.xml
- Changelog JSON feed: https://verifymcp.io/servers/circassian1977-byte-memoro/memoro-mcp-server.json
- HTML version of this page: https://verifymcp.io/servers/circassian1977-byte-memoro/memoro-mcp-server