Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

Lithtrix — Identity, Memory & Trust for AI Agents

NPM · LITHTRIX-MCP · SCANNED SEP 24

Identity, memory, trust, and swarm primitives for AI agents. MIRC base always free.

Available components

0 this week 80 Trust /100
Trust breakdown (7 categories)

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. How we score → Why this is hard to score →

Supply Chain Security98
  • No malware found by supply-chain analysis.Pass
  • No known CVEs affecting this package version or its production dependencies.Pass
  • No install/post-install scripts declared.Pass
  • 31 of 96 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency48
  • Source repository is publicly reachable at the declared URL. View diagnostics → Pass
  • Provenance check failed: no build-provenance attestation is published. See how to fix → View diagnostics → Fail
  • Clear OSI-approved license (MIT).Pass
  • Actively maintained (last published 4 days ago).Pass
  • Publishes a security disclosure policy (SECURITY.md).Pass
Schema Quality & AI Usability76
  • AI-judged instruction clarity (good).Pass
  • Tool/resource definitions use about 4000 tokens (~93/item across 43 items; 43 tools + 0 resources), lean.Pass
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management83
  • Stability observed for 25 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage93
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 79% of tool parameters carry a description.Partial
Tool Safety75
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • 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. See how to fix → Fail
  • An AI judge read all 43 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
  • Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Install

How do I install the Lithtrix — Identity, Memory & Trust for AI Agents MCP server?

Lithtrix — Identity, Memory & Trust for AI Agents 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.

npm · lithtrix-mcp

# add to Claude Code
claude mcp add ai-lithtrix-lithtrix-mcp -- npx -y lithtrix-mcp
// .cursor/mcp.json
{
  "mcpServers": {
    "ai-lithtrix-lithtrix-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "lithtrix-mcp"
      ]
    }
  }
}
// .vscode/mcp.json
{
  "servers": {
    "ai-lithtrix-lithtrix-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "lithtrix-mcp"
      ]
    }
  }
}
# add to Codex CLI
codex mcp add ai-lithtrix-lithtrix-mcp -- npx -y lithtrix-mcp
// opencode.json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "ai-lithtrix-lithtrix-mcp": {
      "type": "local",
      "command": [
        "npx",
        "-y",
        "lithtrix-mcp"
      ],
      "enabled": true
    }
  }
}
# add to OpenClaw
openclaw mcp add ai-lithtrix-lithtrix-mcp --command npx --arg -y --arg lithtrix-mcp
# ~/.hermes/config.yaml
mcp_servers:
  ai-lithtrix-lithtrix-mcp:
    command: "npx"
    args: ["-y", "lithtrix-mcp"]
// ~/.netclaw/config/netclaw.json
{
  "McpServers": {
    "ai-lithtrix-lithtrix-mcp": {
      "Transport": "stdio",
      "Command": "npx",
      "Arguments": [
        "-y",
        "lithtrix-mcp"
      ]
    }
  }
}
# add to Vellum
assistant mcp add ai-lithtrix-lithtrix-mcp -t stdio -c npx -a -y lithtrix-mcp
// mcp.json
{
  "mcpServers": {
    "ai-lithtrix-lithtrix-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "lithtrix-mcp"
      ]
    }
  }
}
Changelog

Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.

  • 24 Sept 26 −3
    • Stability: pass → 0.83 functional
  • 23 Sept 26 +1
    • Stability: 0.97 → pass security
  • 21 Sept 26 +1

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

  • 19 Sept 26 +1

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

  • 17 Sept 26 −3
    • Stability: pass → 0.80 functional
  • 16 Sept 26 +1
    • Stability: 0.97 → pass security
  • 14 Sept 26 +1

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

  • 12 Sept 26 +1

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

Diagnostics

Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.

Captured 24 Sept 2026 · Analysed npm/lithtrix-mcp@0.20.2

Provenance No attestation

The registry publishes no build provenance for this version, so there is nothing to verify.

Result No attestation
Ecosystem npm

Background: How many MCP packages publish verified provenance →

