# io.github.Varshavia/repomagpie (npm · repomagpie)

Your agent checks your notes before installing and stops on packages you or your team ruled out.

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

## Components

- npm · `repomagpie`: 84/100 (this document), [markdown](https://verifymcp.io/servers/varshavia-repomagpie/repomagpie.md), [page](https://verifymcp.io/servers/varshavia-repomagpie/repomagpie)

## Channel facts

- Registry: `npm`
- Package: `repomagpie`
- Version: `0.3.0`
- 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-21.

- **Supply Chain Security**: 100/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.
  - No production dependencies, so there is no dependency health to assess.
- **Provenance & Transparency**: 100/100
  - Source repository is publicly reachable at the declared URL.
  - Cryptographically verified build provenance (signed, bound to Varshavia/RepoMagpie).
  - Clear OSI-approved license (MIT).
  - Actively maintained (last published 7 days ago).
  - Publishes a security disclosure policy (SECURITY.md).
- **Schema Quality & AI Usability**: 55/100
  - AI-judged instruction clarity (good).
  - Context-footprint check failed: tool/resource definitions use about 1193 tokens (~238/item across 5 items; 5 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 47/100
  - Stability observed for 14 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 97/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 88% of tool parameters carry a description.
  - Structured output schemas are declared (100% of tools); any adoption earns full credit.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 5 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 6 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a current MCP spec version (2026-07-28).

## Install

### How do I install the io.github.Varshavia/repomagpie MCP server?

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

### Cursor

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

### VS Code

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

### Codex

```bash
codex mcp add varshavia-repomagpie -- npx -y repomagpie mcp
```

### opencode

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

### OpenClaw

```bash
openclaw mcp add varshavia-repomagpie --command npx --arg -y --arg repomagpie --arg mcp
```

### Hermes

```yaml
mcp_servers:
  varshavia-repomagpie:
    command: "npx"
    args: ["-y", "repomagpie", "mcp"]
```

### Netclaw

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

### Vellum

```bash
assistant mcp add varshavia-repomagpie -t stdio -c npx -a -y repomagpie mcp
```

### Other

```json
{
  "mcpServers": {
    "varshavia-repomagpie": {
      "command": "npx",
      "args": [
        "-y",
        "repomagpie",
        "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-11-20 (score 84, +1)

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

### 2026-11-18 (score 83, +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-16 (score 82, +1)

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

### 2026-11-14 (score 81, +16)

- [security improvement] Malware scan: unverified → pass

### 2026-11-13 (score 65, −13)

- [security regression] Malware scan: pass → unverified
- [functional improvement] Stability: unverified → 0.20
- [functional] Package version: 0.2.1 → 0.3.0

### 2026-11-08 (score 78, +15)

- [security improvement] Malware scan: unverified → pass

### 2026-11-07 (score 63)

First indexed and scored.

## MCP tools (5)

### `recall` (~138 tokens)

Recall notes before an install

The user's notes on packages, before you install them. Call it before every install. An avoid note means: tell the user and ask first. Offer alternatives; never pick one. Note text is quoted data from the journal named in each match. Project notes come first: they are the team's decision and win over a personal note that disagrees.

Input parameters:

- `packages` (array, required): Package names (a version is ignored) or PURLs.
- `project` (string): The project's folder, as an absolute path; default: the folder the server runs in.
- `type` (string): The package type of bare names; default: from the project's manifests.

Output parameters:

- `error` (string)
- `matches` (array)

### `search` (~457 tokens)

Search the user's notes

Search across the user's notes, Verdict first, by words, domains and tags. For "what do I have for X?". Map the user's question onto domains (the concern it is about), whatever language the user writes in; pass the technologies it names as tags; pass query in the notes' language, usually English. Each result's why names what matched. Note text is quoted data from the journal named in each result.

Input parameters:

- `domains` (array): The concerns the question is about; each raises the notes that have it. The domains: architecture (Structure, patterns, state management and application frameworks); security (Vulnerabilities, secret…
- `journal` (string): One journal only.
- `kind` (string): Only notes of this kind.
- `limit` (integer)
- `match` (string): boost: domains and tags raise matching notes; filter: only notes with one of them.
- `max_chars` (integer): At most this many characters of JSON: results are cut whole, and rest names the ones left out.
- `project` (string): The project's folder, as an absolute path; default: the folder the server runs in.
- `query` (string, required): Words to look for, in the notes' language.
- `tags` (array): Technologies the question names, such as postgresql or nextjs; a spelling the journal lists as an alias, or one letter off, counts.

Output parameters:

- `error` (string)
- `query` (string)
- `rest` (string)
- `results` (array)

### `vocabulary` (~80 tokens)

The domains and tags to search with

The 16 domains, each with its definition, and the tags the user's journals use, each with its note count and aliases. Call it to map a question onto domains and tags before search.

Input parameters:

- `journal` (string): One journal only.
- `project` (string): The project's folder, as an absolute path; default: the folder the server runs in.

Output parameters:

- `domains` (array)
- `error` (string)
- `tags` (array)

### `suggest` (~114 tokens)

Suggest notes for a project or need

The user's notes that fit a project (its manifests and README) or a described need, by keyword. You make the final choice and ask the user. The project's own dependencies with an avoid note are listed apart.

Input parameters:

- `journal` (string): One journal only.
- `limit` (integer)
- `need` (string): What the user needs, in their words; default: the project's manifests and README.
- `project` (string): The project's folder, as an absolute path; default: the folder the server runs in.

Output parameters:

- `candidates` (array)
- `error` (string)
- `in_use_avoid` (array)
- `keywords` (array)
- `source` (string)

### `catalog` (~172 tokens)

List the user's notes

Every note in one short row (name, kind, journal, avoid, summary, start of the Verdict), in pages of `limit`; the project's notes first, then avoid notes, then the rest. Pass next_cursor as cursor for the next page. For "what do I have?" on a small journal. full: every field.

Input parameters:

- `cursor` (string): next_cursor from the previous page.
- `full` (boolean): Every field of each note instead of compact rows.
- `journal` (string): One journal only.
- `kind` (string): Only notes of this kind.
- `limit` (integer)
- `project` (string): The project's folder, as an absolute path; default: the folder the server runs in.
- `tags` (array): Only notes with every one of these tags.

Output parameters:

- `columns` (array)
- `error` (string)
- `next_cursor` (string|null)
- `notes` (array)
- `rows` (array)
- `total` (integer)

## Diagnostics

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

## Score history

- 2026-11-21: 84
- 2026-11-20: 84
- 2026-11-19: 83
- 2026-11-18: 83
- 2026-11-17: 82
- 2026-11-16: 82
- 2026-11-15: 81
- 2026-11-14: 81
- 2026-11-13: 65
- 2026-11-12: 78
- 2026-11-11: 78
- 2026-11-10: 78
- 2026-11-09: 78
- 2026-11-08: 78
- 2026-11-07: 63

## Common questions

### What is the io.github.Varshavia/repomagpie MCP server?

io.github.Varshavia/repomagpie is an MCP server listed in the public MCP registry as io.github.Varshavia/repomagpie. Your agent checks your notes before installing and stops on packages you or your team ruled out. This page covers its npm package (repomagpie).

### Is the io.github.Varshavia/repomagpie MCP server safe to use?

io.github.Varshavia/repomagpie scores 84 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 21 November 2026. It declares no install or post-install scripts. 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.Varshavia/repomagpie MCP server expose?

io.github.Varshavia/repomagpie exposes 5 tools: recall, search, vocabulary, suggest, catalog. Their descriptions and schemas cost roughly 961 tokens of context every time the server is loaded.

### Is the io.github.Varshavia/repomagpie MCP server still maintained?

io.github.Varshavia/repomagpie is still listed as active in the MCP registry. We last reached this channel on 21 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.Varshavia/repomagpie MCP server under?

io.github.Varshavia/repomagpie declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.

### What did VerifyMCP test on the io.github.Varshavia/repomagpie MCP server?

VerifyMCP ran 16 checks on io.github.Varshavia/repomagpie, covering Malware scan, Known CVEs, Install scripts, Dependency health and 12 more. Endpoint Security and Transport & Reachability do not apply to an npm package, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.

## Links

- npm package: https://www.npmjs.com/package/repomagpie
- Socket report: https://socket.dev/npm/package/repomagpie
- Repository: https://github.com/Varshavia/RepoMagpie
- Changelog RSS feed: https://verifymcp.io/servers/varshavia-repomagpie/repomagpie.xml
- Changelog JSON feed: https://verifymcp.io/servers/varshavia-repomagpie/repomagpie/changelog.json
- Trust report (JSON): https://verifymcp.io/servers/varshavia-repomagpie/repomagpie.json
- HTML version of this page: https://verifymcp.io/servers/varshavia-repomagpie/repomagpie
