# Vulcanus (npm · @sunsato/vulcanus)

A validated Markdown memory vault your coding agent can recall, project by project.

- Trust score: 94/100 (high trust)
- Change this week: −2
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-09-20

## Components

- npm · `@sunsato/vulcanus`: 94/100 (this document), [markdown](https://verifymcp.io/servers/sunsatosolutions-vulcanus/sunsato-vulcanus.md), [page](https://verifymcp.io/servers/sunsatosolutions-vulcanus/sunsato-vulcanus)

## Channel facts

- Registry: `npm`
- Package: `@sunsato/vulcanus`
- Version: `0.5.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-09-20.

- **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.
  - 31 of 102 dependencies flagged as unhealthy.
- **Provenance & Transparency**: 97/100
  - Source repository is publicly reachable at the declared URL.
  - Cryptographically verified build provenance (signed, bound to sunsatosolutions/Vulcanus).
  - Clear OSI-approved license (MIT).
  - Actively maintained (last published 32 days ago).
  - Disclosure check failed: no security disclosure policy was found in the source repository.
- **Schema Quality & AI Usability**: 83/100
  - AI-judged instruction clarity (excellent).
  - Tool/resource definitions use about 787 tokens (~98/item across 8 items; 8 tools + 0 resources), lean.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 87/100
  - Stability observed for 26 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 8 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 8 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 Vulcanus MCP server?

Vulcanus runs locally as an npm package, launched with npx -y @sunsato/vulcanus. 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 sunsatosolutions-vulcanus -- npx -y @sunsato/vulcanus
```

### Cursor

```json
{
  "mcpServers": {
    "sunsatosolutions-vulcanus": {
      "command": "npx",
      "args": [
        "-y",
        "@sunsato/vulcanus"
      ]
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "sunsatosolutions-vulcanus": {
      "command": "npx",
      "args": [
        "-y",
        "@sunsato/vulcanus"
      ]
    }
  }
}
```

### Codex

```bash
codex mcp add sunsatosolutions-vulcanus -- npx -y @sunsato/vulcanus
```

### opencode

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

### OpenClaw

```bash
openclaw mcp add sunsatosolutions-vulcanus --command npx --arg -y --arg @sunsato/vulcanus
```

### Hermes

```yaml
mcp_servers:
  sunsatosolutions-vulcanus:
    command: "npx"
    args: ["-y", "@sunsato/vulcanus"]
```

### Netclaw

```json
{
  "McpServers": {
    "sunsatosolutions-vulcanus": {
      "Transport": "stdio",
      "Command": "npx",
      "Arguments": [
        "-y",
        "@sunsato/vulcanus"
      ]
    }
  }
}
```

### Vellum

```bash
assistant mcp add sunsatosolutions-vulcanus -t stdio -c npx -a -y @sunsato/vulcanus
```

### Other

```json
{
  "mcpServers": {
    "sunsatosolutions-vulcanus": {
      "command": "npx",
      "args": [
        "-y",
        "@sunsato/vulcanus"
      ]
    }
  }
}
```

## 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-20 (score 94, +1)

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

### 2026-09-18 (score 93, −3)

- [functional] Stability: pass → 0.80

### 2026-09-16 (score 96, +1)

- [security] Stability: 0.97 → pass

### 2026-09-14 (score 95, −1)

- [functional] Stability: pass → 0.93

### 2026-09-13 (score 96, +1)

- [security] Stability: 0.97 → pass

### 2026-09-11 (score 95, +1)

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

### 2026-09-09 (score 94, +1)

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

### 2026-09-06 (score 93, +1)

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

## MCP tools (8)

### `recall` (~78 tokens)

Recall a project

The entry point before working on any project: returns its Capsule (the compressed must-remember summary) plus the read-next list for deeper context. Query by project name, id, or a trigger word. Read-only; when nothing matches, the error lists the projects that exist.

Input parameters:

- `project` (string, required): Project name, id, or trigger word

### `search` (~72 tokens)

Search the vault

Layer-aware text search across the vault. Capsule and Recall Map hits rank first so the cheapest sufficient note surfaces on top. Read-only; prefer `recall` when you already know which project you need.

Input parameters:

- `limit` (integer): Max hits, default 20
- `query` (string, required): Text to look for

### `list_projects` (~48 tokens)

List projects

The routing table: every project with its status, summary, trigger words, and capsule path. Read-only, and the cheapest way to see what exists before calling `recall` or `search`.

### `append_decision` (~138 tokens)

Record a decision

Append a confirmed decision to a project's Decisions note, in the vault's Decision/Details format. Only record what the operator has actually confirmed. Writes to disk: it adds to the end of the note and never edits what is already there, so calling it twice records the decision twice. Returns the note path and the heading written; errors when the project or its Decisions note is missing.

Input parameters:

- `decision` (string, required): The decision itself, one or two sentences
- `details` (string): Optional supporting details
- `project` (string, required): Project name, id, or trigger word
- `title` (string, required): Short heading for the decision

### `update_capsule` (~146 tokens)

Refresh a capsule section

Replace one section of a project's Capsule — the compressed summary every recall reads first. Use it after the operator confirms something that makes the summary wrong or incomplete; never to record a guess. `Read Next` is generated and cannot be written here. Writes to disk and overwrites that section's previous contents, which are recoverable only from Git; every other section and the rest of the file are left untouched. Errors when the project or its Capsule is missing.

Input parameters:

- `body` (string, required): The section's new Markdown body, without the heading itself
- `project` (string, required): Project name, id, or trigger word
- `section` (string, required): Which capsule section to replace

### `append_rule` (~155 tokens)

Record a rule

Add a durable rule to a project's Rules note. Rules are standing constraints the operator has confirmed — how to work on this project, what never to assume — not observations about one conversation. Use `append_decision` instead for a choice that was made, and `update_capsule` when the summary itself is now wrong. Writes to disk: it appends and never edits existing rules, so calling it twice records the rule twice. Errors when the project or its Rules note is missing.

Input parameters:

- `name` (string, required): Short name for the rule, e.g. "Naming"
- `project` (string, required): Project name, id, or trigger word
- `rule` (string, required): The rule itself, in one or two sentences

### `vault_status` (~58 tokens)

Vault status

One-shot health summary: projects, note counts, doctor result, stale capsules, git state. Read-only — it inspects the working tree and reports, and writes nothing. Use `doctor` when you need every validation finding rather than the summary.

### `doctor` (~92 tokens)

Validate the vault

Run the full structural validation and return every finding: unresolved links, missing frontmatter, projects unreachable from the Recall Map, hubs that do not link what they own. Read-only — it reports and never repairs; repairing is `vulcanus doctor --repair` in a terminal. A finding is an error (structure the manifest requires is missing) or a warning (something added by hand that the manifest does not describe).

## Diagnostics

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

## Score history

- 2026-09-20: 94
- 2026-09-19: 93
- 2026-09-18: 93
- 2026-09-17: 96
- 2026-09-16: 96
- 2026-09-15: 95
- 2026-09-14: 95
- 2026-09-13: 96
- 2026-09-12: 95
- 2026-09-11: 95
- 2026-09-10: 94
- 2026-09-09: 94
- 2026-09-08: 93
- 2026-09-07: 93
- 2026-09-06: 93
- 2026-09-05: 92
- 2026-09-04: 92
- 2026-09-03: 91
- 2026-09-02: 91
- 2026-09-01: 90
- 2026-08-31: 90
- 2026-08-30: 89
- 2026-08-29: 89
- 2026-08-28: 88
- 2026-08-27: 88
- 2026-08-26: 87
- 2026-08-25: 86
- 2026-08-24: 85
- 2026-08-23: 85
- 2026-08-22: 84

## Common questions

### What is the Vulcanus MCP server?

Vulcanus is an MCP server listed in the public MCP registry as io.github.sunsatosolutions/vulcanus. A validated Markdown memory vault your coding agent can recall, project by project. This page covers its npm package (@sunsato/vulcanus).

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

Vulcanus scores 94 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 20 September 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 Vulcanus MCP server expose?

Vulcanus exposes 8 tools: recall, search, list_projects, append_decision, update_capsule, and 3 more. Their descriptions and schemas cost roughly 787 tokens of context every time the server is loaded.

### Is the Vulcanus MCP server still maintained?

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

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