Dependencies 96 packages
Packages resolved 96
Stale 31
Tree resolution Complete

Background: SBOMs and build attestations, explained →

MCP tools · 43 exposed · ~4,000 tokens

The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →

Tool Tokens
lithtrix_agent_vouch ~55

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

NameTypeReqDescription
skillstringyes–
target_agent_idstringyes–

No output schema declared.

No examples provided.

lithtrix_agent_vouch_revoke ~57

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

NameTypeReqDescription
skillstringyes–
target_agent_idstringyes–

No output schema declared.

No examples provided.

lithtrix_blob_delete ~56

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

NameTypeReqDescription
blob_idstringyesContent-addressed blob id (b_ + 16 hex chars)

No output schema declared.

No examples provided.

lithtrix_blob_download ~65

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

NameTypeReqDescription
blob_idstringyesContent-addressed blob id (b_ + 16 hex chars)

No output schema declared.

No examples provided.

lithtrix_blob_list ~67

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

NameTypeReqDescription
pageinteger–Page (default 1)
per_pageinteger–Page size (1–100, default 50)

No output schema declared.

No examples provided.

lithtrix_blob_meta ~60

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

NameTypeReqDescription
blob_idstringyesContent-addressed blob id (b_ + 16 hex chars)

No output schema declared.

No examples provided.

lithtrix_blob_parse ~108

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

NameTypeReqDescription
asyncboolean–When true, calls ?async=true (async parse + poll)
blob_idstringyesContent-addressed blob id (b_ + 16 hex chars)
callback_urlstring–HTTPS callback for async completion (public host)

No output schema declared.

No examples provided.

lithtrix_blob_parse_status ~73

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

NameTypeReqDescription
blob_idstringyesContent-addressed blob id (b_ + 16 hex chars)
parse_idstringyesParse operation UUID

No output schema declared.

No examples provided.

lithtrix_blob_search ~76

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

NameTypeReqDescription
limitinteger–Max hits (1–20)
qstringyesNatural-language query
thresholdnumber–Minimum similarity (0–1)

No output schema declared.

No examples provided.

lithtrix_blob_signed_url ~104

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.

NameTypeReqDescription
blob_idstringyesContent-addressed blob id (b_ + 16 hex chars)
expires_ininteger–TTL seconds (min 60; max from server). Omit for API default.

No output schema declared.

No examples provided.

lithtrix_blob_upload ~128

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.

NameTypeReqDescription
content_base64stringyesStandard base64-encoded file bytes (no data: URL prefix)
content_typestringyesMIME type sent as Content-Type (e.g. application/pdf)
filenamestring–Optional display filename (sent as filename query on the request)

No output schema declared.

No examples provided.

lithtrix_browse ~119

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.

NameTypeReqDescription
modestring–Fetch mode: "static" (HTTP GET) or "dynamic" (rendered HTML)
urlstringyesPublic http(s) URL to fetch

No output schema declared.

No examples provided.

lithtrix_commons_read ~121

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.

NameTypeReqDescription
pageinteger–Page number (1-based, default 1)
per_pageinteger–Page size (1–100, default 20)

No output schema declared.

No examples provided.

lithtrix_delegate ~192

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

NameTypeReqDescription
assumptionsobject–Assumptions map stored in contract.
conflict_policystring–Only accepted value: "last_writer_wins_audit".
parent_agent_idstring–Delegating parent UUID; inferred from GET /v1/me when omitted.
read_setarray–Declarative read scope labels.
recipient_agent_idstringyesRecipient agent UUID — typically child_agent_id from lithtrix_spawn.
task_id––Task UUID correlating delegation + trace; auto-generated when omitted.
ttl_secondsinteger–Contract TTL in seconds.
verifier_obligations–––
version_refsarray–Optional version pin references.
write_setarray–Declarative write scope labels (authoritative).

No output schema declared.

No examples provided.

lithtrix_feedback ~152

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.

