rutter
NPM · RUTTER-MEMORY
Recall past decisions and the notes your AI sessions cited, from a local markdown folder.
Available components
Last scanned (13 hours ago)
Scores higher than 48% of npm servers
Category Memory and Knowledge
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 Security98
- No malware found by supply-chain analysis.Pass
- A known CVE affects sprintf-js, but no fixed version has been published, so there is nothing to upgrade to. View diagnostics → Partial
- No install/post-install scripts declared.Pass
- 39 of 103 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency100
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Cryptographically verified build provenance (signed, bound to shinytoyrobots/rutter). View diagnostics → Pass
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 1 days ago).Pass
- Publishes a security disclosure policy (SECURITY.md).Pass
Schema Quality & AI Usability62
- AI-judged instruction clarity (excellent).Pass
- 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. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management0
- Stability not yet verified: not enough scan history yet (needs a 30-day window).Unverified
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Tool Safety50
- Injection-marker check failed: the server instructions contains hidden, non-rendering content, an HTML comment, at byte 752 of that field. See how to fix → Fail
- We read all 4 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- 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
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.
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.
- 16 Oct 26 76
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 17 Oct 2026 · Analysed npm/rutter-memory@0.7.0
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 | npm |
| Reason | Verified |
| Discovered via | Registry attestation endpoint |
| Source repo | shinytoyrobots/rutter |
| Certificate issuer | https://token.actions.githubusercontent.com |
| Certificate SAN | https://github.com/shinytoyrobots/rutter/.github/workflows/release.yml@refs/tags/v0.7.0 |
| Rekor log index | 3273968577 |
| Predicate type | SLSA build provenance https://slsa.dev/provenance/v1 |
| Subject digest | sha512:5b351cede1d2542b82522a59f554c3588965e11f7d8902646f1868a987274868cfe968b31f0f282f16ff1a98c0c2601fe966eb0a845f7829b600a033a |
Background: How many MCP packages publish verified provenance →
Vulnerabilities 1 finding
| ID | CVE | Severity | Vector | Fix available |
|---|---|---|---|---|
| GHSA-hp3w-g68c-fv3c | CVE-2026-97058 | medium | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L | no |
Background: What a vulnerability scan can and cannot prove →
Dependencies 103 packages
| Packages resolved | 103 |
|---|---|
| Stale | 39 |
| Tree resolution | Complete |
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 →
librarian-get-note Read a note ~51
Return the full content of one vault note by its path (as returned by librarian-search). Read-only.
| Name | Type | Req | Description |
|---|---|---|---|
| path | string | yes | Vault-relative note path, e.g. 'Notes/Reference/foo.md'. |
No output schema declared.
No examples provided.
librarian-positions Recall a recorded position ~347
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.
| Name | Type | Req | Description |
|---|---|---|---|
| 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. |
No output schema declared.
No examples provided.
librarian-recent Recall recent work ~256
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.
| Name | Type | Req | Description |
|---|---|---|---|
| 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. |
No output schema declared.
No examples provided.
librarian-search Search the vault ~172
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.
| Name | Type | Req | Description |
|---|---|---|---|
| domain | string | – | Filter by frontmatter `domain`. |
| limit | integer | – | Max results (default 8). |
| query | string | yes | 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). |
No output schema declared.
No examples provided.
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.
npm · rutter-memory
claude mcp add shinytoyrobots-rutter -- npx -y rutter-memory
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.