verify-proof vs io.github.vdappdev2/vtimestamp-write
verify-proof is an MCP server published by csolomon0704-prog. Marketplaces we read that list it: 1 (Official MCP Registry). io.github.vdappdev2/vtimestamp-write 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
| Marketplace |  verify-proof |  io.github.vdappdev2/vtimestamp-write |
|---|---|---|
| Official MCP Registry | Listed Version: 0.4.0 Downloads/month (PyPI): 410 Downloads/week (PyPI): 29 Forks (GitHub): 0 Stars (GitHub): 0 Not marked · First seen |
Listed Version: 1.0.0 Downloads/month (npm): 149 Downloads/week (npm): 17 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 | verify-proof | io.github.vdappdev2/vtimestamp-write |
|---|---|---|
| Marketplaces that list it | 1 | 1 |
| Stars (GitHub) | 0 | 0 |
| Forks (GitHub) | 0 | 0 |
| Last release (differs) | 2026-10-19 | Not published |
| Where it runs (differs) | On your machine (verify-proof) | On your machine (vtimestamp-mcp-write) |
| Transport | stdio | stdio |
| Tools it declares | Not published | Not published |
| Environment variables it asks for (differs) | Not published | 4, secrets among them: 2 |
| Licence | Not stated | Not stated |
| Repository (differs) | github.com/fulcrum-enterprises/verify-proof | github.com/vdappdev2/vtimestamp-mcp-write |
| Changes in the last 7 days (differs) | 5 | 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
verify-proof
Verify timestamp proofs offline, anchor hashes through ProofLedger, keep agent run receipts.
io.github.vdappdev2/vtimestamp-write
MCP server for creating vtimestamp proofs on the Verus blockchain via a local or remote daemon
How to run each
verify-proof As a local MCP server: PyPI package
claude mcp add --transport stdio verify-proof -- uvx verify-proofio.github.vdappdev2/vtimestamp-write As a local MCP server: npm package
claude mcp add --env "VERUS_RPC_PASSWORD=<YOUR_VERUS_RPC_PASSWORD>" --env "VERUS_RPC_URL=<YOUR_VERUS_RPC_URL>" --env "VERUS_RPC_USER=<YOUR_VERUS_RPC_USER>" --transport stdio vtimestamp-write -- npx -y vtimestamp-mcp-writeRequires: VERUS_RPC_PASSWORD (secret), VERUS_RPC_URL, VERUS_RPC_USER (secret)
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 verify-proof publish no settings it asks for, so we do not compare settings.
What it can do: verify-proof · What it can do: io.github.vdappdev2/vtimestamp-write · 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.