Vulcanus
NPM · @SUNSATO/VULCANUS · SCANNED SEP 20
A validated Markdown memory vault your coding agent can recall, project by project.
Available components
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 102 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency97
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Cryptographically verified build provenance (signed, bound to sunsatosolutions/Vulcanus). View diagnostics → Pass
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 32 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability83
- AI-judged instruction clarity (excellent).Pass
- Tool/resource definitions use about 787 tokens (~98/item across 8 items; 8 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management87
- Stability observed for 26 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
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 Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 8 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 8 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
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.
npm · @sunsato/vulcanus
claude mcp add sunsatosolutions-vulcanus -- npx -y @sunsato/vulcanus
{
"mcpServers": {
"sunsatosolutions-vulcanus": {
"command": "npx",
"args": [
"-y",
"@sunsato/vulcanus"
]
}
}
} {
"servers": {
"sunsatosolutions-vulcanus": {
"command": "npx",
"args": [
"-y",
"@sunsato/vulcanus"
]
}
}
} codex mcp add sunsatosolutions-vulcanus -- npx -y @sunsato/vulcanus
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"sunsatosolutions-vulcanus": {
"type": "local",
"command": [
"npx",
"-y",
"@sunsato/vulcanus"
],
"enabled": true
}
}
} openclaw mcp add sunsatosolutions-vulcanus --command npx --arg -y --arg @sunsato/vulcanus
mcp_servers:
sunsatosolutions-vulcanus:
command: "npx"
args: ["-y", "@sunsato/vulcanus"] {
"McpServers": {
"sunsatosolutions-vulcanus": {
"Transport": "stdio",
"Command": "npx",
"Arguments": [
"-y",
"@sunsato/vulcanus"
]
}
}
} assistant mcp add sunsatosolutions-vulcanus -t stdio -c npx -a -y @sunsato/vulcanus
{
"mcpServers": {
"sunsatosolutions-vulcanus": {
"command": "npx",
"args": [
"-y",
"@sunsato/vulcanus"
]
}
}
} 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.
- 20 Sept 26 +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.
- 18 Sept 26 −3
- Stability: pass → 0.80 functional
- 16 Sept 26 +1
- Stability: 0.97 → pass security
- 14 Sept 26 −1
- Stability: pass → 0.93 functional
- 13 Sept 26 +1
- Stability: 0.97 → pass security
- 11 Sept 26 +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.
- 9 Sept 26 +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.
- 6 Sept 26 +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.
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 20 Sept 2026 · Analysed npm/@sunsato/vulcanus@0.5.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 | sunsatosolutions/Vulcanus |
| Certificate issuer | https://token.actions.githubusercontent.com |
| Certificate SAN | https://github.com/sunsatosolutions/Vulcanus/.github/workflows/release.yml@refs/tags/v0.5.0 |
| Rekor log index | 2501021872 |
| Predicate type | https://slsa.dev/provenance/v1 |
| Subject digest | sha512:9621749578d60420af40684b311ade096f8eb25882bf414719b3506265fc3d436871cec592456d50c1a0bbb12b94461a34a00e0d62ffdce8a12b5eab5 |
Background: How many MCP packages publish verified provenance →
Dependencies 102 packages
| Packages resolved | 102 |
|---|---|
| Stale | 31 |
| 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 →
append_decision Record a decision ~138
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.
| Name | Type | Req | Description |
|---|---|---|---|
| decision | string | yes | The decision itself, one or two sentences |
| details | string | – | Optional supporting details |
| project | string | yes | Project name, id, or trigger word |
| title | string | yes | Short heading for the decision |
No output schema declared.
No examples provided.
append_rule Record a rule ~155
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.
| Name | Type | Req | Description |
|---|---|---|---|
| name | string | yes | Short name for the rule, e.g. "Naming" |
| project | string | yes | Project name, id, or trigger word |
| rule | string | yes | The rule itself, in one or two sentences |
No output schema declared.
No examples provided.
doctor Validate the vault ~92
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).
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
list_projects List projects ~48
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`.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
recall Recall a project ~78
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.
| Name | Type | Req | Description |
|---|---|---|---|
| project | string | yes | Project name, id, or trigger word |
No output schema declared.
No examples provided.
search Search the vault ~72
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.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | Max hits, default 20 |
| query | string | yes | Text to look for |
No output schema declared.
No examples provided.
update_capsule Refresh a capsule section ~146
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.
| Name | Type | Req | Description |
|---|---|---|---|
| body | string | yes | The section's new Markdown body, without the heading itself |
| project | string | yes | Project name, id, or trigger word |
| section | string | yes | Which capsule section to replace |
No output schema declared.
No examples provided.
vault_status Vault status ~58
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.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
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.