Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

RoadRaven

NPM · @ROADRAVEN/MCP

Create and update roadmap tree nodes and statuses in the RoadRaven desktop app (must be running).

Available components

+38 this week 84 Trust /100

Last scanned (3 hours ago)

Scores higher than 83% of npm servers

Category Project Management

Trust breakdown (7 categories)

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
  • No known CVEs affecting this package version or its production dependencies.Pass
  • No install/post-install scripts declared.Pass
  • 31 of 92 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency84
  • Source repository is publicly reachable at the declared URL. View diagnostics → Pass
  • Cryptographically verified build provenance (signed, bound to Shuffzord/RoadRaven). View diagnostics → Pass
  • License check failed: the license (FSL-1.1-MIT) isn't a recognized OSI-approved license. See how to fix → Fail
  • Actively maintained (last published 4 days ago).Pass
  • Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability78
  • AI-judged instruction clarity (excellent).Pass
  • Tool/resource definitions use about 1956 tokens (~88/item across 22 items; 22 tools + 0 resources), lean.Pass
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management60
  • Stability observed for 18 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage82
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 46% of tool parameters carry a description.Partial
Tool Safety75
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • 0 of 1 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation; "deleteNode" implies "delete" and declares no destructiveHint at all, which the MCP spec reads as destructive by default. See how to fix → Fail
  • An AI judge read all 22 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
Changelog

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.

  • 17 Oct 26 +1

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

  • 15 Oct 26 +1

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

  • 13 Oct 26 +36
    • Injection markers: unverified → pass ▲ security
    • Tool coverage: unverified → 100 ▲ functional
    • MCP protocol: unverified → pass ▲ functional
    • Stability: unverified → 0.47 ▲ functional
  • 12 Oct 26 0
    • Tool safety: Tool safety not yet verified: we do not have a sandbox capture of the tool definitions this version of the package serves yet. security
    • Stability: Stability not yet verified: we do not have a sandbox capture of the MCP schema this version of the package serves yet. security
    • Capabilities: Protocol version not yet verified: we do not have a sandbox capture of the MCP handshake this version of the package performs yet. functional
    • Tool coverage: Tool coverage not yet verified: we do not have a sandbox capture of the tool definitions this version of the package serves yet. functional
    • Schema quality: Schema quality not yet verified: we do not have a sandbox capture of the MCP schema this version of the package serves yet. functional
    • Package version: 0.8.7 → 0.9.0 functional
    • Package version: 0.8.7 → 0.8.9 functional
  • 9 Oct 26 −29
    • Tool safety: pass → unverified ▼ security
    • Stability: Stability not yet verified: this package could not be installed in a clean environment, so we have no schema to compare. security
    • Tool coverage: 100 → unverified ▼ functional
    • Capabilities: pass → unverified ▼ functional
    • First check of Schema quality: unverified functional
  • 30 Sept 26 +15
    • Malware scan: unverified → pass ▲ security
  • 29 Sept 26 60

    First indexed and scored.

Diagnostics

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/@roadraven/mcp@0.9.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 Shuffzord/RoadRaven
Certificate issuer https://token.actions.githubusercontent.com
Certificate SAN https://github.com/Shuffzord/RoadRaven/.github/workflows/release.yml@refs/tags/v0.9.0
Rekor log index 3231860371
Predicate type SLSA build provenance https://slsa.dev/provenance/v1
Subject digest sha512:df5acd126d6b9d6a05d9ebcea157f31c2fa893f5dd751a1136d714878005148d4f0e57a2f612863c435ff87ea96361a1940ce83aa90dd9d2d211b7fa1

Background: How many MCP packages publish verified provenance →

Dependencies 92 packages
Packages resolved 92
Stale 31
Tree resolution Complete

Background: SBOMs and build attestations, explained →

MCP tools · 22 exposed · ~1,956 tokens

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 →

Tool Tokens
cameraFitView ~51

Compute a zoom + pan that fits all nodes into the viewport with margin. No-op when no roadmap is loaded. Used by automated demos / recordings to pull-back the camera; safe for live agent use too.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

createNode ~269

Add a child node under parentId with the given title. Optional: id (UUID or slug — supply it when recovering/recreating a node so its identity stays stable and history/metadata continuity survives file churn; duplicate_id if it already exists), type, core status (defaults to not-started), notes (markdown), metadata. Returns the new node's id. Requires a loaded roadmap.

