Ext Ops Panel
Open dashboard
Comparison

Vault Cortex vs NeuroStack

Vault Cortex is an MCP server published by aliasunder. Marketplaces we read that list it: 1 (Official MCP Registry). NeuroStack is an MCP server published by raphasouthall. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-14. This pair was picked by a reader, not by our comparison rule, so search engines are asked not to index the page.

Where each is published

Where each is published
MarketplaceVault CortexNeuroStack
Official MCP Registry Listed
Version: 0.54.13
Forks (GitHub): 3
Stars (GitHub): 26
Not marked · First seen
Listed
Version: 0.12.0
Downloads/month (npm): 447
Downloads/week (npm): 41
Forks (GitHub): 5
Stars (GitHub): 47
Not marked · First seen

Each figure is the marketplace's own and is never added up across marketplaces. A marketplace that publishes no figure shows none: no number is not zero.

The facts side by side

Vault Cortex vs NeuroStack
FactVault CortexNeuroStack
Marketplaces that list it11
Stars (GitHub) (differs)26 (worse)47 (better)
Forks (GitHub) (differs)3 (worse)5 (better)
Last release (differs)2026-10-12Not published
Where it runs (differs)On your machine (ghcr.io/aliasunder/vault-cortex:0.54.13)Remote server (mcp.neurostack.sh/mcp)
TransportStreamable HTTPStreamable HTTP
Tools it declaresNot publishedNot published
Environment variables it asks for (differs)24, secrets among them: 11, secrets among them: 0
LicenceNot statedNot stated
Repository (differs)github.com/aliasunder/vault-cortexgithub.com/raphasouthall/neurostack
Changes in the last 7 days (differs)20
First seen2026-10-112026-10-11
Endpoint at the last check (differs)no remote endpoint we checknot checked yet

Lines where the two differ have a tinted background and bold values. Where the data itself says which value is better (more marketplaces, a larger figure of the same marketplace, a fresher release, a verified mark on a marketplace that lists both), the better one is also marked green with ▲ and the worse one red with ▼. Where it runs, the transport, the tools, the settings, hooks, the bundle's parts, the licence and the week's changes are marked only as different: more or fewer is not better in itself.

What each says it does

Vault Cortex

In its own words, on Official MCP Registry:

Standalone MCP server for Obsidian vaults — hybrid search, notes & files, memory, tasks, OAuth 2.1

NeuroStack

In its own words, on Official MCP Registry:

Token-efficient MCP memory for Markdown vaults. Tiered search, GraphRAG, AI memories.

How to run each

Vault Cortex

No data for an automatic command: what its marketplaces declare does not say unambiguously how to connect it.

Requires: MCP_AUTH_TOKEN (secret)

NeuroStack As a remote MCP server

Claude Code
claude mcp add --transport http neurostack https://mcp.neurostack.sh/mcp

Commands built only from what the marketplaces declare; the full set for every client is on each card.

Tools each declares

Neither one's marketplaces publish a list of tools, so there is nothing to compare.

Settings each asks for

Only Vault Cortex asks for

  • DAILY_NOTES_FOLDER
  • DAILY_NOTES_FORMAT
  • DISABLED_TOOLS
  • EMBEDDING_ENABLED
  • FILE_TOOLS_ENABLED
  • LOG_DIR
  • LOG_LEVEL
  • LOG_RETENTION_DAYS
  • MAX_FILE_BYTES
  • MAX_IMAGE_OUTPUT_BYTES
  • MAX_PDF_RENDER_PAGES
  • MCP_AUTH_TOKEN (secret)
Show the remaining 12
  • MEMORY_DIR
  • MEMORY_ENABLED
  • ORPHAN_EXCLUDE_FOLDERS
  • PROTECTED_PATHS
  • PUBLIC_URL
  • READONLY_MODE
  • RERANK_MODE
  • SERVICE_DOCUMENTATION_URL
  • TRUST_FORWARDED_HOPS
  • TRUST_PROXY_HOPS
  • TZ
  • WINDOWS_MODE

Only NeuroStack asks for

  • NEUROSTACK_VAULT_ROOT

Settings as each marketplace publishes them. Asking for fewer is not better in itself.

What it can do: Vault Cortex · What it can do: NeuroStack · Compare two other plugins

Data comes from the Official MCP Registry (registry.modelcontextprotocol.io), CC0 1.0. Figures come from our own regular passes over the marketplaces, last read on . We publish no contact details for plugin publishers.

Where the data comes from: how the catalog is built