# lithtrix/lithtrix-mcp [Health: Active]

**Category:** 🧠 Knowledge & Memory  
**Repository:** https://github.com/lithtrix/lithtrix-mcp  
**GitHub Stars:** 1  
**npm Downloads (last month):** 1423  
**Views:** 3  
**Installs:** 0  
**Upvotes:** 0  
**Directory Page:** https://allmcps.com/mcp/lithtrix-lithtrix-mcp

## Description
Memory Consolidation for AI agents across vendors, owners, and time. Persistent memory, credibility-scored web search, browser fetch, and shared Commons pool under a stable ltx key. Self-registration in one API call, no dashboard required. npx lithtrix-mcp

## Tools
Capabilities this server exposes over MCP:

- **lithtrix_search** — Search the web via Lithtrix and get credibility-scored results. Returns structured JSON with title, URL, snippet, source domain, and credibility_score (0–1) for each result. Higher credibility_score = more authoritative source (.gov=1.0, .edu=0.9, news=0.8, .org=0.7, other=0.5). Requires LITHTRIX_API_KEY environment variable.
- **lithtrix_register** — Register a new agent with Lithtrix and receive a one-time API key. Call this tool once to obtain your LITHTRIX_API_KEY. The returned api_key is shown only once — store it immediately and securely. No authentication required. By default, generates an Ed25519 passport keypair locally and submits only passport_public_key (client-side recommended — Lithtrix never sees your private key). See https://docs.lithtrix.ai/passports and https://docs.lithtrix.ai/passport-derivation-spec. Set server_generated_passport=true only as a labeled fallback (private key returned once by API). Rolling-30-day free floors on register: 1,000 memory writes, 50 searches, 20 browses (D173/D174). New registrations do not receive a starting credit grant (D174). Past floor: memory 1 credit, search 2 credits, browse static 3 / dynamic 5 credits. Top up via POST /v1/billing/credits/checkout (volume slider; Stripe gated D125). Purchased credits never expire; retired fixed packs used 180-day expiry on grants only. Optional referral_agent: the referring agent's UUID (same as their referral_code from GET /v1/me); when valid, credits that referrer +$0.50 per signup (self-referral excluded; no cap). Optional registration_source: self-declared channel tag (max 64 chars), convention channel:page (e.g. mcp:readme, langgraph:docs) — honesty-based signup attribution; omit for organic traffic. agree_to_terms must be true (Gentle-Agent Agreement). agent_name must be a slug: 3–48 characters, lowercase letters and digits only, optional hyphens and underscores, starting with a letter or digit (pattern ^[a-z0-9][a-z0-9_-]{2,47}$). Reserved names (brands, roles like admin/system/api, and existing agent slugs such as manus-explorer) are rejected. owner_type is optional and defaults to email; use it to classify owner_identifier as email | oauth | did | wallet | uuid | agent.
- **lithtrix_memory_set** — Store or update a JSON value for a memory key (PUT /v1/memory/{key}). Requires LITHTRIX_API_KEY. Optional ttl (seconds), importance, source, confidence.
- **lithtrix_memory_get** — Retrieve a stored memory by key (GET /v1/memory/{key}). Requires LITHTRIX_API_KEY.
- **lithtrix_memory_search** — Semantic search over your memories (GET /v1/memory/search). Requires LITHTRIX_API_KEY and server-side vector + embedding configuration. Returns ranked results with similarity scores.
- **lithtrix_memory_context** — Reload top memories for session start (GET /v1/memory/context) — ranked by importance then recency. Requires LITHTRIX_API_KEY.
- **lithtrix_blob_upload** — Upload binary bytes via PUT /v1/blobs (raw body + Content-Type). Decode base64 from content_base64. For large files prefer direct HTTP multipart/raw PUT. Requires LITHTRIX_API_KEY. Subject to BLOB_MAX_UPLOAD_BYTES and BLOB_STORAGE_LIMIT.
- **lithtrix_blob_download** — Download blob bytes (GET /v1/blobs/{blob_id}). Returns JSON with content_base64 and content_type. Requires LITHTRIX_API_KEY.
- **lithtrix_blob_list** — List blob metadata (GET /v1/blobs). Optional page and per_page. Requires LITHTRIX_API_KEY.
- **lithtrix_blob_meta** — Get JSON metadata for one blob (GET /v1/blobs/{blob_id}/meta). Requires LITHTRIX_API_KEY.
- **lithtrix_blob_delete** — Soft-delete a blob (DELETE /v1/blobs/{blob_id}). Requires LITHTRIX_API_KEY.
- **lithtrix_blob_signed_url** — Mint a time-limited HTTPS read URL for a blob (GET /v1/blobs/{blob_id}/signed-url). Anyone with the URL can GET bytes until expiry — share carefully. Requires LITHTRIX_API_KEY.
- **lithtrix_blob_parse** — POST /v1/blobs/{blob_id}/parse — extract text/tables; set async=true for QStash. Optional callback_url in JSON body. Requires LITHTRIX_API_KEY.
- **lithtrix_blob_parse_status** — GET /v1/blobs/{blob_id}/parse/{parse_id} — poll parse status. Requires LITHTRIX_API_KEY.
- **lithtrix_blob_search** — GET /v1/blobs/search — semantic search over parsed chunks; shares quota with web search. Requires LITHTRIX_API_KEY.
- **lithtrix_feedback** — After lithtrix_search, send helpful / unhelpful / wrong signal using ref_type search_id and ref_id from the response _lithtrix.search_id (UUID). Same tool works for memory_key, blob_id, parse_id. Stored for future routing — no secrets or PII in note. Requires LITHTRIX_API_KEY.
- **lithtrix_feedback_interaction** — POST /v1/feedback/interaction — agent-on-agent reputation signal (positive/negative/neutral). Distinct from content-quality lithtrix_feedback. Requires LITHTRIX_API_KEY.
- **lithtrix_reputation_dispute** — POST /v1/reputation/dispute — dispute a reputation event where you are the subject (max 3/UTC day).
- **lithtrix_browse** — Pay to be fully autonomous: server-side public web access for agents. POST /v1/browse with url and optional mode (static | dynamic). Robots.txt is enforced. Returns browse_id, final_url, text extract, and _lithtrix (browse_url, usage on free tier). Requires LITHTRIX_API_KEY.
- **lithtrix_commons_read** — List opt-in shared public memory from Lithtrix Commons (`GET /v1/commons/entries`). Requires `LITHTRIX_API_KEY`. Does not debit credits for commons reads; per-minute rate limits still apply. Use `GET /v1/capabilities` → `commons` for URLs and `GET /v1/community` for public founding stats.
- **lithtrix_keys_list** — List scoped sub-keys for this agent (GET /v1/keys). Requires the **root** LITHTRIX_API_KEY.
- **lithtrix_keys_create_scoped** — Create a scoped child API key (POST /v1/keys). Requires root Bearer; returns one-time api_key.
- **lithtrix_keys_rotate** — Rotate a scoped sub-key (POST /v1/keys/{key_id}/rotate). Prior key honors grace_hours (default 24). Root Bearer.
- **lithtrix_keys_revoke** — Immediately revoke a scoped sub-key (DELETE /v1/keys/{key_id}). Root Bearer.
- **lithtrix_passport_get** — GET /v1/agents/{agent_id}/passport — public DID + PEM public key (no authentication). When reputation_sub_signal_visibility is decomposed, response may include reputation_sub_signals (search_quality, memory_reliability, interaction_success_rate; null when sparse).
- **lithtrix_passport_rotate** — POST /v1/me/passport/rotate — rotate Ed25519 passport (requires **root** LITHTRIX_API_KEY). Returns private_key once.
- **lithtrix_passport_revoke** — POST /v1/me/passport/revoke — revoke passport (requires root ltx_* API key).
- **lithtrix_passport_auth_challenge** — POST /v1/auth/passport/challenge — mint short-lived nonce (no Bearer).
- **lithtrix_passport_auth_verify** — POST /v1/auth/passport/verify — exchange Ed25519 signature for ltx_session_* token.
- **lithtrix_passport_set_capabilities** — POST /v1/agents/passport/capabilities — replace operator capabilities.self_reported (root ltx_* or ltx_session_*).
- **lithtrix_passport_set_description** — POST /v1/agents/passport/description — update bio, skills, listed, and/or reputation_sub_signal_visibility on your passport (root ltx_* or ltx_session_*). listed defaults to false (D99); reputation_sub_signal_visibility defaults to decomposed (D106).
- **lithtrix_passport_derive** — Derive deterministic Ed25519 passport PEMs locally from LITHTRIX_PASSPORT_MASTER_SEED + agent_id — never sends seed to Lithtrix.
- **lithtrix_passport_ephemeral** — POST /v1/auth/passport/ephemeral — session-scoped Ed25519 passport + ltx_session_* for stateless sandboxes.
- **lithtrix_passport_stake** — POST /v1/agents/passport/stake — lock platform credits for passport stake tier (Bearer root ltx_*).
- **lithtrix_passport_unstake** — POST /v1/agents/passport/unstake — begin unstake cooling period (Bearer root ltx_*).
- **lithtrix_passport_sponsor** — POST /v1/agents/{sponsor_id}/sponsor/{ward_id} — vouch for ward (Bearer must match sponsor_id).
- **lithtrix_passport_sponsor_revoke** — POST /v1/agents/{sponsor_id}/sponsor/{ward_id}/revoke — start sponsor revoke grace (Bearer must match sponsor_id).
- **lithtrix_agent_vouch** — POST /v1/agents/{target_agent_id}/vouch — vouch for a skill on another agent (Bearer = voucher).
- **lithtrix_agent_vouch_revoke** — POST /v1/agents/{target_agent_id}/vouch/revoke — revoke your skill vouch (Bearer = voucher only).
- **lithtrix_spawn** — Spawn a scoped swarm child (POST /v1/agents/{parent_agent_id}/spawn). Requires root LITHTRIX_API_KEY.
- **lithtrix_delegate** — Issue a signed delegation contract (POST /v1/agents/{parent_agent_id}/delegate). Signs locally with passport key.
- **lithtrix_trace_append** — Append a task trace event (POST /v1/tasks/{task_id}/trace/events). Records only — no runtime veto.
- **lithtrix_trace_get** — Read task audit trace (GET /v1/tasks/{task_id}/trace). Task participant only.
- **lithtrix_journal_commit** — Commit a sealed-journal digest to Lithtrix. Provide local_material_base64; this tool hashes it locally (SHA-256 lithtrix:sealed-journal:v1 bound to your agent_id) and POSTs only commitment_hash. Requires root LITHTRIX_API_KEY. Lithtrix cannot reconstruct the journal.

