MCP.Market

livewiki MCP server

by eduardoabreu81·io.github.eduardoabreu81/livewiki·v0.3.4·1 stars

A repository wiki of Markdown pages anchored to real code: read, search, and verified writes.

A92/100grade A
What users say
No reviews yet
Be the first
Safety scan
A92/100

full report

Adoption
Growing

1 stars97 downloads/wk

Reviews

Write one

Nobody has reviewed livewiki yet.

If you have run it, two minutes of your experience saves the next person an afternoon.

livewiki tools (9, 1 write)

write = sends, deletes, buys or posts

Read from the package source without running it. The installed server may list more.

  • livewiki_debt

    Lists open documentation debt (changed/moved/deleted anchors), undocumented symbols, and overall wiki status. Equivalent to `livewiki status --json`.

  • livewiki_impact

    Blast radius for a symbol key (e.g. 'src/auth.ts#login'): direct and transitive callers found in the indexed call graph, plus which wiki pages document any of them. Only RESOLVED call edges are walked (an edge the indexer couldn't confidently attribute to one symbol is skipped, never guessed) — treat this as a best-effort signal, not exhaustive static analysis. Bounded by maxDepth/maxNodes; `trunc

  • livewiki_next_task

    Starts or resumes a full wiki bootstrap written by this MCP client. Returns the next prioritized Markdown task with its target path, complete closed symbol-key list, source file paths, and canonical format contract. No provider, model, or API credential is required.

  • livewiki_quickstart

    Returns livewiki/quickstart.md (the low-token entry point for navigating the wiki). Errors if the wiki isn't initialized yet — run `livewiki init` first.

  • livewiki_read

    Reads a wiki page by its relative path inside the repo (e.g. 'livewiki/auth.md'). Path must be inside the livewiki/ allowlist.

  • livewiki_renew_task_claim

    Extends the lease on a task claimed through livewiki_next_task. Pass the taskId and the claimId you were given. Returns the new leaseExpiresAt, or a stale_claim error when the lease already expired or another execution re-claimed the task.

  • livewiki_resolve_debt

    Explicitly accepts the current code/document alignment into the versioned baseline. Choose one wiki page and either specific anchored symbol keys or every anchor on that page. Local SQLite debt IDs are not accepted because they are disposable projections.

  • livewiki_search

    Full-text search over all wiki pages using SQLite FTS5. Returns up to N hits (default 20) with wiki path and a snippet around the match.

  • livewiki_write_docwrite action

    Writes or updates a wiki page. Path MUST be inside livewiki/ (allowlist). Content is validated via `verify` before being accepted — pages with broken anchors are rejected. Never include reasoning or <think> blocks in the content; verify rejects them. Pass the taskId returned by livewiki_next_task to validate against that task's full page contract and complete it atomically.

Public scan report

scanner v0.1.10 · 2026-10-16 · same rubric, same numbers if you re-run it

no findings
  • Code scan13 source files scanned25/25
  • –Live reliabilityno gateway calls yet and no remote to proben/a
  • –Tool poisoningtools not inspected (local package is not executed); not countedn/a
  • Auth qualitylocal package, no credentials required12/15
  • Maintenancelast push 24 days ago15/15
  • Maintainer identityregistry namespace matches repository owner; GitHub account older than a year8/10
Overall 92/100. Components that don't apply are left out of the denominator. Any critical finding is an F.RubricAppeal a findingJSON

How livewiki compares

Against every graded Web search MCP server, from our own scans and uptime checks. Updated after each scan run.

Safety score
92/100
higher than 90% of 3,471 Web search servers
Tools
9
the typical Web search server has 5
Tools that change things
11%
typical: 0%. Fewer write tools means less an agent can break
GitHub stars
1
more than 55% of 1,788 Web search servers
Downloads a week
97
more than 54% of 837 Web search servers with a package

What its tools let an agent do: 8 read · 1 change

Install livewiki in Claude Code, Cursor or VS Code

Runs npx -y @livewiki/mcp on your machine. Read the scan report first; the gateway never runs local packages.

claude mcp add livewiki -- npx -y @livewiki/mcp
Add to Cursor

What the publisher says

From the livewiki repository's README, as published. We do not edit it. Read it on GitHub

livewiki

Code-anchored documentation that knows when it is stale.

livewiki turns a repository into a Markdown wiki whose every code reference is anchored to a real indexed symbol. An LLM writes the prose; livewiki does the deterministic work — planning the pages, running structural anti-hallucination checks on what the model wrote, tracking which anchored symbols changed, and preserving your edits.

The wiki is exposed to any coding agent by @livewiki/mcp — an MCP (Model Context Protocol) server with eight tools for reading, searching, and safely writing the wiki.

livewiki view builds a self-contained offline site from the wiki — grouped sidebar, offline search, diagrams, and dark mode:

Example wiki generated by livewiki for MoneyPrinterTurbo-Plus, an external Python repository.

Why

Technical docs go stale the moment the code changes. livewiki makes that visible and cheap to fix instead of silent:

at a real indexed symbol. livewiki verify reads the wiki fresh from disk and fails on invented symbols, broken anchors, and signatures that no longer match — including references the LLM wrote seconds ago, without running index first, and without spending a token. Structural, not semantic; the section below draws the line.

  • Deterministic anti-hallucination checks. Every code reference must point

lw:manual blocks are preserved byte-for-byte.

  • Your edits win. Pages you mark owner: human are never rewritten, and

a GitHub Action can gate every merge on zero documentation debt, without spending tokens.

  • Debt is tracked, not discovered. livewiki status ranks what drifted;

agent you use, or run a fully automated batch.

  • Works where you already work. Bootstrap and maintain through the coding

What verify checks — and what it doesn't

The anti-hallucination layer is deterministic and structural. livewiki verify reads the wiki fresh from disk — so a page an LLM wrote seconds ago is checked without running index first — and fails on:

  • a cited symbol that does not exist in the code;
  • an anchor that broke because the symbol moved, was renamed, or was deleted;
  • a cited signature that no longer matches the indexed one;
  • an internal link that does not resolve;
  • a referenced artifact that is missing from disk;
  • frontmatter or page structure that violates the format contract.

That removes whole classes of fabricated content — the invented function, the API that never existed, the reference that quietly rotted — before a reader ever sees it, at zero token cost. Anything that fails is rejected and rolled back rather than merged.

It does not prove that a sentence is true. A plausible but wrong explanation of code that really does exist passes every check above, because every check above is about structure and identity, not meaning. Read "anti-hallucination" here as a layer that mechanically eliminates a large class of fabrication and tells you the moment code moves under the prose — not as a guarantee of factual accuracy. Reviewing the explanation itself is still your job.

Quick start

Requires Node.js 24 or newer.

1. Install

npm install -g @livewiki/cli

(npx @livewiki/cli works too, without installing globally.)

2. Initialize

From the root of the repository you want documented:

Shortened. The full README is on GitHub.

Nothing above is checked by us. What we check is on the safety report.

livewiki: common questions

Is livewiki MCP server safe?
Yes, by our scan: it is graded A (92/100). Read the livewiki safety report
How do I install livewiki?
It runs on your machine. Copy the Claude Code, Cursor, VS Code or Claude Desktop config from the install section.
Does livewiki need an API key?
Not as far as the registry entry and our scan can tell: no credentials are declared or required.
Is livewiki maintained?
The last commit was 45 days ago (2026-09-22). The latest release is v0.3.4.
What can I use instead of livewiki?
Servers from other publishers that do the same job: Exa Search MCP server, Zoteus MCP server and Search1API MCP server.
How does livewiki compare with other Web search MCP servers?
safety score 92/100 (higher than 90% of 3,471 Web search servers); tools 9 (the typical Web search server has 5); tools that change things 11% (typical: 0%. Fewer write tools means less an agent can break). Full comparison.

Alternatives to livewiki

Same job from other publishers: the closest match first, then the best rated.

  • Exa Search
    Search the live web and fetch clean content from source pages.
    A
  • Zoteus
    Zotero MCP server for Claude and ChatGPT: search, citations, safe writes, PDF passages and pages.
    A
  • Search1API
    Multi-engine web and platform search, news, Google Maps places, page reading, sitemaps, and trends.
    A
  • Free Search
    No-API-key web search, page fetching and document reading across many engines. Local-first.
    B
  • FrankenSurf
    Read any web page and search the web: 28 tools, cheapest first, every page checked.
    A