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.

llmwiki

NPM · LLM-WIKI-COMPILER

Compile documents into a cited knowledge wiki. Retrieve evidence, query, and review via local MCP.

Available components

+7 this week 88 Trust /100

Last scanned (41 minutes ago)

Scores higher than 90% of npm servers

Category Memory and Knowledge

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 Security99
  • 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
  • 59 of 218 dependencies flagged as unhealthy (1 deprecated). View diagnostics → Partial
Provenance & Transparency97
  • Source repository is publicly reachable at the declared URL. View diagnostics → Pass
  • Cryptographically verified build provenance (signed, bound to atomicstrata/llm-wiki-compiler). View diagnostics → Pass
  • Clear OSI-approved license (MIT).Pass
  • Actively maintained (last published 1 days ago).Pass
  • Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability88
  • 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
  • AI-judged instruction clarity (excellent).Pass
  • Tool/resource definitions use about 1864 tokens (~88/item across 21 items; 16 tools + 5 resources), lean.Pass
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management50
  • Stability observed for 15 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 100% of tool parameters carry a description.Pass
Tool Safety75
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • 0 of 2 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation; "run_eval" implies "eval" 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 18 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
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.

  • 16 Oct 26 +1

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

  • 14 Oct 26 +6
    • Stability: unverified → 0.40 ▲ functional
  • 13 Oct 26 0
    • Security disclosure: unverified → fail ▼ functional
  • 11 Oct 26 0
    • Security disclosure: fail → unverified ▼ functional
  • 3 Oct 26 +20
    • Malware scan: unverified → pass ▲ security
    • Source repository: unverified → pass ▲ security
  • 2 Oct 26 61

    First indexed and scored.

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 17 Oct 2026 · Analysed npm/llm-wiki-compiler@1.4.1

Provenance Verified

A signed build attestation was found and verified, binding this exact artifact to the source repository it claims to come from.

Result Verified
Ecosystem npm
Reason Verified
Discovered via Registry attestation endpoint
Source repo atomicstrata/llm-wiki-compiler
Certificate issuer https://token.actions.githubusercontent.com
Certificate SAN https://github.com/atomicstrata/llm-wiki-compiler/.github/workflows/publish.yml@refs/heads/main
Rekor log index 3047528513
Predicate type SLSA build provenance https://slsa.dev/provenance/v1
Subject digest sha512:c227b99d647020b43e66a71ae602e0b49c17b88c4d0a9914d298fde2d6151ba3660b500faef2662a1613bf443aafdf67038b3c35516014d2d33831632

Background: How many MCP packages publish verified provenance →

Dependencies 218 packages
Packages resolved 218
Deprecated 1
Stale 51
No linked repository 8
Tree resolution Complete

Background: SBOMs and build attestations, explained →

MCP tools · 16 exposed · ~1,547 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
compile_wiki ~59

Update the persistent knowledge wiki after source documents change. Writes wiki pages or review candidates according to project policy. Extract concepts from new/changed sources, generate wiki pages, resolve interlinks, and rebuild the index. Requires an LLM provider with credentials.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

describe_workflow_action ~65

Describe one declared workflow action, including its EFFECTIVE permission per surface = min(profile request, local grant, surface cap). The `mcp` surface is hard-capped at staged-write. Read-only.

NameTypeReqDescription
actionIdstringyesThe declared action id to describe.

No output schema declared.

No examples provided.

export_okf ~64

Export the wiki as an Open Knowledge Format (OKF) v0.1 bundle. `out` defaults to dist/exports/okf and must stay inside the project.

NameTypeReqDescription
outstring–Output dir for the bundle (must resolve inside the project root)

No output schema declared.

No examples provided.

get_context_pack ~269

Retrieve bounded evidence from this project knowledge base for research, document questions, or agent task context. Use it when you will reason over the evidence yourself. Build a token-budgeted pack for `prompt` over the compiled wiki: primary pages, semantic chunks, graph neighbors, citations, warnings, and suggested next actions. Returns the same v1 JSON envelope as `llmwiki context --json`. Read-only; no provider credentials required. Use this to PREPARE evidence; use `query_wiki` to GENERATE a grounded natural-language answer.

NameTypeReqDescription
budgetnumber–Approximate output token budget (default 8000).
depthnumber–Graph neighborhood depth, 0..2 (default 1, 0 disables expansion).
includeSourcesboolean–Materialize `primary[].sourceWindows` from claim-level citations (reads files under `sources/` only; path-confined).
omitRootboolean–Emit `project.root` as null instead of the absolute path.
promptstringyesFree-text task or topic to assemble context for.
topChunksnumber–Max semantic chunks to surface (default 8, max 50).
topPagesnumber–Max primary pages (default 5, max 20).

No output schema declared.

No examples provided.

import_okf ~77

Import an OKF bundle from a path INSIDE the project as review candidates. Always staging-only — imported knowledge requires human review/approval before it enters the wiki. Use dryRun to preview.

NameTypeReqDescription
dirstringyesBundle directory (must resolve inside the project root)
dryRunboolean–Preview only — stage nothing

No output schema declared.

No examples provided.

ingest_source ~78

Add a user-requested document to this knowledge base: fetch a trusted URL or copy a trusted local file into sources/. Writes project files. Returns the saved filename, character count, and whether content was truncated to fit the size limit.