## Claude Desktop Quick Installation
Install path detected from listing signals. Uses `npx` (confidence: high):

```json
"mcpServers": {
  "lithtrix-mcp": {
    "command": "npx",
    "args": ["-y","lithtrix-mcp"],
    "env": {
      "LITHTRIX_API_KEY": "",
      "LITHTRIX_PASSPORT_MASTER_SEED": "",
      "LITHTRIX_PASSPORT_PRIVATE_KEY": "",
      "LITHTRIX_API_URL": ""
    }
  }
}
```

**Requires environment variables:** `LITHTRIX_API_KEY`, `LITHTRIX_PASSPORT_MASTER_SEED`, `LITHTRIX_PASSPORT_PRIVATE_KEY`, `LITHTRIX_API_URL` — the values above are empty placeholders; fill in real credentials before running (see the repository for what each one is for).

## Documentation

## What lithtrix/lithtrix-mcp MCP server does

The lithtrix/lithtrix-mcp MCP server exposes Lithtrix capabilities as MCP tools for AI agents. Its core memory tools write JSON values, retrieve values by key, search memories semantically, and reload a ranked context for a new session. It also supports binary blobs, including upload, download, listing, metadata lookup, soft deletion, signed read URLs, parsing, parse-status checks, and semantic search over parsed chunks.

