Knolo MCP server
io.github.HiveForensics-AI/knolo·v0.1.0·56 starsVerified, local-first retrieval over pinned Knolo Knowledge Images.
56 stars
Reviews
Write oneNobody has reviewed Knolo yet.
If you have run it, two minutes of your experience saves the next person an afternoon.
Knolo tools (4)
write = sends, deletes, buys or postsRead from the package source without running it. The installed server may list more.
knolo_getRead an authorized Knolo evidence object at the state root returned by search.
knolo_searchSearch approved, verified Knolo Knowledge Images.
knolo_statusShow the caller-visible, verified Knolo Knowledge Image mounts.
knolo_verifyVerify the local bytes and V5 roots for approved Knolo Knowledge Images.
Public scan report
scanner v0.1.10 · 2026-10-13 · same rubric, same numbers if you re-run it
- Code scan11 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 0 days ago15/15
- Maintainer identityregistry namespace matches repository owner; GitHub account older than a year9/10
How Knolo compares
Against every graded MCP server, from our own scans and uptime checks. Updated after each scan run.
- Safety score
- 94/100
- higher than 96% of 48,255 servers
- Tools
- 4
- the typical server has 7
- Tools that change things
- 0%
- typical: 0%. Fewer write tools means less an agent can break
- GitHub stars
- 56
- more than 95% of 28,688 servers
What its tools let an agent do: 4 read
Install Knolo in Claude Code, Cursor or VS Code
Runs npx -y @knolo/mcp on your machine. Read the scan report first; the gateway never runs local packages.
claude mcp add knolo -- npx -y @knolo/mcp
What the publisher says
From the Knolo repository's README, as published. We do not edit it. Read it on GitHub
Knolo
The verifiable knowledge layer for trustworthy AI
Knolo turns organizational knowledge into portable, deterministic, and cryptographically verifiable runtime artifacts.
AI products are becoming easier to build. The hard problem is making their knowledge dependable: traceable to evidence, reproducible across environments, safe to move, and defensible under review. Knolo is infrastructure for that problem.
Knowledge should be an asset you can inspect, verify, migrate, and run—not opaque context trapped inside an application.
V6 · KAR · V5 Knowledge Images · V4 compatible · Local-first · Deterministic · Verifiable
Current release
This tree is Knolo 6.1.0. V6 adds KAR: deterministic retrieval of a minimum evidence set from a V5 Knowledge Image and a Committed Evidence Graph. 6.1.0 adds verifiable composition: offline citations of images, packs, graphs, and bounded excerpts, plus attestations. Lexical retrieval, V5 images, and V4 packs stay in place.
import {
createKarSession,
evaluateKar,
verifyKar,
explainKarResult,
createKarDossier,
createKarCoverage,
} from '@knolo/core/kar';The root @knolo/core entry does not load KAR. @knolo/core/experimental/kar remains a compatibility entry for this cycle. SATISFIED means the declared evidence requirements were met. It does not mean a claim is proven. UNSATISFIEDEVIDENCEREQUIREMENTS means those requirements were not met. It does not mean the claim is false.
The npm packages in this repository are 6.1.0. @knolo/cli depends on @knolo/core ^6.1.0. The other packages that depend on @knolo/core stay at ^6.0.0. Publishing that version, and moving the npm latest dist-tag, is a separate step. @knolo/reflex stays 0.2.0. @knolo/evidence-gate stays 0.1.0. Rust, Python, and the ICP canister stay 5.5.1 and do not implement KAR or composition. The bundled contracts, policy, and operations Domain Packs are review-required. The local tag v6.0.0 stays on the 6.0.0 commit.
Start with the KAR guide, the composition guide, the 6.1.0 release notes, examples/kar-v6, examples/kar-coverage, and examples/composition-v1.
The opportunity
The next generation of AI products will compete on the quality and trustworthiness of their knowledge layer. Models may change quickly; durable value accumulates in the evidence, policies, retrieval behavior, runtime state, and operational history surrounding them.
Knolo provides a neutral substrate for that layer:
- Portable knowledge — package a knowledge base as a self-contained Knowledge Image rather than a proprietary database export.
- Verifiable state — every V5 image has deterministic encodings, domain-separated SHA-256 roots, bounded sections, and a commit history.
- Traceable answers — preserve source, chunk, claim, citation, and evidence identity through retrieval and agent execution.
- Reproducible behavior — use deterministic query plans, receipts, migration records, and runtime diagnostics to make results inspectable.
- Composable infrastructure — keep storage, verification, retrieval, policy, and agent execution separate so products can adopt only what they need.
This is the strategic thesis behind Knolo: a trusted knowledge runtime can become shared infrastructure beneath many AI applications, agents, and enterprise workflows.
Why Knolo
Shortened. The full README is on GitHub.
Nothing above is checked by us. What we check is on the safety report.
Knolo: common questions
- Is Knolo MCP server safe?
- Yes, by our scan: it is graded A (94/100). Read the Knolo safety report
- How do I install Knolo?
- It runs on your machine. Copy the Claude Code, Cursor, VS Code or Claude Desktop config from the install section.
- Does Knolo need an API key?
- No secret keys are declared. It reads 1 setting from the environment.
- Is Knolo maintained?
- The last commit was 22 days ago (2026-10-13). The latest release is v0.1.0.
- How does Knolo compare with other MCP servers?
- safety score 94/100 (higher than 96% of 48,255 servers); tools 4 (the typical server has 7); tools that change things 0% (typical: 0%. Fewer write tools means less an agent can break). Full comparison.