NameTypeReqDescription
expectedRevisioninteger–Revision from your last getRoadmap/getNode read. If the roadmap changed since, the write fails with stale_write instead of clobbering.
idstring–Optional caller-supplied node id (UUID or slug ^[A-Za-z0-9][A-Za-z0-9._-]{0,63}$). Use when recreating a node so its identity stays stable and history/metadata continuity survives file churn. Fails w…
metadataobject––
notesstring––
parentIdstringyesID of the parent node
statusstring–Core node status — defaults to not-started
titlestringyesNode title
typestring–Node type id

No output schema declared.

No examples provided.

createRoadmap ~71

Initialize an in-memory untitled schema (mirrors File > New). Optional: title, statusConfig, typeConfig. The agent must call saveFileAs to persist the new roadmap to disk.

NameTypeReqDescription
statusConfigarray––
titlestring––
typeConfigarray––

No output schema declared.

No examples provided.

deleteNode ~92

Delete a node. Leaf nodes delete immediately; non-leaf nodes require cascade:true (returns cascade_required with childCount otherwise). Cannot delete the last remaining root.

NameTypeReqDescription
cascadeboolean––
expectedRevisioninteger–Revision from your last getRoadmap/getNode read. If the roadmap changed since, the write fails with stale_write instead of clobbering.
nodeIdstringyes–

No output schema declared.

No examples provided.

findNodes ~114

Search nodes by AND-combined filter: titleContains (case-insensitive substring), status, type, metaKey + metaValue, parentId. All fields optional. Returns matching nodes (without their children; use parentId or getNode for those) with their parent IDs.

NameTypeReqDescription
metaKeystring––
metaValue–––
parentIdstring––
statusstring––
titleContainsstring–Case-insensitive substring against node.title
typestring––

No output schema declared.

No examples provided.

getEventApiStatus ~33

Returns the current Event API URL, PID, and startedAt — or an error if the app is not running.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

getNode ~59

Return a node by UUID, with its immediate parent ID, full ancestor chain (root-to-parent), and the current roadmap `revision`. Status reflects the live overlay if a recent event landed.

NameTypeReqDescription
nodeIdstringyesID of the target node

No output schema declared.

No examples provided.

getOpenFile ~50

Return filePath (or null if untitled), isUntitled flag, document title, and total nodeCount. Works even when no file is loaded — returns null filePath and isUntitled=false.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

getRoadmap ~104

Return the full schema tree from the desktop app, with live-event statuses merged in, plus the current `revision` (pass it as expectedRevision on writes to detect stale reads). Pass omitNotes: true for polling (large roadmaps exceed the tool-result limit): it leaves out notes and the createdAt/updatedAt timestamps; fetch notes with getNode/findNodes. Requires the app to be running and a file to be loaded.

NameTypeReqDescription
omitNotesboolean––

No output schema declared.

No examples provided.

getStatusConfig ~32

Return the loaded roadmap's statusConfig array (display labels/colors for statuses). Agent mutations accept only core node statuses.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

getTypeConfig ~28

Return the loaded roadmap's typeConfig array (the valid node-type IDs and their visual configuration).

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

moveNode ~108

Re-parent a node to newParentId at optional position (0 = first child; omit = last child). Blocks cycles (cannot move into own subtree) and cross-$ref-boundary moves.

NameTypeReqDescription
expectedRevisioninteger–Revision from your last getRoadmap/getNode read. If the roadmap changed since, the write fails with stale_write instead of clobbering.
newParentIdstringyes–
nodeIdstringyes–
positioninteger––

No output schema declared.

No examples provided.

openFile ~58

Flush any pending autosave, then load a roadmap file by path. Path must satisfy the path-allowlist (same as user actions). The agent may need to ask the user to open the target directory first.

NameTypeReqDescription
pathstringyes–

No output schema declared.

No examples provided.

renameNode ~66

Change a node's title.

NameTypeReqDescription
expectedRevisioninteger–Revision from your last getRoadmap/getNode read. If the roadmap changed since, the write fails with stale_write instead of clobbering.
nodeIdstringyes–
titlestringyes–

No output schema declared.

No examples provided.

revealNode ~74

Select a node, centre the camera on it, open its side panel and bring the RoadRaven window to the front. Where the window manager refuses to raise the window, the node is still selected. Use it to show the human the node you are on.

NameTypeReqDescription
nodeIdstringyesID of the target node

No output schema declared.

No examples provided.

saveFile ~35

