# io.github.GitGudatCodeing/vault-index (pypi · vault-index)

Local hybrid keyword + vector search (SQLite FTS5 + sqlite-vec) over markdown vaults and code.

- Trust score: 81/100 (high trust)
- Change this week: +4
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-04

## Components

- pypi · `vault-index`: 81/100 (this document), [markdown](https://verifymcp.io/servers/gitgudatcodeing-vault-index/vault-index.md), [page](https://verifymcp.io/servers/gitgudatcodeing-vault-index/vault-index)

## Channel facts

- Registry: `pypi`
- Package: `vault-index`
- Version: `0.4.2`
- Transport: `stdio`

## Trust breakdown

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. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-11-04.

- **Supply Chain Security**: 99/100
  - No malware found by supply-chain analysis.
  - Known CVEs were checked across the 68 of 70 dependencies we could resolve, so this covers what we could see, not the whole tree.
  - Runs hatchling.build at install time, a recognised build step with no custom scripting around it.
  - Dependency health was assessed across the 68 of 70 dependencies we could resolve, so this covers what we could see, not the whole tree.
- **Provenance & Transparency**: 100/100
  - Source repository is publicly reachable at the declared URL.
  - Cryptographically verified build provenance (signed, bound to GitGudatCodeing/claude-second-brain).
  - Clear OSI-approved license (MIT).
  - Actively maintained (last published 6 days ago).
  - Publishes a security disclosure policy (SECURITY.md).
- **Schema Quality & AI Usability**: 65/100
  - AI-judged instruction clarity (good).
  - Tool/resource definitions use about 286 tokens (~57/item across 5 items; 5 tools + 0 resources), lean.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 37/100
  - Stability observed for 11 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 71/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 0% of tool parameters carry a description.
  - Structured output schemas are declared (100% of tools); any adoption earns full credit.
- **Tool Safety**: 75/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - 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.
  - An AI judge read all 5 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

## Install

### 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.

### Claude

```bash
claude mcp add gitgudatcodeing-vault-index -- uvx vault-index
```

### Cursor

```json
{
  "mcpServers": {
    "gitgudatcodeing-vault-index": {
      "command": "uvx",
      "args": [
        "vault-index"
      ]
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "gitgudatcodeing-vault-index": {
      "command": "uvx",
      "args": [
        "vault-index"
      ]
    }
  }
}
```

### Codex

```bash
codex mcp add gitgudatcodeing-vault-index -- uvx vault-index
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "gitgudatcodeing-vault-index": {
      "type": "local",
      "command": [
        "uvx",
        "vault-index"
      ],
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add gitgudatcodeing-vault-index --command uvx --arg vault-index
```

### Hermes

```yaml
mcp_servers:
  gitgudatcodeing-vault-index:
    command: "uvx"
    args: ["vault-index"]
```

### Netclaw

```json
{
  "McpServers": {
    "gitgudatcodeing-vault-index": {
      "Transport": "stdio",
      "Command": "uvx",
      "Arguments": [
        "vault-index"
      ]
    }
  }
}
```

### Vellum

```bash
assistant mcp add gitgudatcodeing-vault-index -t stdio -c uvx -a vault-index
```

### Other

```json
{
  "mcpServers": {
    "gitgudatcodeing-vault-index": {
      "command": "uvx",
      "args": [
        "vault-index"
      ]
    }
  }
}
```

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-11-04 (score 81, +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.

### 2026-11-02 (score 80, +16)

- [security improvement] Malware scan: unverified → pass

### 2026-11-01 (score 64, −15)

- [security regression] Malware scan: pass → unverified

### 2026-10-31 (score 79, +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.

### 2026-10-29 (score 78, +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.

### 2026-10-28 (score 77, +16)

- [security improvement] Malware scan: unverified → pass
- [functional improvement] Stability: unverified → 0.13
- [functional] Package version: 0.4.1 → 0.4.2

### 2026-10-26 (score 61, +61)

- [security improvement] CVE-2026-112403 no longer affects this package
- [security improvement] CVE-2026-112900 no longer affects this package
- [security improvement] CVE-2026-96639 no longer affects this package
- [security improvement] CVE-2026-112398 no longer affects this package
- [security improvement] CVE-2026-112393 no longer affects this package
- [security improvement] Known CVEs: fail → partial
- [functional improvement] Score status: failed → scored

### 2026-10-24 (score 0)

First indexed and scored.

## MCP tools (5)

### `index_paths` (~93 tokens)

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.

Input parameters:

- `paths`
- `reindex` (boolean)

Output parameters:

- `result` (string)

### `search_notes` (~112 tokens)

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).

Input parameters:

- `limit` (integer)
- `path_prefix`
- `query` (string, required)

Output parameters:

- `result` (string)

### `get_note` (~28 tokens)

Return the full text of an indexed file (read from disk).

Input parameters:

- `path` (string, required)

Output parameters:

- `result` (string)

### `list_sources` (~18 tokens)

List registered source paths with file and chunk counts.

Output parameters:

- `result` (string)

### `remove_source` (~35 tokens)

Unregister a source and delete its files/chunks from the index (files on disk are untouched).

Input parameters:

- `path` (string, required)

Output parameters:

- `result` (string)

## Diagnostics

Captured diagnostic sections: Provenance, Install scripts, Dependencies. The full working is on the page: https://verifymcp.io/servers/gitgudatcodeing-vault-index/vault-index#diagnostics

## Score history

- 2026-11-04: 81
- 2026-11-03: 80
- 2026-11-02: 80
- 2026-11-01: 64
- 2026-10-31: 79
- 2026-10-30: 78
- 2026-10-29: 78
- 2026-10-28: 77
- 2026-10-27: 61
- 2026-10-26: 61
- 2026-10-25: 0
- 2026-10-24: 0

## Common questions

### 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.

## Links

- PyPI project: https://pypi.org/project/vault-index/
- Socket report: https://socket.dev/pypi/package/vault-index
- Repository: https://github.com/GitGudatCodeing/claude-second-brain
- Changelog RSS feed: https://verifymcp.io/servers/gitgudatcodeing-vault-index/vault-index.xml
- Changelog JSON feed: https://verifymcp.io/servers/gitgudatcodeing-vault-index/vault-index.json
- HTML version of this page: https://verifymcp.io/servers/gitgudatcodeing-vault-index/vault-index