# OriMem (pypi · orimem-mcp)

Long-term memory for coding agents in your own Obsidian vault: recall, write-back, capture.

- Trust score: 34/100 (low)
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-21

## Components

- pypi · `orimem-mcp`: 34/100 (this document), [markdown](https://verifymcp.io/servers/wen5555-orimem/orimem-mcp.md), [page](https://verifymcp.io/servers/wen5555-orimem/orimem-mcp)

## Channel facts

- Registry: `pypi`
- Package: `orimem-mcp`
- Version: `0.1.3`
- 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-11-21.

- **Supply Chain Security**: 50/100
  - Malware scan not yet available for this package.
  - No known CVEs affecting this package version or its production dependencies.
  - Runs setuptools.build_meta at install time, a recognised build step with no custom scripting around it.
  - 2 of 35 dependencies flagged as unhealthy.
- **Provenance & Transparency**: 97/100
  - Source repository is publicly reachable at the declared URL.
  - Cryptographically verified build provenance (signed, bound to Wen5555/OriMem).
  - Clear OSI-approved license (MIT).
  - Actively maintained (last published 3 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 installed, but its server did not start, so we have no schema to assess.
- **Stability & Change Management**: 0/100
  - Stability not yet verified: this package installed, but its server did not start, so we have no schema to compare.
- **Tool Coverage**: 0/100
  - Tool coverage not yet verified: this package installed, but its server did not start, so we have no tool definitions to assess.
- **Tool Safety**: 0/100
  - Tool safety not yet verified: this package installed, but its server did not start, so we have no tool text to scan.
- **Capabilities**: 0/100
  - Protocol version not yet verified: this package installed, but its server did not start, 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 OriMem MCP server?

OriMem runs locally as a PyPI package, launched with uvx orimem-mcp mcp. 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 wen5555-orimem -- uvx orimem-mcp mcp
```

### Cursor

```json
{
  "mcpServers": {
    "wen5555-orimem": {
      "command": "uvx",
      "args": [
        "orimem-mcp",
        "mcp"
      ]
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "wen5555-orimem": {
      "command": "uvx",
      "args": [
        "orimem-mcp",
        "mcp"
      ]
    }
  }
}
```

### Codex

```bash
codex mcp add wen5555-orimem -- uvx orimem-mcp mcp
```

### opencode

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

### OpenClaw

```bash
openclaw mcp add wen5555-orimem --command uvx --arg orimem-mcp --arg mcp
```

### Hermes

```yaml
mcp_servers:
  wen5555-orimem:
    command: "uvx"
    args: ["orimem-mcp", "mcp"]
```

### Netclaw

```json
{
  "McpServers": {
    "wen5555-orimem": {
      "Transport": "stdio",
      "Command": "uvx",
      "Arguments": [
        "orimem-mcp",
        "mcp"
      ]
    }
  }
}
```

### Vellum

```bash
assistant mcp add wen5555-orimem -t stdio -c uvx -a orimem-mcp mcp
```

### Other

```json
{
  "mcpServers": {
    "wen5555-orimem": {
      "command": "uvx",
      "args": [
        "orimem-mcp",
        "mcp"
      ]
    }
  }
}
```

## 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-11-21 (score 34, −15)

- [security regression] Malware scan: pass → unverified

### 2026-11-20 (score 49, +15)

- [security improvement] Malware scan: unverified → pass

### 2026-11-17 (score 34)

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, Install scripts, Dependencies. The full working is on the page: https://verifymcp.io/servers/wen5555-orimem/orimem-mcp#diagnostics

## Score history

- 2026-11-21: 34
- 2026-11-20: 49
- 2026-11-19: 34
- 2026-11-18: 34
- 2026-11-17: 34

## Common questions

### What is the OriMem MCP server?

OriMem is an MCP server listed in the public MCP registry as io.github.Wen5555/orimem. Long-term memory for coding agents in your own Obsidian vault: recall, write-back, capture. This page covers its PyPI package (orimem-mcp).

### Is the OriMem MCP server safe to use?

OriMem scores 34 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 21 November 2026. Its build provenance is signed and verified. 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 OriMem MCP server still maintained?

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

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

### What did VerifyMCP test on the OriMem MCP server?

VerifyMCP ran 8 checks on OriMem, covering Known CVEs, Install scripts, Dependency health, Source repository and 4 more. 6 items could not be completed, a gap on our side rather than a finding about OriMem: Malware scan, Schema quality, Stability, Tool coverage and 2 more. 5 categories score 0 for that reason, because we only credit what we can confirm. Endpoint Security and Transport & Reachability do not apply to a PyPI package, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.

## Links

- PyPI project: https://pypi.org/project/orimem-mcp/
- Socket report: https://socket.dev/pypi/package/orimem-mcp
- Repository: https://github.com/Wen5555/OriMem
- Changelog RSS feed: https://verifymcp.io/servers/wen5555-orimem/orimem-mcp.xml
- Changelog JSON feed: https://verifymcp.io/servers/wen5555-orimem/orimem-mcp/changelog.json
- Trust report (JSON): https://verifymcp.io/servers/wen5555-orimem/orimem-mcp.json
- HTML version of this page: https://verifymcp.io/servers/wen5555-orimem/orimem-mcp