Force-flush the autosave debouncer immediately. Returns ok or save_error. For untitled schemas, call saveFileAs first.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

saveFileAs ~47

Save the loaded roadmap to a new file path. Path must satisfy the same allowlist as user actions (within the loaded directory, or previously user-picked).

NameTypeReqDescription
pathstringyes–

No output schema declared.

No examples provided.

updateNodeMetadata ~103

Shallow-PATCH a node's metadata. Each key in `patch` overwrites the same key in node.metadata; null value deletes that key. Unlisted keys are preserved. Returns the final metadata object.

NameTypeReqDescription
expectedRevisioninteger–Revision from your last getRoadmap/getNode read. If the roadmap changed since, the write fails with stale_write instead of clobbering.
nodeIdstringyes–
patchobjectyes–

No output schema declared.

No examples provided.

updateNodeNotes ~160

Set a node's notes string (markdown). mode "replace" (default) overwrites the entire notes field — pass an empty string to clear. mode "append" adds a blank line then your text after the existing notes; recommended for agent progress lines.

NameTypeReqDescription
expectedRevisioninteger–Revision from your last getRoadmap/getNode read. If the roadmap changed since, the write fails with stale_write instead of clobbering.
modestring–How to combine with existing notes. "replace" (default) overwrites the entire notes field; "append" adds a blank line then your text after the existing notes — recommended for agent progress lines.
nodeIdstringyes–
notesstringyes–

No output schema declared.

No examples provided.

updateNodes ~190

Apply up to 100 node updates (status, notes, metadata patch) in ONE atomic call — the roadmap revision advances exactly once for the whole batch and the response returns the final `revision` so you can chain further writes without re-reading. All-or-nothing: every item is validated first (node exists, status id in statusConfig); any failure returns batch_validation_failed with per-item {index, nodeId, code} and NOTHING is applied. Ideal for replaying a set of changes after stale_write: call getRoadmap once, rebuild all updates against the fresh tree, and resend the whole batch with expectedRevision.

NameTypeReqDescription
expectedRevisioninteger–Revision from your last getRoadmap/getNode read. If the roadmap changed since, the write fails with stale_write instead of clobbering.
updatesarrayyes1..100 node updates applied atomically as one change

No output schema declared.

No examples provided.

updateNodeStatus ~135

Push a status update to a node. Requires the desktop app to be running and a roadmap loaded. Routes through the agent dispatcher so the change appears in the event-log drawer (Ctrl+Shift+L).

NameTypeReqDescription
expectedRevisioninteger–Revision from your last getRoadmap/getNode read. If the roadmap changed since, the write fails with stale_write instead of clobbering.
metaobject–Arbitrary key-value metadata, e.g. { branch, commit, ci_run_id }
nodeIdstringyesThe node UUID from the roadmap
statusstringyesCore node status

No output schema declared.

No examples provided.

updateNodeType ~77

Change a node's type string. Use getTypeConfig to discover valid types.

NameTypeReqDescription
expectedRevisioninteger–Revision from your last getRoadmap/getNode read. If the roadmap changed since, the write fails with stale_write instead of clobbering.
nodeIdstringyes–
typestringyes–

No output schema declared.

No examples provided.

Install

How do I install the RoadRaven MCP server?

RoadRaven runs locally as an npm package, launched with npx -y @roadraven/mcp. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

npm · @roadraven/mcp

# add to Claude Code
claude mcp add shuffzord-roadraven -- npx -y @roadraven/mcp
Common questions

What is the RoadRaven MCP server?

RoadRaven is an MCP server listed in the public MCP registry as io.github.Shuffzord/roadraven. Create and update roadmap tree nodes and statuses in the RoadRaven desktop app (must be running). This page covers its npm package (@roadraven/mcp).

Is the RoadRaven MCP server safe to use?

RoadRaven scores 84 out of 100 on VerifyMCP. We found no known CVEs affecting 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 RoadRaven MCP server expose?

RoadRaven exposes 22 tools: updateNodeStatus, getEventApiStatus, getRoadmap, getNode, findNodes, and 17 more. Their descriptions and schemas cost roughly 1,956 tokens of context every time the server is loaded.

Is the RoadRaven MCP server still maintained?

RoadRaven 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 RoadRaven MCP server under?

RoadRaven declares the FSL-1.1-MIT licence, which is not on the OSI-approved list. Read the terms before using it at work, and note this covers the source only, not the cost of any service it calls.