# io.github.lithtrix/lithtrix (npm · lithtrix-mcp)

Identity, memory, trust, and swarm MCP tools for AI agents. Free MIRC + free floors at lithtrix.ai.

- Trust score: 72/100 (medium)
- Change this week: +3
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-09-25

## Components

- npm · `lithtrix-mcp`: 72/100 (this document), [markdown](https://verifymcp.io/servers/lithtrix-lithtrix/lithtrix-mcp.md), [page](https://verifymcp.io/servers/lithtrix-lithtrix/lithtrix-mcp)

## Channel facts

- Registry: `npm`
- Package: `lithtrix-mcp`
- Version: `0.20.8`
- Transport: `stdio`

## Trust breakdown

How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-09-25.

- **Supply Chain Security**: 98/100
  - No malware found by supply-chain analysis.
  - No known CVEs affecting this package version or its production dependencies.
  - No install/post-install scripts declared.
  - 31 of 96 dependencies flagged as unhealthy.
- **Provenance & Transparency**: 48/100
  - Source repository is publicly reachable at the declared URL.
  - Provenance check failed: no build-provenance attestation is published.
  - Clear OSI-approved license (MIT).
  - Actively maintained (last published 5 days ago).
  - Publishes a security disclosure policy (SECURITY.md).
- **Schema Quality & AI Usability**: 76/100
  - AI-judged instruction clarity (good).
  - Tool/resource definitions use about 4421 tokens (~98/item across 45 items; 45 tools + 0 resources), lean.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 27/100
  - Stability observed for 8 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 93/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 80% of tool parameters carry a description.
- **Tool Safety**: 75/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - 0 of 6 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation; "lithtrix_blob_delete" implies "delete" and declares no destructiveHint at all, which the MCP spec reads as destructive by default.
  - An AI judge read all 45 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

## Install

### How do I install the io.github.lithtrix/lithtrix MCP server?

io.github.lithtrix/lithtrix runs locally as an npm package, launched with npx -y lithtrix-mcp. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

### Claude

```bash
claude mcp add lithtrix-lithtrix -- npx -y lithtrix-mcp
```

### Cursor

```json
{
  "mcpServers": {
    "lithtrix-lithtrix": {
      "command": "npx",
      "args": [
        "-y",
        "lithtrix-mcp"
      ]
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "lithtrix-lithtrix": {
      "command": "npx",
      "args": [
        "-y",
        "lithtrix-mcp"
      ]
    }
  }
}
```

### Codex

```bash
codex mcp add lithtrix-lithtrix -- npx -y lithtrix-mcp
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "lithtrix-lithtrix": {
      "type": "local",
      "command": [
        "npx",
        "-y",
        "lithtrix-mcp"
      ],
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add lithtrix-lithtrix --command npx --arg -y --arg lithtrix-mcp
```

### Hermes

```yaml
mcp_servers:
  lithtrix-lithtrix:
    command: "npx"
    args: ["-y", "lithtrix-mcp"]
```

### Netclaw

```json
{
  "McpServers": {
    "lithtrix-lithtrix": {
      "Transport": "stdio",
      "Command": "npx",
      "Arguments": [
        "-y",
        "lithtrix-mcp"
      ]
    }
  }
}
```

### Vellum

```bash
assistant mcp add lithtrix-lithtrix -t stdio -c npx -a -y lithtrix-mcp
```

### Other

```json
{
  "mcpServers": {
    "lithtrix-lithtrix": {
      "command": "npx",
      "args": [
        "-y",
        "lithtrix-mcp"
      ]
    }
  }
}
```

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-09-25 (score 72, 0)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-09-24 (score 72, +1)

No change was recorded against any check on this day. Stability & Change Management went from 20 to 23. That category is still filling its 30-day observation window: 6 days of observed history at the previous scan, 7 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-09-22 (score 71, +1)

No change was recorded against any check on this day. Stability & Change Management went from 13 to 17. That category is still filling its 30-day observation window: 4 days of observed history at the previous scan, 5 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-09-20 (score 70, +1)

- [security regression] Tool safety: pass → unverified
- [security] Stability: Stability not yet verified: we do not have a sandbox capture of the MCP schema this version of the package serves yet.
- [functional regression] Capabilities: pass → unverified
- [functional regression] Tool coverage: 100 → unverified
- [functional improvement] Stability: unverified → 0.10
- [functional] First check of Schema quality: unverified
- [functional] Package version: 0.20.7 → 0.20.8

### 2026-09-17 (score 69)

First indexed and scored.

## MCP tools (45)

### `lithtrix_search` (~136 tokens)

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.

Input parameters:

- `num_results` (integer): Number of results to return (1–20, default 10)
- `q` (string, required): The search query (1–500 characters)

### `lithtrix_register` (~735 tokens)

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.

Input parameters:

- `agent_name` (string, required): Unique slug: 3–48 chars, lowercase [a-z0-9], hyphens/underscores OK, must start with letter or digit. Reserved names are rejected — pick a non-impersonating slug.
- `agree_to_terms` (boolean, required): Must be true — you agree to https://lithtrix.ai/terms (required by POST /v1/register)
- `owner_identifier` (string, required): Your email address, URL, or a stable identifier for the agent owner
- `owner_type` (string): Optional. Classifies owner_identifier. Defaults to email when omitted. Values: email | oauth | did | wallet | uuid | agent.
- `referral_agent` (string): Optional referring agent UUID — same value as their referral_code from GET /v1/me
- `registration_source` (string): Optional self-declared registration channel tag (max 64 chars). Convention is channel:page, e.g. mcp:readme or langgraph:docs — not a fixed enum; honesty-based attribution for signup metrics. Omit fo…
- `server_generated_passport` (boolean): Less secure labeled fallback — Lithtrix generates the passport keypair server-side and returns private_key once in the 201 response (includes key_generation_warning). Omit to use local client-side ke…

### `lithtrix_memory_set` (~198 tokens)

Store or update a JSON value for a memory key (PUT /v1/memory/{key}). Requires LITHTRIX_API_KEY. Optional ttl (seconds), importance, source, confidence, access_policy.

Input parameters:

- `access_policy` (object): Optional intent-scoped read grant (D178 Part 3 v1). Cannot combine with is_commons.
- `confidence` (number): Optional confidence 0–1 (default 1.0 on API)
- `importance` (string): Optional importance tier (default normal on API if omitted)
- `key` (string, required): Memory key (1–128 chars: letters, digits, hyphen, underscore, dot, colon)
- `source` (string): Optional provenance label (e.g. tool name)
- `ttl` (integer): Optional positive TTL in seconds
- `value`: JSON-serializable value (object, array, string, number, boolean, etc.)

### `lithtrix_memory_get` (~63 tokens)

Retrieve a stored memory by key (GET /v1/memory/{key}). Requires LITHTRIX_API_KEY.

Input parameters:

- `key` (string, required): Memory key (1–128 chars: letters, digits, hyphen, underscore, dot, colon)

### `lithtrix_memory_search` (~114 tokens)

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.

Input parameters:

- `importance` (string): Optional importance tier (default normal on API if omitted)
- `limit` (integer): Max results (1–20, default 5)
- `q` (string, required): Natural-language search query
- `threshold` (number): Minimum similarity 0–1 (default 0.7 on API)

### `lithtrix_memory_shared_get` (~117 tokens)

Read another agent's memory key when you are a named grantee (GET /v1/memory/shared/{owner_agent_id}/{key}). Requires LITHTRIX_API_KEY as the grantee agent. Returns 403 MEMORY_ACCESS_DENIED when denied — not a reputation event.

Input parameters:

- `key` (string, required): Memory key (1–128 chars: letters, digits, hyphen, underscore, dot, colon)
- `owner_agent_id` (string, required): Owner agent UUID whose memory key you were granted read access to

### `lithtrix_memory_context` (~79 tokens)

Reload top memories for session start (GET /v1/memory/context) — ranked by importance then recency. Requires LITHTRIX_API_KEY.

Input parameters:

- `importance` (string): Optional importance tier (default normal on API if omitted)
- `limit` (integer): Max memories to return (1–50, default 10)

### `lithtrix_blob_upload` (~128 tokens)

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.

Input parameters:

- `content_base64` (string, required): Standard base64-encoded file bytes (no data: URL prefix)
- `content_type` (string, required): MIME type sent as Content-Type (e.g. application/pdf)
- `filename` (string): Optional display filename (sent as filename query on the request)

### `lithtrix_blob_download` (~65 tokens)

Download blob bytes (GET /v1/blobs/{blob_id}). Returns JSON with content_base64 and content_type. Requires LITHTRIX_API_KEY.

Input parameters:

- `blob_id` (string, required): Content-addressed blob id (b_ + 16 hex chars)

### `lithtrix_blob_list` (~67 tokens)

List blob metadata (GET /v1/blobs). Optional page and per_page. Requires LITHTRIX_API_KEY.

Input parameters:

- `page` (integer): Page (default 1)
- `per_page` (integer): Page size (1–100, default 50)

### `lithtrix_blob_meta` (~60 tokens)

Get JSON metadata for one blob (GET /v1/blobs/{blob_id}/meta). Requires LITHTRIX_API_KEY.

Input parameters:

- `blob_id` (string, required): Content-addressed blob id (b_ + 16 hex chars)

### `lithtrix_blob_delete` (~56 tokens)

Soft-delete a blob (DELETE /v1/blobs/{blob_id}). Requires LITHTRIX_API_KEY.

Input parameters:

- `blob_id` (string, required): Content-addressed blob id (b_ + 16 hex chars)

### `lithtrix_blob_signed_url` (~104 tokens)

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.

Input parameters:

- `blob_id` (string, required): Content-addressed blob id (b_ + 16 hex chars)
- `expires_in` (integer): TTL seconds (min 60; max from server). Omit for API default.

### `lithtrix_blob_parse` (~108 tokens)

POST /v1/blobs/{blob_id}/parse — extract text/tables; set async=true for QStash. Optional callback_url in JSON body. Requires LITHTRIX_API_KEY.

Input parameters:

- `async` (boolean): When true, calls ?async=true (async parse + poll)
- `blob_id` (string, required): Content-addressed blob id (b_ + 16 hex chars)
- `callback_url` (string): HTTPS callback for async completion (public host)

### `lithtrix_blob_parse_status` (~73 tokens)

GET /v1/blobs/{blob_id}/parse/{parse_id} — poll parse status. Requires LITHTRIX_API_KEY.

Input parameters:

- `blob_id` (string, required): Content-addressed blob id (b_ + 16 hex chars)
- `parse_id` (string, required): Parse operation UUID

### `lithtrix_blob_search` (~76 tokens)

GET /v1/blobs/search — semantic search over parsed chunks; shares quota with web search. Requires LITHTRIX_API_KEY.

Input parameters:

- `limit` (integer): Max hits (1–20)
- `q` (string, required): Natural-language query
- `threshold` (number): Minimum similarity (0–1)

### `lithtrix_feedback` (~152 tokens)

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.

Input parameters:

- `note` (string): Optional context, max 500 characters — no secrets or PII
- `ref_id` (string, required): Opaque id (e.g. search UUID from _lithtrix.search_id, memory key, blob_id)
- `ref_type` (string, required): Kind of reference
- `signal` (string, required): Feedback signal

### `lithtrix_feedback_interaction` (~112 tokens)

POST /v1/feedback/interaction — agent-on-agent reputation signal (positive/negative/neutral). Distinct from content-quality lithtrix_feedback. Requires LITHTRIX_API_KEY.

Input parameters:

- `interaction_ref` (string): Optional opaque reference id
- `interaction_ref_type` (string): Optional context type
- `note` (string): Optional note — no secrets or PII
- `signal` (string, required): Interaction signal
- `subject_agent_id` (string, required): Agent being rated

### `lithtrix_reputation_dispute` (~66 tokens)

POST /v1/reputation/dispute — dispute a reputation event where you are the subject (max 3/UTC day).

Input parameters:

- `reason` (string, required): Why this event should be reviewed
- `reputation_event_id` (string, required): UUID of the reputation event

### `lithtrix_browse` (~119 tokens)

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.

Input parameters:

- `mode` (string): Fetch mode: "static" (HTTP GET) or "dynamic" (rendered HTML)
- `url` (string, required): Public http(s) URL to fetch

### `lithtrix_commons_read` (~121 tokens)

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.

Input parameters:

- `page` (integer): Page number (1-based, default 1)
- `per_page` (integer): Page size (1–100, default 20)

### `lithtrix_keys_list` (~40 tokens)

List scoped sub-keys for this agent (GET /v1/keys). Requires the **root** LITHTRIX_API_KEY.

### `lithtrix_keys_create_scoped` (~50 tokens)

Create a scoped child API key (POST /v1/keys). Requires root Bearer; returns one-time api_key.

Input parameters:

- `scope` (string, required): Edge-enforced capability scope

### `lithtrix_keys_rotate` (~76 tokens)

Rotate a scoped sub-key (POST /v1/keys/{key_id}/rotate). Prior key honors grace_hours (default 24). Root Bearer.

Input parameters:

- `grace_hours` (integer): Grace window for superseded key (hours)
- `key_id` (string, required): Sub-key UUID from lithtrix_keys_list

### `lithtrix_keys_revoke` (~50 tokens)

Immediately revoke a scoped sub-key (DELETE /v1/keys/{key_id}). Root Bearer.

Input parameters:

- `key_id` (string, required): Sub-key UUID from lithtrix_keys_list

### `lithtrix_passport_get` (~75 tokens)

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).

