io.github.GitGudatCodeing/vault-index
PYPI · VAULT-INDEX
Local hybrid keyword + vector search (SQLite FTS5 + sqlite-vec) over markdown vaults and code.
Available components
Last scanned (17 hours ago)
Scores higher than 82% of PyPI servers
Category Search and Retrieval
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
- Known CVEs were checked across the 68 of 70 dependencies we could resolve, so this covers what we could see, not the whole tree.Partial
- Runs hatchling.build at install time, a recognised build step with no custom scripting around it. View diagnostics → Pass
- Dependency health was assessed across the 68 of 70 dependencies we could resolve, so this covers what we could see, not the whole tree. View diagnostics → Partial
Provenance & Transparency100
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Cryptographically verified build provenance (signed, bound to GitGudatCodeing/claude-second-brain). View diagnostics → Pass
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 6 days ago).Pass
- Publishes a security disclosure policy (SECURITY.md).Pass
Schema Quality & AI Usability65
- AI-judged instruction clarity (good).Pass
- Tool/resource definitions use about 286 tokens (~57/item across 5 items; 5 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management37
- Stability observed for 11 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
Tool Safety75
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- 0 of 1 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation; "remove_source" implies "remove" 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 5 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
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.
- 4 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 33 to 37. That category is still filling its 30-day observation window: 10 days of observed history at the previous scan, 11 at this one. The score rises as the window fills, whether or not the server changes.
- 2 Nov 26 +16
- Malware scan: unverified → pass ▲ security
- 1 Nov 26 −15
- Malware scan: pass → unverified ▼ security
- 31 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 20 to 23. That category is still filling its 30-day observation window: 6 days of observed history at the previous scan, 7 at this one. The score rises as the window fills, whether or not the server changes.
- 29 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 13 to 17. That category is still filling its 30-day observation window: 4 days of observed history at the previous scan, 5 at this one. The score rises as the window fills, whether or not the server changes.
- 28 Oct 26 +16
- Malware scan: unverified → pass ▲ security
- Stability: unverified → 0.13 ▲ functional
- Package version: 0.4.1 → 0.4.2 functional
- 26 Oct 26 +61
- CVE-2026-112403 no longer affects this package ▲ security
- CVE-2026-112900 no longer affects this package ▲ security
- CVE-2026-96639 no longer affects this package ▲ security
- CVE-2026-112398 no longer affects this package ▲ security
- CVE-2026-112393 no longer affects this package ▲ security
- Known CVEs: fail → partial ▲ security
- Score status: failed → scored ▲ functional
- 24 Oct 26 0
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 4 Nov 2026 · Analysed pypi/vault-index@0.4.2
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 | pypi |
| Reason | Verified |
| Discovered via | Registry attestation endpoint |
| Source repo | GitGudatCodeing/claude-second-brain |
| Certificate issuer | https://token.actions.githubusercontent.com |
| Certificate SAN | https://github.com/GitGudatCodeing/claude-second-brain/.github/workflows/release.yml@refs/tags/v0.4.2 |
| Rekor log index | 3537233573 |
| Predicate type | PyPI publish attestation https://docs.pypi.org/attestations/publish/v1 |
| Subject digest | sha256:f84667cc2b732f0e41e7933e495c915f1e08826bf1c6f8a963290e6468c06650 |
Background: How many MCP packages publish verified provenance →
Install scripts 1 script
| Hook | Tier | Command |
|---|---|---|
| build_backend | allowlisted | hatchling.build |
Background: Why install scripts are a supply-chain risk →
Dependencies 68 packages
| Packages resolved | 68 |
|---|---|
| Stale | 7 |
| No linked repository | 2 |
| Tree resolution | Partial |
The dependency tree was only partially resolved, so these counts may be incomplete.
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 →
get_note ~28
Return the full text of an indexed file (read from disk).
| Name | Type | Req | Description |
|---|---|---|---|
| path | string | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
index_paths ~93
Add folders/files to the index (remembered as sources) and sync them. With no `paths`, re-syncs every registered source (picks up new, changed and deleted files). `reindex=True` forces re-embedding of everything (needed after a model change). A registered source that is missing on disk keeps its index until remove_source.
| Name | Type | Req | Description |
|---|---|---|---|
| paths | – | – | – |
| reindex | boolean | – | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
list_sources ~18
List registered source paths with file and chunk counts.
Input schema present but exposes no named parameters.
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
remove_source ~35
Unregister a source and delete its files/chunks from the index (files on disk are untouched).
| Name | Type | Req | Description |
|---|---|---|---|
| path | string | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
search_notes ~112
Hybrid search (keyword + semantic, merged with reciprocal rank fusion, then the top results reordered by a cross-encoder). Returns the best-matching chunks with file path, heading and score (higher is better). `path_prefix` restricts the search to files under it: an absolute path, or one relative to a source such as "docs/lessons.md" (either slash, any case).
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | – |
| path_prefix | – | – | – |
| query | string | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
How do I install the io.github.GitGudatCodeing/vault-index MCP server?
io.github.GitGudatCodeing/vault-index runs locally as a PyPI package, launched with uvx vault-index. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
pypi · vault-index
claude mcp add gitgudatcodeing-vault-index -- uvx vault-index
What is the io.github.GitGudatCodeing/vault-index MCP server?
io.github.GitGudatCodeing/vault-index is an MCP server listed in the public MCP registry as io.github.GitGudatCodeing/vault-index. Local hybrid keyword + vector search (SQLite FTS5 + sqlite-vec) over markdown vaults and code. This page covers its PyPI package (vault-index).
Is the io.github.GitGudatCodeing/vault-index MCP server safe to use?
io.github.GitGudatCodeing/vault-index scores 81 out of 100 on VerifyMCP. 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 io.github.GitGudatCodeing/vault-index MCP server expose?
io.github.GitGudatCodeing/vault-index exposes 5 tools: index_paths, search_notes, get_note, list_sources, remove_source. Their descriptions and schemas cost roughly 286 tokens of context every time the server is loaded.
Is the io.github.GitGudatCodeing/vault-index MCP server still maintained?
io.github.GitGudatCodeing/vault-index is still listed as active in the MCP registry. We last reached this channel on 4 November 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 io.github.GitGudatCodeing/vault-index MCP server under?
io.github.GitGudatCodeing/vault-index declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.