MCP.Market

Vulcanus MCP server

by sunsatosolutions·io.github.sunsatosolutions/vulcanus·v0.6.3·5 stars
No reviews yet

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

A91/100grade A
Write a reviewInstall
What users say
No reviews yet
Be the first
Safety scan
A91/100

full report

Adoption
Growing

5 stars49 downloads/wk

Reviews

Write one

Nobody has reviewed Vulcanus yet.

If you have run it, two minutes of your experience saves the next person an afternoon.

Vulcanus tools (8, 2 write)

write = sends, deletes, buys or posts

Read from the package source without running it. The installed server may list more.

  • append_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. When it replaces an earlier decision, pass that decision's heading as `supersedes`: the new section records `supersedes::`, and the old one gains `superseded-by::` and `superseded-on::` under its heading but is otherwise left as history — never de

  • append_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. When it replaces an earlier rule, pass that rule's heading as `supersedes`; the old

  • doctorwrite action

    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 d

  • 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`.

  • recall

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

  • search

    Layer-aware text search across the vault. Capsule and Recall Map hits rank first so the cheapest sufficient note surfaces on top; hits inside superseded or expired sections carry a `state` and rank below every live hit. Read-only; prefer `recall` when you already know which project you need.

  • update_capsulewrite action

    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 th

  • 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.

Public scan report

scanner v0.1.10 · 2026-11-03 · same rubric, same numbers if you re-run it

no findings
  • Code scan149 source files scanned25/25
  • –Live reliabilityno gateway calls yet and no remote to proben/a
  • –Tool poisoningtools not inspected (local package is not executed); not countedn/a
  • Auth qualitylocal package, no credentials required12/15
  • Maintenancelast push 1 days ago15/15
  • Maintainer identityregistry namespace matches repository owner7/10
Overall 91/100. Components that don't apply are left out of the denominator. Any critical finding is an F.RubricAppeal a findingJSON

How Vulcanus compares

Against every graded AI and agents MCP server, from our own scans and uptime checks. Updated after each scan run.

Safety score
91/100
higher than 88% of 4,460 AI and agents servers
Tools
8
the typical AI and agents server has 6
Tools that change things
25%
typical: 0%. Fewer write tools means less an agent can break
GitHub stars
5
more than 78% of 2,711 AI and agents servers
Downloads a week
49
more than 41% of 1,538 AI and agents servers with a package

What its tools let an agent do: 6 read · 2 change

Release history: 3 versions in the registry since 2026-08-18, latest 2026-10-14, typically one every 49 days.

Install Vulcanus in Claude Code, Cursor or VS Code

Runs npx -y @sunsato/vulcanus on your machine. Read the scan report first; the gateway never runs local packages.

claude mcp add vulcanus -- npx -y @sunsato/vulcanus
Add to Cursor

What the publisher says

From the Vulcanus repository's README, as published. We do not edit it. Read it on GitHub

Vulcanus

Your coding agent starts every session cold. You re-explain the architecture, repeat decisions you already made, and watch it break a rule you set last week. The context lives in your head and in a scrollback buffer that is already gone.

Vulcanus fixes that at the source. It builds an AI-readable second brain — a Git-versioned vault of linked Markdown that you and your agents both read — and serves it over MCP, so an agent can recall a project instead of guessing at it.

npx @sunsato/vulcanus

You answer a few questions, and Vulcanus writes the whole vault — routing layer, operator profile, agent protocol, and one memory cluster per project — then validates that the graph actually holds together. Already keep an Obsidian vault? It adds the memory structure to that vault instead of creating a separate one.

Requires Node 22.12 or newer. Nothing leaves your machine: no account, no network call beyond an optional once-a-day version check.

A Sunsato product · vulcanus.sunsato.com

Why a vault and not a prompt

A CLAUDE.md that grows forever is the thing this replaces. It gets read in full on every task, it drifts out of date silently, and nothing checks that what it claims is still true.

A vault is layered instead, so recall is scoped: an agent reads the Recall Map, then the one Capsule its task needs, and goes deeper only for authority or detail. vulcanus stats measures that on your own vault — in the demo above, a task-scoped recall reads 59% less than the whole vault. vulcanus doctor then enforces that every link resolves and every project is reachable, so the memory fails loudly instead of rotting quietly.

Wire it to your agent

The vault is only worth as much as the recall it gives your tools, so that is one command each:

claude mcp add vulcanus -- vulcanus serve   # Claude Code, or any MCP client
vulcanus skills --install   # skills that run the real commands, in every repo
vulcanus agents             # the block to paste into a tool's global instructions

MCP server, Skills, and Making agents actually use it below cover what each one exposes.

What it creates

YourVault
├─ AGENTS.md              # the protocol AI agents must follow in this repo
├─ CLAUDE.md              # points Claude Code at that protocol
├─ USING-WITH-AI.md       # how to make every tool recall this vault
├─ README.md
├─ vulcanus.json          # the manifest everything is derived and validated from
├─ .claude/skills/        # invocable skills for Claude Code
├─ .agents/skills/        # the same skills for Codex, Cursor, and Gemini CLI
├─ 00_System/             # Index, Recall Map, Admin Profile, Rules, Update Format …
├─ 02_Projects/           # one cluster per project
└─ _imports/              # raw AI exports, ignored by Git

Each project cluster is five notes plus any specialized ones you ask for:

The point of the layering is token economy: an agent reads the Recall Map, then one Capsule, and only goes deeper when the task actually needs authority or detail.

What a project is, and who may hear about it

Two optional fields on each project in vulcanus.json carry what a note cannot enforce:

Shortened. The full README is on GitHub.

Nothing above is checked by us. What we check is on the safety report.

Vulcanus: common questions

Is Vulcanus MCP server safe?
Yes, by our scan: it is graded A (91/100). Read the Vulcanus safety report
How do I install Vulcanus?
It runs on your machine. Copy the Claude Code, Cursor, VS Code or Claude Desktop config from the install section.
Does Vulcanus need an API key?
Not as far as the registry entry and our scan can tell: no credentials are declared or required.
Is Vulcanus maintained?
The last commit was 2 days ago (2026-11-02). The latest release is v0.6.3.
What can I use instead of Vulcanus?
Servers from other publishers that do the same job: Total Agent Memory MCP server, Basic Memory MCP server and IWE (iwe.md) MCP server. Compare all Vulcanus alternatives.
How does Vulcanus compare with other AI and agents MCP servers?
safety score 91/100 (higher than 88% of 4,460 AI and agents servers); tools 8 (the typical AI and agents server has 6); tools that change things 25% (typical: 0%. Fewer write tools means less an agent can break). Full comparison.

Alternatives to Vulcanus

Same job from other publishers: the closest match first, then the best rated.

All Vulcanus alternatives →
  • Total Agent Memory
    Persistent local memory for coding agents: temporal knowledge graph, procedural and episodic recall
    A
  • Basic Memory
    Local-first knowledge management with bi-directional LLM sync via Markdown files.
    B
  • IWE (iwe.md)
    Markdown knowledge base as agent memory. Runs against the notes directory it is started in.
    A
  • Agent Recall
    Correction-first agent memory. Precision KPI tracks if agents heed warnings. 5 layers, local-only.
    A
  • Serena MCP: the IDE for your agent
    A powerful toolkit for coding, providing semantic retrieval and editing capabilities.
    C