@smartergpt/lex-mcp

MCPcommunity
v4.4.0GuffawaffleMITUpdated 5d agonpmGitHub

MCP server for Lex episodic memory - stdio transport wrapper

Works in
ClaudeCursorCopilotGemini

Inferred from the transports this listing declares (stdio). A client not listed here hasn’t been ruled out — it just isn’t something Forge can confirm.

Automatically indexed from public sources. Not yet verified by the developer on Forge.Claim this listing →
211Downloads/wk
5d agoLast update
Reads these credentials
  • LEX_DATABASE_URLAPI keyoptional

    PostgreSQL connection URL for the compatibility adapter. Treat as secret because it may contain credentials.

  • LEX_POSTGRES_PASSWORDAPI keyoptional

    PostgreSQL password supplied separately when LEX_DATABASE_URL omits one.

Declared by the author in the official MCP registry. Forge does not store, broker, or ever see these values — the config below is scaffolded with placeholders you fill in locally.

Package
AuthorGuffawaffle
LicenseMIT
Version4.4.0
Sourcenpm+mcp-registry
Trust Status
B
60/100Good
Listed in Forge index+10/10
Publisher identity verified+0/20
Publisher: run `forge publish` from the package repo to claim ownership
Ed25519 publish signature+0/5
Included automatically when the publisher runs `forge publish`
Domain verification+0/5
Publisher: host /.well-known/forge.json on the package homepage with { "publisher": "<github-login>" }
npm Trusted Publishing (Sigstore)+0/5
Publish from GitHub Actions with --provenance so the attestation binds this package to this repo
npm maintainer match+0/5
Earned once your identity is verified above and that login is an npm maintainer of this package
CVE scan · clean+30/30
Static analysis · clean+20/20
Paste into Claude Code, Cursor, or any AI assistant to fix all gaps
StatusCommunity-indexed
PublisherUnverified
SignatureUnsigned
Domain
Provenance
Dependencies✓ 0 resolved · none vulnerable
Tool surface
Security scan✓ Cleanv4.0.0 · 1mo agoHow well does this scan work?
EvalsNone
IndexedJul 12, 2026

Verification confirms publisher identity (repo ownership), not code safety. The security scan covers known CVEs and suspicious install scripts.

Tools

No tool declarations found in the source1mo ago

Forge read 3 source files from the published package tarball and matched no MCP tool registrations. Extraction is pattern-based over shipped source: a server that builds its tool list at runtime, or that ships only bundled or minified code, registers nothing this can see. Treat it as “not detected”, not as “exposes none”.

About

MCP server for Lex episodic memory - stdio transport wrapper

Keywords
mcpmodel-context-protocollexepisodic-memoryai-agents
Alternatives
Comparing tool surfaces…

No dependency coverage

This package was last scanned before Forge began storing the resolved tree. The next scan will record it.

Topics

Related in memory & knowledge graphs