NameTypeReqDescription
sourcestringyesURL (http/https) or absolute path to a .md/.txt file

No output schema declared.

No examples provided.

lint_wiki ~40

Run rule-based quality checks (broken wikilinks, orphans, duplicates, empty pages, broken citations). Returns structured diagnostics. No LLM call.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

list_workflow_actions ~39

List the workflow actions declared by the active profile (id, label, workflow, operation). Read-only; takes no lock and mutates nothing.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

query_wiki ~146

Get a model-generated answer grounded in this knowledge base. For source evidence to reason over yourself, use get_context_pack instead. Selects relevant pages, loads them, and returns a grounded answer with citations. Set save=true to request publication as a wiki page; citation or profile refusals return the answer with publicationRefusal and no saved slug. Set debug=true to include the selected chunks and their scores. Requires an LLM provider.

NameTypeReqDescription
debugboolean–Include retrieval debug info (selected chunks/pages + scores).
questionstringyesThe natural-language question to answer.
saveboolean–Request a wiki/queries/ page; publication requires fresh citation validation.

No output schema declared.

No examples provided.

read_page ~52

Read a single wiki page by slug. Searches concepts/ first, then queries/. Returns the parsed frontmatter and body. No LLM call required.

NameTypeReqDescription
slugstringyesPage slug, without .md extension.

No output schema declared.

No examples provided.

run_eval ~131

Run the wiki quality eval harness. fast suite checks health and citation coverage without LLM calls. full suite also LLM-judges a sample of citations (requires an LLM provider). Set record: true to append results to eval history (default false — read-only).

NameTypeReqDescription
recordboolean–Append results to eval history (default false; set true to persist a checkpoint)
sampleSizeinteger–Citations to sample for citation support (full suite only, default 20)
suitestring–fast=no LLM calls, full=includes citation support (requires LLM provider)

No output schema declared.

No examples provided.

run_workflow_action ~94

Execute a declared workflow action. MCP actions are HARD-CAPPED at staged-write: they CANNOT perform trusted writes or satisfy human gates, regardless of what a profile or local config requests. A denied, unknown, or invalid action returns a clean error result rather than crashing.

NameTypeReqDescription
actionIdstringyesThe declared action id to execute.
inputsobject–The action's inputs, validated against its schema.

No output schema declared.

No examples provided.

search_pages ~57

Select pages relevant to a question and return their full content. Uses semantic embeddings when available, falling back to LLM-based selection over the wiki index. Requires an LLM provider.

NameTypeReqDescription
questionstringyesThe query used to rank pages.

No output schema declared.

No examples provided.

verify_artifact ~116

Verify a hash-pinned artifact ref against the active profile's declared artifact types. Returns manifest metadata (artifactType, slug, sha256, bytes, contentKind, writtenAt) plus a health verdict — NEVER the artifact body. Read-only; no write or store-wide list tool is exposed over MCP.

NameTypeReqDescription
artifactTypestringyesThe profile-declared artifact type.
sha256stringyesThe 64-character lowercase-hex sha256 digest to verify against.
slugstringyesThe artifact's slug.

No output schema declared.

No examples provided.

wiki_status ~170

Start here to inspect this knowledge base before retrieval or updating it. No provider credentials required. Summarize page count, source count, last compile time, pending source changes, and freshness-derived page health. stalePages lists concept slugs whose source changed or partially disappeared since last compile. orphanedPages lists concept slugs whose every owning source was deleted OR that are frontmatter-flagged orphaned (superset of prior behavior). stateStatus reports state.json readability (ok | missing | corrupt) so corrupt state is never silent. Each list (stalePages, orphanedPages, pendingChanges) is capped at 100 entries for response size; the corresponding *Count fields (staleCount, orphanedCount, pendingChangesCount) give the true totals. Read-only — never modifies the workspace.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

workflow_run_status ~90

Report the status of one workflow run (by runId) or of all runs, classified against the active profile (current / historical / needs-adaptation / blocked-by-config). Read-only and fail-visible: an unavailable store surfaces a problem row, never an empty result. Takes no lock and mutates nothing.

NameTypeReqDescription
runIdstring–A run id to report on; omit for all runs.

No output schema declared.

No examples provided.

Install

How do I install the llmwiki MCP server?

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

npm · llm-wiki-compiler

# add to Claude Code
claude mcp add atomicstrata-llmwiki -- npx -y llm-wiki-compiler
Common questions

What is the llmwiki MCP server?

llmwiki is an MCP server listed in the public MCP registry as io.github.atomicstrata/llmwiki. Compile documents into a cited knowledge wiki. Retrieve evidence, query, and review via local MCP. This page covers its npm package (llm-wiki-compiler).

Is the llmwiki MCP server safe to use?

llmwiki scores 88 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 17 October 2026. It declares no install or post-install scripts. Its build provenance is signed and verified. 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 llmwiki MCP server expose?

llmwiki exposes 16 tools: ingest_source, compile_wiki, query_wiki, search_pages, read_page, and 11 more. Their descriptions and schemas cost roughly 1,547 tokens of context every time the server is loaded.

Is the llmwiki MCP server still maintained?

llmwiki is still listed as active in the MCP registry. We last reached this channel on 17 October 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 llmwiki MCP server under?

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