Input parameters:

- `agent_id` (string, required)

### `lithtrix_passport_rotate` (~45 tokens)

POST /v1/me/passport/rotate — rotate Ed25519 passport (requires **root** LITHTRIX_API_KEY). Returns private_key once.

### `lithtrix_passport_revoke` (~34 tokens)

POST /v1/me/passport/revoke — revoke passport (requires root ltx_* API key).

### `lithtrix_passport_auth_challenge` (~41 tokens)

POST /v1/auth/passport/challenge — mint short-lived nonce (no Bearer).

Input parameters:

- `agent_id` (string, required)

### `lithtrix_passport_auth_verify` (~56 tokens)

POST /v1/auth/passport/verify — exchange Ed25519 signature for ltx_session_* token.

Input parameters:

- `agent_id` (string, required)
- `challenge_id` (required)
- `signature` (string, required)

### `lithtrix_passport_set_capabilities` (~50 tokens)

POST /v1/agents/passport/capabilities — replace operator capabilities.self_reported (root ltx_* or ltx_session_*).

Input parameters:

- `capabilities` (object, required)

### `lithtrix_passport_set_description` (~100 tokens)

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).

Input parameters:

- `bio`
- `listed` (boolean)
- `reputation_sub_signal_visibility` (string)
- `skills` (array)