NameTypeReqDescription
notestring–Optional context, max 500 characters — no secrets or PII
ref_idstringyesOpaque id (e.g. search UUID from _lithtrix.search_id, memory key, blob_id)
ref_typestringyesKind of reference
signalstringyesFeedback signal

No output schema declared.

No examples provided.

lithtrix_feedback_interaction ~112

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

NameTypeReqDescription
interaction_refstring–Optional opaque reference id
interaction_ref_typestring–Optional context type
notestring–Optional note — no secrets or PII
signalstringyesInteraction signal
subject_agent_idstringyesAgent being rated

No output schema declared.

No examples provided.

lithtrix_keys_create_scoped ~50

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

NameTypeReqDescription
scopestringyesEdge-enforced capability scope

No output schema declared.

No examples provided.

lithtrix_keys_list ~40

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

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

lithtrix_keys_revoke ~50

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

NameTypeReqDescription
key_idstringyesSub-key UUID from lithtrix_keys_list

No output schema declared.

No examples provided.

lithtrix_keys_rotate ~76

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

NameTypeReqDescription
grace_hoursinteger–Grace window for superseded key (hours)
key_idstringyesSub-key UUID from lithtrix_keys_list

No output schema declared.

No examples provided.

lithtrix_memory_context ~79

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

NameTypeReqDescription
importancestring–Optional importance tier (default normal on API if omitted)
limitinteger–Max memories to return (1–50, default 10)

No output schema declared.

No examples provided.

lithtrix_memory_get ~63

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

NameTypeReqDescription
keystringyesMemory key (1–128 chars: letters, digits, hyphen, underscore, dot, colon)

No output schema declared.

No examples provided.

lithtrix_memory_search ~114

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.

NameTypeReqDescription
importancestring–Optional importance tier (default normal on API if omitted)
limitinteger–Max results (1–20, default 5)
qstringyesNatural-language search query
thresholdnumber–Minimum similarity 0–1 (default 0.7 on API)

No output schema declared.

No examples provided.

lithtrix_memory_set ~166

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

NameTypeReqDescription
confidencenumber–Optional confidence 0–1 (default 1.0 on API)
importancestring–Optional importance tier (default normal on API if omitted)
keystringyesMemory key (1–128 chars: letters, digits, hyphen, underscore, dot, colon)
sourcestring–Optional provenance label (e.g. tool name)
ttlinteger–Optional positive TTL in seconds
value––JSON-serializable value (object, array, string, number, boolean, etc.)

No output schema declared.

No examples provided.

lithtrix_passport_auth_challenge ~41

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

NameTypeReqDescription
agent_idstringyes–

No output schema declared.

No examples provided.

lithtrix_passport_auth_verify ~56

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

NameTypeReqDescription
agent_idstringyes–
challenge_id–yes–
signaturestringyes–

No output schema declared.

No examples provided.

lithtrix_passport_derive ~55

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

NameTypeReqDescription
agent_idstringyes–

No output schema declared.

No examples provided.

lithtrix_passport_ephemeral ~50

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

NameTypeReqDescription
agent_idstringyes–

No output schema declared.

No examples provided.

lithtrix_passport_get ~75

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

NameTypeReqDescription
agent_idstringyes–

No output schema declared.

No examples provided.

lithtrix_passport_revoke ~34

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

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

lithtrix_passport_rotate ~45

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

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

lithtrix_passport_set_capabilities ~50

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

NameTypeReqDescription
capabilitiesobjectyes–

No output schema declared.

No examples provided.

lithtrix_passport_set_description ~100

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

NameTypeReqDescription
bio–––
listedboolean––
reputation_sub_signal_visibilitystring––
skillsarray––

No output schema declared.

No examples provided.

lithtrix_passport_sponsor ~56

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

NameTypeReqDescription
sponsor_idstringyes–
ward_id–yes–

No output schema declared.

No examples provided.

lithtrix_passport_sponsor_revoke ~60

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

NameTypeReqDescription
sponsor_idstringyes–
ward_id–yes–

No output schema declared.

No examples provided.

