← Index

OMEM

io.github.troybrandonc-bit/omemv0.2.7Memory & RAG

Memory for AI agents that tracks beliefs over time and surfaces contradictions

The current version, v0.2.7, was published to the official MCP registry on 2026-08-26. It is distributed as omem-infrastructure on PyPI, filed under Memory & RAG by this index, and declares 5 environment variables. Removals and unreachable sources are measured across every server this index tracks, contract drift across the servers that answer in consecutive snapshots; the index's current counts put this record in context.

In-path gate · all MCP tools

Using OMEM in Claude, Cursor, Gemini CLI, Cline, or Zed?

MCP tool contracts can change remotely with no version bump. The mcpindex gate pins each contract and HOLDs the call when it drifts-before your agent acts. Zero credentials. This is not the package install for this server itself (use Install this server for that).

Install the mcpindex gate (one command)

Rewrites your MCP host config so each server launches behind the gate. Inspect first: curl -fsSL https://mcpindex.ai/install.sh | less

uv tool install mcpindex-gate && mcpindex-config-wire
Trust verdict · v1 advisory · method
NOT YET SCREENEDno verdict on file

Verdict not yet evaluated for this tool. The semantic screen takes adversarial cases first; coverage rolls out as the corpus expands (15/150 labels to graduation). The deterministic conformance probe is built but has not yet run on the public corpus, so a recorded verdict here is REVIEW or UNVERIFIED, never a clearing ALLOW. Until a verdict is recorded, an agent should treat this tool as not-yet-cleared and fall back to its own checks. Method: the eval, four-state verdict, honest limits.

Own this server? Screen its description →

That verdict was true at screening time (snapshot 2026-08-27).

Contracts can change after screening, with no version bump. The gate pins OMEM’s tool contracts on first sight and holds any silent change before your agent acts - the check that keeps being true on Tuesday.

See your first HOLD in 2 minutes →

Related: how to trust an MCP server · screen before install · silent contract drift

Environment variables
OMEM_API_KEY
requiredsecret

API key from the OMEM server. It is printed on first run of `omem-server`.

OMEM_PROJECT
required

Project id to read and write memory in, also printed on first run.

OMEM_BASE_URL

URL of the OMEM server.

OMEM_AGENT

The agent whose memory this process reads and writes. Fixed here rather than passed as a tool argument, so the model cannot act as a different agent.

OMEM_USER

The end user this process is acting for. Also fixed here, not a tool argument. Leave unset and no user-scoped memory is visible.

MCP quality score · maturity, not trust · methodology
freshness
25
completeness
20
installability
25
documentation
15
stability
5
Alternatives in Memory & RAG