# io.github.RuloGB/compendio-mcp (npm · compendio-mcp)

Indexes your project's markdown docs and serves them to any agent via local hybrid search.

- Trust score: 76/100 (medium)
- Change this week: +3
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-09-25

## Components

- npm · `compendio-mcp`: 76/100 (this document), [markdown](https://verifymcp.io/servers/rulogb-compendio-mcp/compendio-mcp.md), [page](https://verifymcp.io/servers/rulogb-compendio-mcp/compendio-mcp)

## Channel facts

- Registry: `npm`
- Package: `compendio-mcp`
- Version: `1.7.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-09-25.

- **Supply Chain Security**: 98/100
  - No malware found by supply-chain analysis.
  - No known CVEs affecting this package version or its production dependencies.
  - No install/post-install scripts declared.
  - 87 of 253 dependencies flagged as unhealthy (1 deprecated).
- **Provenance & Transparency**: 45/100
  - Source repository is publicly reachable at the declared URL.
  - Provenance check failed: no build-provenance attestation is published.
  - Clear OSI-approved license (MIT).
  - Actively maintained (last published 4 days ago).
  - Disclosure check failed: no security disclosure policy was found in the source repository.
- **Schema Quality & AI Usability**: 64/100
  - AI-judged instruction clarity (excellent).
  - Context-footprint check failed: tool/resource definitions use about 1137 tokens (~379/item across 3 items; 3 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 60/100
  - Stability observed for 18 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 3 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 4 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.RuloGB/compendio-mcp server?

io.github.RuloGB/compendio-mcp runs locally as an npm package, launched with npx -y compendio-mcp. 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 rulogb-compendio-mcp -- npx -y compendio-mcp
```

### Cursor

```json
{
  "mcpServers": {
    "rulogb-compendio-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "compendio-mcp"
      ]
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "rulogb-compendio-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "compendio-mcp"
      ]
    }
  }
}
```

### Codex

```bash
codex mcp add rulogb-compendio-mcp -- npx -y compendio-mcp
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "rulogb-compendio-mcp": {
      "type": "local",
      "command": [
        "npx",
        "-y",
        "compendio-mcp"
      ],
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add rulogb-compendio-mcp --command npx --arg -y --arg compendio-mcp
```

### Hermes

```yaml
mcp_servers:
  rulogb-compendio-mcp:
    command: "npx"
    args: ["-y", "compendio-mcp"]
```

### Netclaw

```json
{
  "McpServers": {
    "rulogb-compendio-mcp": {
      "Transport": "stdio",
      "Command": "npx",
      "Arguments": [
        "-y",
        "compendio-mcp"
      ]
    }
  }
}
```

### Vellum

```bash
assistant mcp add rulogb-compendio-mcp -t stdio -c npx -a -y compendio-mcp
```

### Other

```json
{
  "mcpServers": {
    "rulogb-compendio-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "compendio-mcp"
      ]
    }
  }
}
```

## 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-09-25 (score 76, 0)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-09-24 (score 76, +1)

No change was recorded against any check on this day. Stability & Change Management went from 53 to 57. That category is still filling its 30-day observation window: 16 days of observed history at the previous scan, 17 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-09-21 (score 75, +1)

No change was recorded against any check on this day. Stability & Change Management went from 43 to 47. That category is still filling its 30-day observation window: 13 days of observed history at the previous scan, 14 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-09-20 (score 74, 0)

- [security regression] Stability: 0.40 → unverified
- [security regression] Tool safety: pass → unverified
- [security regression] Known CVEs: pass → unverified
- [functional regression] Capabilities: pass → unverified
- [functional regression] Tool coverage: 100 → unverified
- [functional regression] Dependency health: 0.83 → unverified
- [functional] First check of Schema quality: unverified
- [functional] Package version: 1.7.0 → 1.7.2
- [functional] Package version: 1.7.0 → 1.7.1

### 2026-09-19 (score 74, +1)

- [security regression] Stability: 0.37 → unverified
- [security regression] Tool safety: pass → unverified
- [functional regression] Capabilities: pass → unverified
- [functional regression] Tool coverage: 100 → unverified
- [functional] First check of Schema quality: unverified
- [functional] Package version: 1.6.0 → 1.7.0

### 2026-09-17 (score 73, +4)

- [security improvement] GHSA-rgj7-g3m4-5g8c no longer affects this package
- [security improvement] GHSA-f88m-g3jw-g9cj no longer affects this package
- [security improvement] CVE-2026-39244 no longer affects this package
- [security improvement] Known CVEs: fail → pass

### 2026-09-15 (score 69, +16)

- [security improvement] Malware scan: unverified → pass

### 2026-09-13 (score 53, −15)

- [security regression] Malware scan: pass → unverified
- [functional] Package version: 1.5.0 → 1.6.0

## MCP tools (3)

### `docs_overview` (~108 tokens)

Documentation map

Map of the documentation corpus: counts by type and module, plus one line per document ([type] path — summary (status)). Use it to enumerate what exists, or to pick filter values for search_docs. When a user names a .md file but its exact indexed path is uncertain, use this to find that path before calling read_doc. For a specific question, call search_docs first — it answers in one call, while orienting here lists the whole corpus before you can read anything.

### `search_docs` (~426 tokens)

Documentation search

Hybrid search (lexical BM25 + semantic) in natural language over the project's documentation, with metadata filters. Entry point for any question about what the project does or why — behaviour, business rules, the exact text of a user-facing message, limits, endpoints, deployment steps, or the reasoning behind a decision. For a content or project question, this is the cheapest first probe; a filename alone does not reliably identify an indexed path, so resolve named .md files with docs_overview before calling read_doc. Source code remains the authority on current behaviour, while these docs are the only record of intent. The top result carries a full-length excerpt, centred on the part of the document that matched, which usually answers outright; the rest carry short ones, centred on their own match, enough to tell whether the top result is the right one. Each result has path, title, section, excerpt and score; section names the document region the fragment came from — a document with no headings reports one region for the whole file. A '…' at either end of an excerpt marks content omitted there — that is the signal to call read_doc with its path and section. If the project declares convention.excludedStatuses, documents in those statuses are left out unless include_excluded is set; if it declares none, no document is excluded by status.

Input parameters:

- `include_excluded` (boolean): Include documents whose status is listed in convention.excludedStatuses (no effect if the project declares no exclusions)
- `k` (integer): Number of results (5 by default)
- `module` (string): Filter by module — same caveat as type: omit unless docs_overview showed the value.
- `query` (string, required): Natural-language query
- `tags` (array): Filter by tags (matching one is enough) — same caveat: omit unless docs_overview showed them.
- `type` (string): Filter by document type — project-defined, and absent entirely in many projects. Omit it unless docs_overview showed you the value; never infer it from directory names or paths.

### `read_doc` (~241 tokens)

Read a document

Reads one section of a document, along with its frontmatter. Built for sections, not whole files: pass section whenever you can. Omitting it returns the entire document when it is small or cannot usefully be split into sections; a large document with sections returns its outline instead (H2 and H3 headings, each with an estimated token size), so call again with one of those headings as section. To read or summarize a whole document, start from its outline and request the sections you need. When a user names a section in a .md document, pass that named section here after locating the indexed path with docs_overview if necessary. If the path does not exist, it responds with the 3 closest matching paths instead of failing.

Input parameters:

- `path` (string, required): Document path, relative to the docs directory
- `section` (string): Heading (or part of it) of the section to read, e.g. 'Business rules', or a heading from read_doc's outline. Use the section field of a search_docs result. Sections name a region of a document, not a…

## Diagnostics

Captured diagnostic sections: Provenance, Dependencies. The full working is on the page: https://verifymcp.io/servers/rulogb-compendio-mcp/compendio-mcp#diagnostics

## Score history

- 2026-09-25: 76
- 2026-09-24: 76
- 2026-09-23: 75
- 2026-09-22: 75
- 2026-09-21: 75
- 2026-09-20: 74
- 2026-09-19: 74
- 2026-09-18: 73
- 2026-09-17: 73
- 2026-09-16: 69
- 2026-09-15: 69
- 2026-09-14: 53
- 2026-09-13: 53
- 2026-09-12: 68
- 2026-09-11: 52
- 2026-09-10: 52
- 2026-09-09: 65
- 2026-09-08: 65
- 2026-09-07: 65

## Common questions

### What is the io.github.RuloGB/compendio-mcp server?

io.github.RuloGB/compendio-mcp is listed in the public MCP registry as io.github.RuloGB/compendio-mcp. Indexes your project's markdown docs and serves them to any agent via local hybrid search. This page covers its npm package (compendio-mcp).

### Is the io.github.RuloGB/compendio-mcp server safe to use?

io.github.RuloGB/compendio-mcp scores 76 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 25 September 2026. It declares no install or post-install scripts. 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.RuloGB/compendio-mcp server expose?

io.github.RuloGB/compendio-mcp exposes 3 tools: docs_overview, search_docs, read_doc. Their descriptions and schemas cost roughly 775 tokens of context every time the server is loaded.

### Is the io.github.RuloGB/compendio-mcp server still maintained?

io.github.RuloGB/compendio-mcp is still listed as active in the MCP registry. We last reached this channel on 25 September 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.RuloGB/compendio-mcp server under?

io.github.RuloGB/compendio-mcp 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

- npm package: https://www.npmjs.com/package/compendio-mcp
- Socket report: https://socket.dev/npm/package/compendio-mcp
- Repository: https://github.com/RuloGB/compendio-mcp
- Changelog RSS feed: https://verifymcp.io/servers/rulogb-compendio-mcp/compendio-mcp.xml
- Changelog JSON feed: https://verifymcp.io/servers/rulogb-compendio-mcp/compendio-mcp.json
- HTML version of this page: https://verifymcp.io/servers/rulogb-compendio-mcp/compendio-mcp