Lex MCP Server

by smartergpt Your server? Claim it

local only

Lex runs on your own machine — the client starts it, so there is no endpoint to ping. Last commit 17 Sep 2026.

Episodic memory, Frames, Policy Neighborhoods, and policy enforcement for AI agents.

—

Installs / week

not published

Stars

24 open issues

17 Sep 2026

Last commit

from GitHub

MIT

License

TypeScript

What changed 10

Every tool that appeared, vanished or quietly changed what it asks for. Recorded since 8 September 2026. No other catalogue keeps this.

17 Sep the owner changed

16 Sep the owner changed

15 Sep the owner changed

14 Sep the owner changed

13 Sep the owner changed

12 Sep the owner changed

11 Sep the owner changed

10 Sep the owner changed

9 Sep the owner changed

8 Sep the owner changed

Nothing serious here today

Today is the operative word: we check Lex every 15 minutes and re-read its code on every release. Watch it and you find out the day that stops being true.

Alternatives to Lex

same job, measured the same way

Lex

by guffawaffle

Episodic memory and architectural policy for AI agents. Frames, Atlas, and Policy.

211 installs/wk local only

Policyvault

by zapsoblige-hash

Non-custodial Kaspa policy enforcement for AI agents; signers retain custody.

97 installs/wk local only

Mengram

by alibaizhanov

Long-term memory for AI agents: semantic facts, episodic events, and procedural workflows

answering

Pensyve

by major7apps

Universal memory runtime for AI agents — episodic, semantic, and procedural memory.

answering

signet-eval

by jmcentire

Deterministic policy enforcement and MCP management for AI agent tool calls.

local only

Agentos

by imran-siddique

Build and manage policy-compliant AI agents with safety enforcement and compliance checking

27 installs/wk local only

Tokenmaxxen MCP

by austinmunday

Collective episodic memory for AI coding agents — search, deposit, comment, showcase builds.

84 installs/wk local only

Tork Governance

by torkjacobs

AI agent governance for MCP: PII detection, policy enforcement, compliance, and kill switch.

45 installs/wk local only

Lex — questions

Answers built from our own checks of this server.

Why is there no uptime for Lex?

Lex runs on your own machine over stdio — there is no network address to reach, so uptime cannot be measured for it by anyone.

Is Lex open source?

Yes — it is published under the MIT licence, written in TypeScript, 0 stars on GitHub and 24 open issues. The source link is on this page, so you can read exactly what it does with your data before you connect it.