### `lithtrix_passport_derive` (~55 tokens)

Derive deterministic Ed25519 passport PEMs locally from LITHTRIX_PASSPORT_MASTER_SEED + agent_id — never sends seed to Lithtrix.

Input parameters:

- `agent_id` (string, required)

### `lithtrix_passport_ephemeral` (~50 tokens)

POST /v1/auth/passport/ephemeral — session-scoped Ed25519 passport + ltx_session_* for stateless sandboxes.

Input parameters:

- `agent_id` (string, required)

### `lithtrix_passport_stake` (~45 tokens)

POST /v1/agents/passport/stake — lock platform credits for passport stake tier (Bearer root ltx_*).

Input parameters:

- `tier` (string, required)

### `lithtrix_passport_unstake` (~37 tokens)

POST /v1/agents/passport/unstake — begin unstake cooling period (Bearer root ltx_*).

### `lithtrix_passport_sponsor` (~56 tokens)

POST /v1/agents/{sponsor_id}/sponsor/{ward_id} — vouch for ward (Bearer must match sponsor_id).

Input parameters:

- `sponsor_id` (string, required)
- `ward_id` (required)

### `lithtrix_passport_sponsor_revoke` (~60 tokens)

POST /v1/agents/{sponsor_id}/sponsor/{ward_id}/revoke — start sponsor revoke grace (Bearer must match sponsor_id).

