Ext Ops Panel
Open dashboard
Comparison

FastMCP server for bidirectional sync between personal and team Obsidian vaults vs io.github.vdappdev2/vtimestamp

FastMCP server for bidirectional sync between personal and team Obsidian vaults is an MCP server published by adelaidasofia. Marketplaces we read that list it: 1 (Official MCP Registry). io.github.vdappdev2/vtimestamp is an MCP server published by vdappdev2. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-20. 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
MarketplaceFastMCP server for bidirectional sync between personal and team Obsidian vaultsio.github.vdappdev2/vtimestamp
Official MCP Registry Listed
Version: 0.1.0
Forks (GitHub): 0
Stars (GitHub): 0
Not marked · First seen
Listed
Version: 1.0.1
Downloads/month (npm): 172
Downloads/week (npm): 31
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

FastMCP server for bidirectional sync between personal and team Obsidian vaults vs io.github.vdappdev2/vtimestamp
FactFastMCP server for bidirectional sync between personal and team Obsidian vaultsio.github.vdappdev2/vtimestamp
Marketplaces that list it11
Stars (GitHub)00
Forks (GitHub)00
Last releaseNot publishedNot published
Where it runs (differs)On your machine (https://github.com/adelaidasofia/vault-sync-mcp/releases/download/v0.1.0/vault-sync-mcp.mcpb)On your machine (vtimestamp-mcp)
Transportstdiostdio
Tools it declaresNot publishedNot published
Environment variables it asks for (differs)2, secrets among them: 0Not published
LicenceNot statedNot stated
Repository (differs)github.com/adelaidasofia/vault-sync-mcpgithub.com/vdappdev2/vtimestamp-mcp
Changes in the last 7 days (differs)20
First seen2026-10-112026-10-11

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

FastMCP server for bidirectional sync between personal and team Obsidian vaults

In its own words, on Official MCP Registry:

FastMCP server for bidirectional sync between personal and team Obsidian vaults.

io.github.vdappdev2/vtimestamp

In its own words, on Official MCP Registry:

MCP server for verifying and querying vtimestamp proofs on the Verus blockchain

How to run each

FastMCP server for bidirectional sync between personal and team Obsidian vaults

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

Requires: PERSONAL_VAULT_PATH, TEAM_VAULT_PATH

io.github.vdappdev2/vtimestamp As a local MCP server: npm package

Claude Code
claude mcp add --transport stdio vtimestamp -- npx -y vtimestamp-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

The marketplaces of io.github.vdappdev2/vtimestamp publish no settings it asks for, so we do not compare settings.

What it can do: FastMCP server for bidirectional sync between personal and team Obsidian vaults · What it can do: io.github.vdappdev2/vtimestamp · 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