io.github.sfrangulov/minirag-mcp
PYPI · MINIRAG-MCP · SCANNED AUG 19
Local-first RAG MCP server: hybrid search over a folder of your own documents
Available components
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 →
Supply Chain Security99
- No malware found by supply-chain analysis.Pass
- No known CVEs affecting this package version or its production dependencies.Pass
- Runs hatchling.build at install time, a recognised native-build step with no shell scripting around it. View diagnostics → Pass
- 14 of 83 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency32
- 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
- License check failed: no license is declared. See how to fix → Fail
- Actively maintained (last published 9 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability67
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 2067 tokens (~187/item across 11 items; 11 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management33
- Stability observed for 10 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage71
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 0% of tool parameters carry a description.Fail
- Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Add this component to your MCP client. Where a client-specific snippet is available, pick your client below and copy it straight into your config; otherwise use the connection detail shown.
pypi · minirag-mcp
claude mcp add sfrangulov-minirag-mcp -- uvx minirag-mcp
codex mcp add sfrangulov-minirag-mcp -- uvx minirag-mcp
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"sfrangulov-minirag-mcp": {
"type": "local",
"command": [
"uvx",
"minirag-mcp"
],
"enabled": true
}
}
} openclaw mcp add sfrangulov-minirag-mcp --command uvx --arg minirag-mcp
mcp_servers:
sfrangulov-minirag-mcp:
command: "uvx"
args: ["minirag-mcp"] {
"mcpServers": {
"sfrangulov-minirag-mcp": {
"command": "uvx",
"args": [
"minirag-mcp"
]
}
}
} 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.
- 19 Aug 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 30 to 33. That category is still filling its 30-day observation window: 9 days of observed history at the previous scan, 10 at this one. The score rises as the window fills, whether or not the server changes.
- 17 Aug 26 +4
- Security disclosure: unverified → fail ▼ functional
- Stability: unverified → 0.27 ▲ functional
- 16 Aug 26 0
- Security disclosure: fail → unverified ▼ functional
- 11 Aug 26 +1
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 9 Aug 26 61
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 19 Aug 2026 · Analysed pypi/minirag-mcp@0.6.0
Provenance No attestation
The registry publishes no build provenance for this version, so there is nothing to verify.
| Result | No attestation |
|---|---|
| Ecosystem | pypi |
Install scripts 1 script
| Hook | Tier | Command |
|---|---|---|
| build_backend | allowlisted | hatchling.build |
Dependencies 83 packages
| Packages resolved | 83 |
|---|---|
| Stale | 13 |
| No linked repository | 1 |
| Tree resolution | Complete |
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.
delete_file ~88
Delete an indexed file, data item, or url item from the index. Provide exactly one of filePath (absolute path inside a document root) or source (the id of a data/url item). This only removes the index entry — a file left in place under a document root is re-ingested by a later sync_start.
| Name | Type | Req | Description |
|---|---|---|---|
| filePath | – | – | – |
| source | – | – | – |
Structured output declared, but exposes no named fields.
No examples provided.
ingest_data ~108
Ingest text/markdown/html content the client holds, under a source id you choose. format is one of "text", "markdown", or "html" (default "text"). source is a stable identifier you pick, not a filesystem path — re-using it replaces the previously ingested content for that id, so reuse the same source to update an item.
| Name | Type | Req | Description |
|---|---|---|---|
| data | string | yes | – |
| format | string | – | – |
| source | string | yes | – |
| title | – | – | – |
Structured output declared, but exposes no named fields.
No examples provided.
ingest_file ~69
Ingest or re-ingest one file, replacing any content already indexed for it. filePath must be an absolute path inside a configured document root. Re-ingesting an already-indexed file discards its old chunks and replaces them with freshly parsed ones.
| Name | Type | Req | Description |
|---|---|---|---|
| filePath | string | yes | – |
Structured output declared, but exposes no named fields.
No examples provided.
ingest_url ~135
Fetch an http(s) URL, convert it to Markdown, and index it. Only http and https schemes are accepted, and the host must not be a private or local address (loopback, link-local, private, reserved) — set ALLOW_PRIVATE_URLS=1 to lift that. This is the one tool that reaches the network — every other tool works purely against local files and the local index. source defaults to the URL itself; pass one to control the index key or to update a previously ingested URL.
| Name | Type | Req | Description |
|---|---|---|---|
| source | – | – | – |
| title | – | – | – |
| url | string | yes | – |
Structured output declared, but exposes no named fields.
No examples provided.
list_files ~221
List files found on disk under the document roots, plus indexed data/url sources. Each disk file is reported with a state: "ingested" (index matches disk), "stale" (changed on disk since it was indexed), "stale_scheme" (unchanged on disk, but indexed under an older chunking scheme, so its vectors are not comparable with current ones), "not_ingested" (never indexed), or "unreadable" (indexed and still on disk, but of a type this installation cannot read because an optional extra is absent — images need [ocr]). Everything but "ingested" and "unreadable" needs a sync_start; an "unreadable" source is kept as indexed and no sync can refresh it here. "stale_scheme" is the per-source view of what status reports as staleChunkCount. Data and url sources have no disk state to compare against, so they are "ingested" or "stale_scheme".
| Name | Type | Req | Description |
|---|---|---|---|
| scope | – | – | – |
Structured output declared, but exposes no named fields.
No examples provided.
query_documents ~331
Hybrid search: semantic similarity plus a keyword boost for exact terms. Returns `results` — ranked chunks with text, source, title, chunkIndex, score and parentId — `sources`, the distinct sources in rank order each with a hits count and a `displayPath` to show the user (`source` stays absolute and is what the other tools take), and `parents`, a map from parentId to section text. Use `sources` to answer "which documents cover this topic" without inspecting individual chunks. `text` is the passage that matched and that `score` describes. `parentId` names the section it sits in — a transcript time window, a heading section, a slide, a table. Look it up in `parents` to read the whole section when the match alone is too small to act on. A chunk indexed before parent sections existed has parentId null and no entry; re-sync to fill it in. topK must be at least 1 and is capped at 100; a larger value is silently clamped to the cap rather than rejected. Cite what you take, so the user can verify it, in whatever language you answer: end with a Sources list, one line per document you actually used, each line just that document's `displayPath` copied verbatim — no [n] markers, nothing else on the line. Plain text, never a markdown link or file://.
| Name | Type | Req | Description |
|---|---|---|---|
| query | string | yes | – |
| scope | – | – | – |
| topK | integer | – | – |
Structured output declared, but exposes no named fields.
No examples provided.
read_chunk_neighbors ~106
Read the chunks immediately before and after a search result, for context. Provide exactly one of filePath (absolute path inside a document root) or source (the id of a data/url item). before/after control how many chunks to include on each side of chunkIndex (both default to 1).
| Name | Type | Req | Description |
|---|---|---|---|
| after | integer | – | – |
| before | integer | – | – |
| chunkIndex | integer | yes | – |
| filePath | – | – | – |
| source | – | – | – |
Structured output declared, but exposes no named fields.
No examples provided.
read_file ~142
Read a source's entire indexed content as Markdown. The document is reconstructed from its chunks, not concatenated from them: the context each chunk repeats so its own vector carries it — a heading breadcrumb, a time-window label, a table's header row — is emitted once, where the document had it. Provide exactly one of filePath (absolute path inside a document root) or source (the id of a data/url item). The response holds the full document text, so large documents produce large responses — prefer read_chunk_neighbors when only the context around one chunk is needed.
| Name | Type | Req | Description |
|---|---|---|---|
| filePath | – | – | – |
| source | – | – | – |
Structured output declared, but exposes no named fields.
No examples provided.
status ~198
Report configuration and index status. Works even when configuration is invalid. Always includes version. When configuration is valid, also includes roots, dbPath, model, hybridWeight, and chunkCount/sourceCount (both present on every call, 0 before anything is indexed) — or, if opening the index itself fails, indexError instead of the counts. When configuration is invalid, includes configError instead, and every other tool raises an error referencing it until the configuration is fixed. chunkScheme is the chunking scheme the index is being written with. staleChunkCount counts chunks still stored under an older scheme — when it is above zero, schemeWarning explains that those chunks need a re-sync to be rebuilt. ocr names the OCR engine this install can use, or is "unavailable" when the optional extra is missing — scanned PDFs and images cannot be indexed then, and ocrHint says what to install.
Input schema present but exposes no named parameters.
Structured output declared, but exposes no named fields.
No examples provided.
sync_start ~171
Reconcile the index with the document roots (or one path inside them). Returns a jobId immediately; poll sync_status until state is 'succeeded' or 'failed'. New and changed files are ingested, byte-identical files skipped, vanished files removed from the index. Only the latest sync job is retained — starting a new one, or a server restart, discards the previous job's record. Only one sync runs against an index at a time. If one is already in progress — in this server or in another process, such as a `minirag-mcp sync` in a terminal — this call fails immediately with a message identifying it, and no job is started. Single-file ingests and queries are never blocked by a running sync.
| Name | Type | Req | Description |
|---|---|---|---|
| path | – | – | – |
Structured output declared, but exposes no named fields.
No examples provided.
sync_status ~147
Poll a sync job started by sync_start. Returns state ('pending' | 'running' | 'succeeded' | 'failed'), counts (scanned/ingested/skipped/deleted/unreadable/failed), and any per-file errors. Only the latest job is retained — an old jobId, or any jobId from before a server restart, raises an error. unreadable counts indexed sources this installation cannot read because an optional extra is absent (images need [ocr]); each one appears in errors saying it was kept rather than deleted, but it is not a failure and does not make the job fail.
| Name | Type | Req | Description |
|---|---|---|---|
| jobId | string | yes | – |
Structured output declared, but exposes no named fields.
No examples provided.