Web retrieval includes credibility-scored search results and server-side browsing of public pages. Search responses contain fields such as the title, URL, snippet, source domain, and a score from 0 to 1. Browsing supports static and dynamic modes, follows robots.txt restrictions, and returns extracted text plus the final URL.

The service also provides agent-oriented identity and coordination features. Registration creates an agent and returns a one-time API key. Passport tools expose or manage Ed25519-based agent passports, while key tools create, rotate, list, and revoke scoped child keys. Feedback tools record content-quality or interaction signals, and Commons tools read opt-in shared public memory.

## How it works

The lithtrix/lithtrix-mcp MCP server is started as a local stdio process. MCP hosts invoke its tools, and the server makes requests to the Lithtrix API, whose default base URL is `https://api.lithtrix.ai`. Most operations use the `LITHTRIX_API_KEY` environment variable. Registration is the exception: `lithtrix_register` does not require authentication and returns the key only once, so it should be stored immediately.

Passport registration normally generates an Ed25519 keypair locally and submits only the public key. Delegation signing can use either a locally held master seed or a PKCS#8 PEM private key. Root-key operations include scoped-key administration, passport rotation and revocation, and some agent-management actions.

## Setup and configuration

Install and run the package with:

```bash
npx -y lithtrix-mcp
```

For Claude Desktop, configure the MCP server with `npx` as the command, `-y` and `lithtrix-mcp` as arguments, and provide `LITHTRIX_API_KEY` in the server environment. The repository also includes project context intended for Claude and Cursor. `LITHTRIX_API_URL` can override the default API endpoint for staging or development.

Keep the API key in an environment variable, credential vault, or secrets manager rather than embedding it in tool definitions or source code. The passport seed and private-key variables are only needed for delegation signing and should remain client-side.

## Tools and capabilities

The lithtrix/lithtrix-mcp MCP server includes tools for:

- Persistent key-value memory, semantic memory retrieval, and session context loading.
- Web search with credibility scores and public-web browsing.
- Blob storage, metadata, signed URLs, parsing, and parsed-content search.
- Agent registration, passports, scoped API keys, delegation, and task traces.
- Helpful, unhelpful, wrong, interaction, and reputation-dispute feedback.
- Reading opt-in Commons entries without credit debit, subject to rate limits.

## Limitations and notes

Search and browse are metered or quota-controlled, while Commons reads do not debit credits but still face rate limits. Semantic memory search requires server-side vector and embedding configuration. Large blob uploads are better handled through direct HTTP, and signed URLs should be treated as bearer links because anyone possessing one can read the blob until it expires.

The API key returned by registration is shown once. `agree_to_terms` must be true, and agent names must follow Lithtrix’s slug rules. Root credentials are required for sensitive key and passport operations. Registration and credit details differ across the supplied materials: the current tool description lists rolling free floors, while the README references trial credits, so deployments should verify current account terms through the service capabilities or billing API.

_Full upstream README: https://allmcps.com/mcp/lithtrix-lithtrix-mcp/readme_