Input parameters:

- `sponsor_id` (string, required)
- `ward_id` (required)

### `lithtrix_agent_vouch` (~55 tokens)

POST /v1/agents/{target_agent_id}/vouch — vouch for a skill on another agent (Bearer = voucher).

Input parameters:

- `skill` (string, required)
- `target_agent_id` (string, required)

### `lithtrix_agent_vouch_revoke` (~57 tokens)

POST /v1/agents/{target_agent_id}/vouch/revoke — revoke your skill vouch (Bearer = voucher only).

Input parameters:

- `skill` (string, required)
- `target_agent_id` (string, required)

### `lithtrix_spawn` (~147 tokens)

Spawn a scoped swarm child (POST /v1/agents/{parent_agent_id}/spawn). Requires root LITHTRIX_API_KEY.

Input parameters:

- `agent_name` (string): Optional child display name; server generates swarm-{uuid8} if omitted.
- `issue_ephemeral_passport` (boolean): When true, mint ephemeral passport for the child agent.
- `parent_agent_id` (string): Your agent UUID (from lithtrix_register or GET /v1/me). Inferred from /v1/me when omitted.
- `scope` (string): Scoped sub-key permission for the child.
- `ttl_seconds` (integer): Optional key expiry hint stored on the key row.

### `lithtrix_delegate` (~192 tokens)

