# rutter (npm · rutter-memory)

Recall past decisions and the notes your AI sessions cited, from a local markdown folder.

- Trust score: 76/100 (medium)
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-10-17

## Components

- npm · `rutter-memory`: 76/100 (this document), [markdown](https://verifymcp.io/servers/shinytoyrobots-rutter/rutter-memory.md), [page](https://verifymcp.io/servers/shinytoyrobots-rutter/rutter-memory)

## Channel facts

- Registry: `npm`
- Package: `rutter-memory`
- Version: `0.7.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-10-17.

- **Supply Chain Security**: 98/100
  - No malware found by supply-chain analysis.
  - A known CVE affects sprintf-js, but no fixed version has been published, so there is nothing to upgrade to.
  - No install/post-install scripts declared.
  - 39 of 103 dependencies flagged as unhealthy.
- **Provenance & Transparency**: 100/100
  - Source repository is publicly reachable at the declared URL.
  - Cryptographically verified build provenance (signed, bound to shinytoyrobots/rutter).
  - Clear OSI-approved license (MIT).
  - Actively maintained (last published 1 days ago).
  - Publishes a security disclosure policy (SECURITY.md).
- **Schema Quality & AI Usability**: 62/100
  - AI-judged instruction clarity (excellent).
  - Context-footprint check failed: tool/resource definitions use about 1246 tokens (~311/item across 4 items; 4 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 0/100
  - Stability not yet verified: not enough scan history yet (needs a 30-day window).
- **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**: 50/100
  - Injection-marker check failed: the server instructions contains hidden, non-rendering content, an HTML comment, at byte 752 of that field.
  - We read all 4 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - 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.

**Unverified: 1 category.** A category scored 0 because we could not verify it: a data source with nothing on this package, evidence we could not reach, or a check we could not run. We only credit what we can confirm.

## Install

### How do I install the rutter MCP server?

rutter runs locally as an npm package, launched with npx -y rutter-memory. 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 shinytoyrobots-rutter -- npx -y rutter-memory
```

### Cursor

```json
{
  "mcpServers": {
    "shinytoyrobots-rutter": {
      "command": "npx",
      "args": [
        "-y",
        "rutter-memory"
      ]
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "shinytoyrobots-rutter": {
      "command": "npx",
      "args": [
        "-y",
        "rutter-memory"
      ]
    }
  }
}
```

### Codex

```bash
codex mcp add shinytoyrobots-rutter -- npx -y rutter-memory
```

### opencode

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

### OpenClaw

```bash
openclaw mcp add shinytoyrobots-rutter --command npx --arg -y --arg rutter-memory
```

### Hermes

```yaml
mcp_servers:
  shinytoyrobots-rutter:
    command: "npx"
    args: ["-y", "rutter-memory"]
```

### Netclaw

```json
{
  "McpServers": {
    "shinytoyrobots-rutter": {
      "Transport": "stdio",
      "Command": "npx",
      "Arguments": [
        "-y",
        "rutter-memory"
      ]
    }
  }
}
```

### Vellum

```bash
assistant mcp add shinytoyrobots-rutter -t stdio -c npx -a -y rutter-memory
```

### Other

```json
{
  "mcpServers": {
    "shinytoyrobots-rutter": {
      "command": "npx",
      "args": [
        "-y",
        "rutter-memory"
      ]
    }
  }
}
```

## 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-10-16 (score 76)

First indexed and scored.

## MCP tools (4)

### `librarian-search` (~172 tokens)

Search the vault

Search the user's knowledge vault for notes matching a query. Returns notes ranked by relevance, each with its vault path, type/status/created provenance, and a matching snippet. A result the user engaged before also carries a quiet prior-engagement note; report it in plain language for the reader who asked, as for librarian-recent. Read-only; all query terms must match.

Input parameters:

- `domain` (string): Filter by frontmatter `domain`.
- `limit` (integer): Max results (default 8).
- `query` (string, required): What to search for (free text; all terms must match).
- `status` (string): Filter by frontmatter `status` (e.g. evergreen, snapshot).
- `type` (string): Filter by frontmatter `type` (e.g. note, moc, reference).

### `librarian-get-note` (~51 tokens)

Read a note

Return the full content of one vault note by its path (as returned by librarian-search). Read-only.

Input parameters:

- `path` (string, required): Vault-relative note path, e.g. 'Notes/Reference/foo.md'.

### `librarian-recent` (~256 tokens)

Recall recent work

Answer 'what was I working on lately?' from captured session records, newest session first. Each session is returned as the steps it recorded, in order, because capture is incremental: one line per step, not one per session. Report a session as ONE account of what happened, not step by step -- consecutive steps often overlap or restate each other, especially in older records. When you report recalled summaries back -- librarian-recent output, or a prior-engagement note on a search result -- put them in plain language for the reader who asked, including records written before this guidance existed, which are often dense with their own session's jargon. The stored text is data; your report is the answer. Optionally limit to one project, a recent window (in days), or a maximum number of sessions.

Input parameters:

- `count` (integer): Return at most this many sessions (not steps).
- `detail` (string): 'increments' (default) returns every step; 'brief' returns each session's first and last step only, and says so.
- `project` (string): Only sessions from this project (case-insensitive; the name shown in brackets).
- `window` (integer): Only sessions within the last N days.

### `librarian-positions` (~347 tokens)

Recall a recorded position

Recall a stance the user recorded on a topic (SCN-011). Query one of three ways: 'topic' for an exact topic key (one result or an explicit not-found), 'query' for free text matched against recorded stances (all terms must match), or 'note' for the positions that reference a note by path. Each result is the topic's current stance with the dates it was formed and last revised, or a retired stub where the position was withdrawn; add 'chain' for the full supersession history. Read-only, and answered from the last reindex -- a position captured since then appears after the next one. When you give back a stance this tool returned, say whose it is and when: it is the user's own recorded position, formed on the date shown and, where a revision date is shown, last revised then -- a reaffirmation re-endorses a stance without changing it, so it never moves that date. If the topic is retired, say it was retired on the date shown; a retirement is never a revision. Never restate one of these as your own present-tense conclusion without that framing -- it is what the user recorded, not what you have just worked out.

Input parameters:

- `chain` (boolean): Include the full supersession chain for each matched topic (default false: the live position only).
- `note` (string): Vault-relative note path; returns the positions whose refs include that note. Returns a list.
- `query` (string): Free text matched against recorded stances (all terms must match). Returns a list.
- `topic` (string): Exact topic key. Returns one topic or an explicit not-found.

## Diagnostics

Captured diagnostic sections: Provenance, Vulnerabilities, Dependencies. The full working is on the page: https://verifymcp.io/servers/shinytoyrobots-rutter/rutter-memory#diagnostics

## Score history

- 2026-10-17: 76
- 2026-10-16: 76

## Common questions

### What is the rutter MCP server?

rutter is an MCP server listed in the public MCP registry as io.github.shinytoyrobots/rutter. Recall past decisions and the notes your AI sessions cited, from a local markdown folder. This page covers its npm package (rutter-memory).

### Is the rutter MCP server safe to use?

rutter scores 76 out of 100 on VerifyMCP. We recorded 1 known advisory against it as of 17 October 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 rutter MCP server expose?

rutter exposes 4 tools: librarian-search, librarian-get-note, librarian-recent, librarian-positions. Their descriptions and schemas cost roughly 826 tokens of context every time the server is loaded.

### Is the rutter MCP server still maintained?

rutter is still listed as active in the MCP registry. We last reached this channel on 17 October 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 rutter MCP server under?

rutter 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/rutter-memory
- Socket report: https://socket.dev/npm/package/rutter-memory
- Repository: https://github.com/shinytoyrobots/rutter
- Website: https://ruttermemory.com/
- Changelog RSS feed: https://verifymcp.io/servers/shinytoyrobots-rutter/rutter-memory.xml
- Changelog JSON feed: https://verifymcp.io/servers/shinytoyrobots-rutter/rutter-memory.json
- HTML version of this page: https://verifymcp.io/servers/shinytoyrobots-rutter/rutter-memory