Ext Ops Panel
Open dashboard
Comparison

io.github.Evanciel/stellavault vs io.github.IsaiahDupree/second-brain-bridge

io.github.Evanciel/stellavault is an MCP server published by Evanciel. Marketplaces we read that list it: 1 (Official MCP Registry). io.github.IsaiahDupree/second-brain-bridge is an MCP server published by IsaiahDupree. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-29. 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
Marketplaceio.github.Evanciel/stellavaultio.github.IsaiahDupree/second-brain-bridge
Official MCP Registry Listed
Version: 0.9.0
Downloads/month (npm): 301
Downloads/week (npm): 21
Forks (GitHub): 2
Stars (GitHub): 5
Not marked · First seen
Listed
Version: 1.3.0
Forks (GitHub): 0
Stars (GitHub): 0
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

io.github.Evanciel/stellavault vs io.github.IsaiahDupree/second-brain-bridge
Factio.github.Evanciel/stellavaultio.github.IsaiahDupree/second-brain-bridge
Marketplaces that list it11
Stars (GitHub) (differs)5 (better)0 (worse)
Forks (GitHub) (differs)2 (better)0 (worse)
Last releaseNot publishedNot published
Where it runs (differs)On your machine (stellavault)Remote server (secondbrainbridge.vercel.app/mcp)
Transport (differs)stdioStreamable HTTP
Tools it declaresNot publishedNot published
Environment variables it asks for (differs)1, secrets among them: 0Not published
Licence (differs)MITNot stated
Repository (differs)github.com/evanciel/stellavaultgithub.com/isaiahdupree/second-brain-bridge
Changes in the last 7 days00
First seen2026-10-112026-10-11
Endpoint at the last check (differs)no remote endpoint we checkResponded 4 days ago, requires a key

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

io.github.Evanciel/stellavault

In its own words, on Official MCP Registry:

Local-first MCP server: Claude searches, asks & drafts from your Obsidian vault. 21 tools, no keys.

io.github.IsaiahDupree/second-brain-bridge

In its own words, on Official MCP Registry:

Search and reason over your Obsidian-style Markdown vault, right from ChatGPT.

How to run each

io.github.Evanciel/stellavault As a local MCP server: npm package

Claude Code
claude mcp add --transport stdio stellavault -- npx -y stellavault serve

io.github.IsaiahDupree/second-brain-bridge As a remote MCP server

Claude Code
claude mcp add --transport http second-brain-bridge https://secondbrainbridge.vercel.app/mcp

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

Only io.github.IsaiahDupree/second-brain-bridge has a remote endpoint we check. How we check endpoints

Tools each declares

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

Settings each asks for

The marketplaces of io.github.IsaiahDupree/second-brain-bridge publish no settings it asks for, so we do not compare settings.

What it can do: io.github.Evanciel/stellavault · What it can do: io.github.IsaiahDupree/second-brain-bridge · Compare two other plugins

Data comes from the Official MCP Registry (registry.modelcontextprotocol.io), CC0 1.0. Data comes from public marketplace files in GitHub repositories of their authors. 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