LibKa
NPM · @LIBKA/MCP
Write accessible documents: one Markdown file to checked, signed web pages, PDFs, slides, Word.
Available components
Last scanned (1 hour ago)
Scores higher than 48% of npm servers
Category Documents and Files
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 Security97
- 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
- 90 of 208 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency100
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Cryptographically verified build provenance (signed, bound to aivigator-ai/open-libka-design-platform). View diagnostics → Pass
- Clear OSI-approved license (Apache-2.0).Pass
- Actively maintained (last published 4 days ago).Pass
- Publishes a security disclosure policy (SECURITY.md).Pass
Schema Quality & AI Usability49
- 25% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Partial
- AI-judged instruction clarity (fair).Partial
- Tool/resource definitions use about 499 tokens (~71/item across 7 items; 4 tools + 3 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management0
- Stability not yet verified: not enough scan history yet (needs a 30-day window).Unverified
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 Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 4 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 6 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
Unverified: 1 category
A category scored 0 because we could not verify it: a data source with nothing on this package, evidence we could not reach, or a check we could not run. We only credit what we can confirm.
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.
- 14 Oct 26 +27
- Injection markers: unverified → pass ▲ security
- First check of Judged manipulation: pass security
- Stability: Stability not yet verified: not enough scan history yet (needs a 30-day window). security
- Schema quality: unverified → 25 ▲ functional
- Tool coverage: unverified → 100 ▲ functional
- MCP protocol: unverified → pass ▲ functional
- First check of Schema quality: fail functional
- First check of Schema quality: fair functional
- First check of Destructive annotations: pass functional
- First check of Schema quality: pass functional
- First check of Tool coverage: 100 functional
- 13 Oct 26 +10
- Provenance: fail → pass ▲ security
- The attested source repository moved: aivigator-ai/open-libka-design-platform security
- Package version: 2.0.0 → 2.0.1 functional
- 12 Oct 26 39
First indexed and scored.
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 18 Oct 2026 · Analysed npm/@libka/mcp@2.0.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 | aivigator-ai/open-libka-design-platform |
| Certificate issuer | https://token.actions.githubusercontent.com |
| Certificate SAN | https://github.com/aivigator-ai/open-libka-design-platform/.github/workflows/publish.yml@refs/tags/v2.0.1 |
| Rekor log index | 3246087272 |
| Predicate type | SLSA build provenance https://slsa.dev/provenance/v1 |
| Subject digest | sha512:591e0b6d696b44c985fb79347ab7001cae866e2d9fadf44e450e186b515a98afae8ed7f38bdd02f2c00472047ff61ea8e6e66f387cef2e9e7910c4b43 |
Background: How many MCP packages publish verified provenance →
Dependencies 208 packages
| Packages resolved | 208 |
|---|---|
| Stale | 90 |
| Tree resolution | Complete |
Background: SBOMs and build attestations, explained →
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 →
libka_build Build a LibKa document ~208
Write the Markdown to a folder and build it: the outputs the document asks for in its front matter (outputs: web, pdf, deck, docx; default web and pdf), or the outputs given here. Guard checks every output (the pages in Chrome, the PDF with veraPDF, the Word file's structure); passing outputs are signed. Returns the files and every Guard finding to fix. Writes files on this machine.
| Name | Type | Req | Description |
|---|---|---|---|
| markdown | string | – | The document; or give path instead, not both |
| name | string | – | File name without extension when markdown is given (default: document) |
| outDir | string | – | Output folder (default: LIBKA_OUT, or ./libka-out) |
| outputs | array | – | Build these instead of the document's own outputs, e.g. ["web", "deck"] to check slide fit quickly |
| path | string | – | An existing .md file to build, only read (images are found next to it) |
No output schema declared.
No examples provided.
libka_check Check LibKa Markdown ~65
Parse LibKa Markdown without building: problems with line numbers (fix all of them), the outline, block counts and how many slides the deck will have. Fast; call it after every change.
| Name | Type | Req | Description |
|---|---|---|---|
| markdown | string | yes | The complete LibKa Markdown document, including front matter |
No output schema declared.
No examples provided.
libka_get_block Get one LibKa block ~66
Full definition of a block: example syntax, attributes, what the web page, PDF, slides and Word file do with it, accessibility rules, anti-patterns and its JSON schema.
| Name | Type | Req | Description |
|---|---|---|---|
| name | string | yes | Block name, such as steps, tabs, chart or ui |
No output schema declared.
No examples provided.
libka_list_blocks List LibKa blocks ~65
Every LibKa block with the content it fits ("use when"), grouped; plus content that has no block, and what to write for it instead.
| Name | Type | Req | Description |
|---|---|---|---|
| group | string | – | Only this group: text, how-to, explain, highlight, media, data, ui |
No output schema declared.
No examples provided.
How do I install the LibKa MCP server?
LibKa runs locally as an npm package, launched with npx -y @libka/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 · @libka/mcp
claude mcp add aivigator-ai-libka -- npx -y @libka/mcp
What is the LibKa MCP server?
LibKa is an MCP server listed in the public MCP registry as io.github.aivigator-ai/libka. Write accessible documents: one Markdown file to checked, signed web pages, PDFs, slides, Word. This page covers its npm package (@libka/mcp).
Is the LibKa MCP server safe to use?
LibKa scores 76 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 18 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 LibKa MCP server expose?
LibKa exposes 4 tools: libka_list_blocks, libka_get_block, libka_check, libka_build. Their descriptions and schemas cost roughly 404 tokens of context every time the server is loaded.
Is the LibKa MCP server still maintained?
LibKa is still listed as active in the MCP registry. We last reached this channel on 18 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 LibKa MCP server under?
LibKa declares the Apache-2.0 licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.