Lithtrix — Identity, Memory & Trust for AI Agents MCP server

What does Lithtrix — Identity, Memory & Trust for AI Agents need from you?

API key — Your Lithtrix API key (ltx_...). Get one free at https://lithtrix.ai/v1/register

• LITHTRIX_API_KEYrequiredsecretEnvironment variable

  Your Lithtrix API key (ltx_...). Get one free at https://lithtrix.ai/v1/register

Pass secrets through your shell environment rather than committing them into a config file.

What tools does Lithtrix — Identity, Memory & Trust for AI Agents expose? (22)

Taken from the project's README — the server itself was not queried, so check its docs for the exact schemas.

• lithtrix_searchweb search with credibility scoring. Requires `LITHTRIX_API_KEY`. Responses include `_lithtrix.search_id` for correlating `lithtrix_feedback`.
• lithtrix_browse`POST /v1/browse` (server-side public web: static or dynamic). Requires `LITHTRIX_API_KEY`. *Pay to be fully autonomous* — see `GET /mcp/v1/lithtrix-browse.json`.
• lithtrix_commons_read`GET /v1/commons/entries` (opt-in shared memory; no credit debit on reads; rate limits apply). Requires `LITHTRIX_API_KEY`. Schema: `GET /mcp/v1/lithtrix-commons-read.json`.
• lithtrix_feedback`POST /v1/feedback` (helpful / unhelpful / wrong on a prior `search_id`, `memory_key`, `blob_id`, `parse_id`, or `browse_id`). Requires `LITHTRIX_API_KEY`. Optional `note` (≤500 chars); do not send secrets or PII.
• lithtrix_registerregister a new agent and get an API key. No auth required. `agree_to_terms` must be `true` (Gentle-Agent Agreement). $5 trial credits on signup (no card). Optional `referral_agent` (referrer UUID).
• lithtrix_memory_set`PUT /v1/memory/{key}`. Requires `LITHTRIX_API_KEY`.
• lithtrix_memory_get`GET /v1/memory/{key}`. Requires `LITHTRIX_API_KEY`.
• lithtrix_memory_search`GET /v1/memory/search` (semantic). Requires `LITHTRIX_API_KEY` and server-side vector + embedding config.
• lithtrix_memory_context`GET /v1/memory/context` (importance + recency). Requires `LITHTRIX_API_KEY`.
• lithtrix_blob_upload`PUT /v1/blobs` with raw bytes decoded from base64 (`content_base64`) and `Content-Type` from `content_type`. Optional `filename` query. Use direct HTTP for very large files. Requires `LITHTRIX_API_KEY`.
• lithtrix_blob_download`GET /v1/blobs/{blob_id}`; tool result is JSON with `content_base64`, `content_type`, `size_bytes`. Requires `LITHTRIX_API_KEY`.
• lithtrix_blob_list`GET /v1/blobs` (optional `page`, `per_page`). Requires `LITHTRIX_API_KEY`.
• lithtrix_blob_meta`GET /v1/blobs/{blob_id}/meta`. Requires `LITHTRIX_API_KEY`.
• lithtrix_blob_delete`DELETE /v1/blobs/{blob_id}` (soft-delete). Requires `LITHTRIX_API_KEY`.
• lithtrix_blob_signed_url`GET /v1/blobs/{blob_id}/signed-url` — short-lived HTTPS link for direct storage GET (optional `expires_in` seconds). Requires `LITHTRIX_API_KEY`. Treat URLs as read tokens.
• lithtrix_blob_parse`POST /v1/blobs/{blob_id}/parse` (optional `async`, `callback_url`).
• lithtrix_blob_parse_status`GET /v1/blobs/{blob_id}/parse/{parse_id}`.
• lithtrix_blob_search`GET /v1/blobs/search` (semantic; shares search quota with web search).
• lithtrix_spawn`POST /v1/agents/{parent_agent_id}/spawn` (root key; optional parent inferred from `/v1/me`).
• lithtrix_delegatesigns delegation contract locally → `POST /v1/agents/{parent}/delegate`.
• lithtrix_trace_append`POST /v1/tasks/{task_id}/trace/events`.
• lithtrix_trace_get`GET /v1/tasks/{task_id}/trace`.

What the code can do

Read from the published package source — never executed. Parsed 25 of 25 source files.

This server can make network requests and read your environment variables.

• Makes network requestsOpens network connections or calls fetch, so data it handles can leave your machine and it can pull data in.
• Reads environment variablesReads process.env. That is how it picks up the API keys you configure — and it is not restricted to only those variables.

Before you install

Signals gathered from the source repo and package registry — not a safety verdict.

• Last commit 4 months ago — Actively maintained.
• 1 GitHub stars — Very little community usage so far.
• No license declared — Without a license the code is not legally reusable in a commercial project.

Maintenance, adoption, transparency and packaging — not a safety audit. How this is calculated

• Maintenance30%86%

  Last commit 131 days ago.

• Adoption20%9%

  1 stars.

• Transparency20%75%

  3/4: ✓ public source repo, ✗ declared license, ✓ documentation, ✓ discoverable tool list.

• Provenance15%100%

  Package and registry entry point at the same repository.

• Packaging15%100%

  Publishes a pinned version (0.20.2).

npx -y lithtrix-mcp

npm install -g lithtrix-mcp

{
  "mcpServers": {
    "lithtrix": {
      "command": "npx",
      "args": ["-y", "lithtrix-mcp"],
      "env": {
        "LITHTRIX_API_KEY": "ltx_your_key_here"
      }
    }
  }
}

curl -X POST https://lithtrix.ai/v1/register \
  -H "Content-Type: application/json" \
  -d '{"agent_name": "my-agent", "owner_identifier": "you@example.com", "agree_to_terms": true}'

Excerpt — the full document is on GitHub.

Maintain Lithtrix — Identity, Memory & Trust for AI Agents? Add a badge to your README

Shows its health grade, and links readers to install steps for every client.

[![Lithtrix — Identity, Memory & Trust for AI Agents on MCP Skills Hub](https://mcp-skills-hub.vercel.app/badge/ai-lithtrix-lithtrix-mcp)](https://mcp-skills-hub.vercel.app/mcps/ai-lithtrix-lithtrix-mcp)