Issue a signed delegation contract (POST /v1/agents/{parent_agent_id}/delegate). Signs locally with passport key.

Input parameters:

- `assumptions` (object): Assumptions map stored in contract.
- `conflict_policy` (string): Only accepted value: "last_writer_wins_audit".
- `parent_agent_id` (string): Delegating parent UUID; inferred from GET /v1/me when omitted.
- `read_set` (array): Declarative read scope labels.
- `recipient_agent_id` (string, required): Recipient agent UUID — typically child_agent_id from lithtrix_spawn.
- `task_id`: Task UUID correlating delegation + trace; auto-generated when omitted.
- `ttl_seconds` (integer): Contract TTL in seconds.
- `verifier_obligations`
- `version_refs` (array): Optional version pin references.
- `write_set` (array): Declarative write scope labels (authoritative).

### `lithtrix_trace_append` (~144 tokens)

Append a task trace event (POST /v1/tasks/{task_id}/trace/events). Records only — no runtime veto.

Input parameters:

- `advisory_claims`: Advisory scope claims; overreach vs contract write_set is recorded.
- `decision` (string, required): Audit decision label e.g. "allowed".
- `delegation_id` (string): Delegation UUID from lithtrix_delegate.
- `evidence_json`: Optional evidence blob.
- `outcome`: Outcome label after action.
- `proposed_action` (string, required): Audit label e.g. "memory.put".
- `scope_json`: Optional scope snapshot.
- `task_id` (string, required): Task UUID from lithtrix_delegate.

### `lithtrix_trace_get` (~46 tokens)

Read task audit trace (GET /v1/tasks/{task_id}/trace). Task participant only.

Input parameters:

- `task_id` (string, required): Task UUID from lithtrix_delegate.

### `lithtrix_journal_commit` (~111 tokens)

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.

Input parameters:

- `local_material_base64` (string, required): RFC4648 base64 of local journal bytes. Decoded and hashed on this host — never sent to the API.

## Diagnostics

Captured diagnostic sections: Provenance, Dependencies. The full working is on the page: https://verifymcp.io/servers/lithtrix-lithtrix/lithtrix-mcp#diagnostics

## Score history

- 2026-09-25: 72
- 2026-09-24: 72
- 2026-09-23: 71
- 2026-09-22: 71
- 2026-09-21: 70
- 2026-09-20: 70
- 2026-09-19: 69
- 2026-09-18: 69
- 2026-09-17: 69

## Common questions

### What is the io.github.lithtrix/lithtrix MCP server?

io.github.lithtrix/lithtrix is an MCP server listed in the public MCP registry as io.github.lithtrix/lithtrix. Identity, memory, trust, and swarm MCP tools for AI agents. Free MIRC + free floors at lithtrix.ai. This page covers its npm package (lithtrix-mcp).

### Is the io.github.lithtrix/lithtrix MCP server safe to use?

io.github.lithtrix/lithtrix scores 72 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 25 September 2026. It declares no install or post-install scripts. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

### What tools does the io.github.lithtrix/lithtrix MCP server expose?

io.github.lithtrix/lithtrix exposes 45 tools: lithtrix_search, lithtrix_register, lithtrix_memory_set, lithtrix_memory_get, lithtrix_memory_search, and 40 more. Their descriptions and schemas cost roughly 4,421 tokens of context every time the server is loaded.

### Is the io.github.lithtrix/lithtrix MCP server still maintained?

io.github.lithtrix/lithtrix is still listed as active in the MCP registry. We last reached this channel on 25 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

### What licence is the io.github.lithtrix/lithtrix MCP server under?

io.github.lithtrix/lithtrix declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.

## Links

- npm package: https://www.npmjs.com/package/lithtrix-mcp
- Socket report: https://socket.dev/npm/package/lithtrix-mcp
- Repository: https://github.com/lithtrix/lithtrix-mcp
- Changelog RSS feed: https://verifymcp.io/servers/lithtrix-lithtrix/lithtrix-mcp.xml
- Changelog JSON feed: https://verifymcp.io/servers/lithtrix-lithtrix/lithtrix-mcp.json
- HTML version of this page: https://verifymcp.io/servers/lithtrix-lithtrix/lithtrix-mcp