io.github.beepboop2025/umbra-proof vs io.github.vdappdev2/vtimestamp
io.github.beepboop2025/umbra-proof is an MCP server published by beepboop2025. 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-22. 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
| Marketplace |  io.github.beepboop2025/umbra-proof |  io.github.vdappdev2/vtimestamp |
|---|---|---|
| Official MCP Registry | Listed Version: 0.1.2 Forks (GitHub): 0 (last published figure) Stars (GitHub): 1 (last published figure) 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
| Fact | io.github.beepboop2025/umbra-proof | io.github.vdappdev2/vtimestamp |
|---|---|---|
| Marketplaces that list it | 1 | 1 |
| Stars (GitHub) (differs) | 1 (last published figure) | 0 |
| Forks (GitHub) (differs) | 0 (last published figure) | 0 |
| Last release | Not published | Not published |
| Where it runs (differs) | On your machine (ghcr.io/beepboop2025/umbra-proof-mcp:v0.1.2) | On your machine (vtimestamp-mcp) |
| Transport | stdio | stdio |
| Tools it declares | Not published | Not published |
| Environment variables it asks for | Not published | Not published |
| Licence | Not stated | Not stated |
| Repository (differs) | github.com/beepboop2025/umbra-xmr-bridge | github.com/vdappdev2/vtimestamp-mcp |
| Changes in the last 7 days | 0 | 0 |
| First seen | 2026-10-11 | 2026-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
io.github.beepboop2025/umbra-proof
Verify Umbra bridge accountability proofs (signed receipts, checkpoints, Merkle inclusion).
io.github.vdappdev2/vtimestamp
MCP server for verifying and querying vtimestamp proofs on the Verus blockchain
How to run each
io.github.beepboop2025/umbra-proof As a local MCP server: Docker image
claude mcp add --transport stdio umbra-proof -- docker run -i --rm ghcr.io/beepboop2025/umbra-proof-mcp:v0.1.2io.github.vdappdev2/vtimestamp As a local MCP server: npm package
claude mcp add --transport stdio vtimestamp -- npx -y vtimestamp-mcpCommands 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
Neither one's marketplaces publish the settings it asks for.
What it can do: io.github.beepboop2025/umbra-proof · 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. Figures come from our own regular passes over the marketplaces, last read on . We publish no contact details for plugin publishers.