lithtrix_passport_stake ~45

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

NameTypeReqDescription
tierstringyes–

No output schema declared.

No examples provided.

lithtrix_passport_unstake ~37

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

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

lithtrix_register ~574

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). Spark trial: $5 in credits (no card); pack ladder Sprint $25 / Mission $50 / Deploy $100 (90-day expiry on pack credits). Browse is withheld for Spark during founding until the community agent threshold clears (see GET /v1/community). 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). 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.

NameTypeReqDescription
agent_namestringyesUnique 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_termsbooleanyesMust be true — you agree to https://lithtrix.ai/terms (required by POST /v1/register)
owner_identifierstringyesYour email address, URL, or a stable identifier for the agent owner
owner_typestring–Optional. Classifies owner_identifier. Defaults to email when omitted. Values: email | oauth | did | wallet | uuid | agent.
referral_agentstring–Optional referring agent UUID — same value as their referral_code from GET /v1/me
server_generated_passportboolean–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…

No output schema declared.

No examples provided.

lithtrix_reputation_dispute ~66

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

NameTypeReqDescription
reasonstringyesWhy this event should be reviewed
reputation_event_idstringyesUUID of the reputation event

No output schema declared.

No examples provided.

lithtrix_search ~136

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.

NameTypeReqDescription
num_resultsinteger–Number of results to return (1–20, default 10)
qstringyesThe search query (1–500 characters)

No output schema declared.

No examples provided.

lithtrix_spawn ~147

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

NameTypeReqDescription
agent_namestring–Optional child display name; server generates swarm-{uuid8} if omitted.
issue_ephemeral_passportboolean–When true, mint ephemeral passport for the child agent.
parent_agent_idstring–Your agent UUID (from lithtrix_register or GET /v1/me). Inferred from /v1/me when omitted.
scopestring–Scoped sub-key permission for the child.
ttl_secondsinteger–Optional key expiry hint stored on the key row.

No output schema declared.

No examples provided.

lithtrix_trace_append ~144

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

NameTypeReqDescription
advisory_claims––Advisory scope claims; overreach vs contract write_set is recorded.
decisionstringyesAudit decision label e.g. "allowed".
delegation_idstring–Delegation UUID from lithtrix_delegate.
evidence_json––Optional evidence blob.
outcome––Outcome label after action.
proposed_actionstringyesAudit label e.g. "memory.put".
scope_json––Optional scope snapshot.
task_idstringyesTask UUID from lithtrix_delegate.

No output schema declared.

No examples provided.

lithtrix_trace_get ~46

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

NameTypeReqDescription
task_idstringyesTask UUID from lithtrix_delegate.

No output schema declared.

No examples provided.

Common questions

What is the Lithtrix — Identity, Memory & Trust for AI Agents MCP server?

Lithtrix — Identity, Memory & Trust for AI Agents is an MCP server listed in the public MCP registry as ai.lithtrix/lithtrix-mcp. Identity, memory, trust, and swarm primitives for AI agents. MIRC base always free. This page covers its npm package (lithtrix-mcp).

Is the Lithtrix — Identity, Memory & Trust for AI Agents MCP server safe to use?

Lithtrix — Identity, Memory & Trust for AI Agents scores 80 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 24 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 Lithtrix — Identity, Memory & Trust for AI Agents MCP server expose?

Lithtrix — Identity, Memory & Trust for AI Agents exposes 43 tools: lithtrix_search, lithtrix_register, lithtrix_memory_set, lithtrix_memory_get, lithtrix_memory_search, and 38 more. Their descriptions and schemas cost roughly 4,000 tokens of context every time the server is loaded.

Is the Lithtrix — Identity, Memory & Trust for AI Agents MCP server still maintained?

Lithtrix — Identity, Memory & Trust for AI Agents is still listed as active in the MCP registry. We last reached this channel on 24 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 Lithtrix — Identity, Memory & Trust for AI Agents MCP server under?

Lithtrix — Identity, Memory & Trust for AI Agents declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.