Lex MCP server
Episodic memory, Frames, Policy Neighborhoods, and policy enforcement for AI agents.
B82/100grade B
Adoption
Growing
0 stars326 downloads/wk
Reviews
Write oneNobody has reviewed Lex yet.
If you have run it, two minutes of your experience saves the next person an afternoon.
Lex tools
No tool declarations could be read from the package source. They show once the server is installed.
Public scan report
scanner v0.1.5 · 2026-09-19 · same rubric, same numbers if you re-run it
no findings
- Code scan4 source files scanned25/25
- –Live reliabilityno gateway calls yet and no remote to proben/a
- –Tool poisoningtools not inspected (local package is not executed); not countedn/a
- Auth qualitystatic API keys via environment variables6/15
- Maintenancelast push 1 days ago15/15
- Maintainer identityregistry namespace matches repository owner7/10
Overall 82/100. Components that don't apply are left out of the denominator. Any critical finding is an F.RubricAppeal a findingJSON
Grade history
- 2026-09-19restoreC → Bscore 82
Install directly
Runs npx -y @smartergpt/lex-mcp on your machine. Read the scan report first; the gateway never runs local packages.
claude mcp add lex -- npx -y @smartergpt/lex-mcp
Lex: common questions
- Is Lex MCP server safe?
- Mostly: it is graded B (82/100). Read the Lex safety report
- How do I install Lex?
- It runs on your machine. Copy the Claude Code, Claude Desktop or Cursor config from the install section.
- Does Lex need an API key?
- Yes. The registry entry asks for
LEX_DATABASE_URL,LEX_POSTGRES_PASSWORD. - Is Lex maintained?
- The last commit was 2 days ago (2026-09-18). The latest release is v4.4.1.