Log inSubmit server
Vtimestamp Write logo

Vtimestamp Write

Creates Verus blockchain timestamps from files or text through a local or remote Verus daemon.

InstallRepositoryWebsite
Full README Compare alternatives Embed widget Claim this listing

Install Vtimestamp Write

Pick your client, then add it in one click or paste the config.

STDIONode.js
~/Library/Application Support/Claude/claude_desktop_config.json
claude_desktop_config.json
{
  "mcpServers": {
    "vtimestamp-write": {
      "command": "npx",
      "args": [
        "-y",
        "vtimestamp-mcp-write@latest"
      ],
      "env": {
        "VERUS_CONF_PATH": "YOUR_VALUE_HERE",
        "VERUS_RPC_URL": "YOUR_VALUE_HERE",
        "VERUS_RPC_USER": "YOUR_VALUE_HERE",
        "VERUS_RPC_PASSWORD": "YOUR_VALUE_HERE"
      }
    }
  }
}

Settings → Developer → Edit Config, merge this into mcpServers, then fully quit and reopen Claude Desktop.

Values are written into the snippet above so you can paste it as is. They never leave your browser.

Install not yet sandbox-tested— we haven't run this command through our automated sandbox yet. Not a red flag; we're working through the catalog.

Overview

vtimestamp-write MCP server creates on-chain document proofs on the Verus blockchain through a local or remote Verus daemon. Its `vtimestamp_create` tool accepts either a file path or text, hashes the content with SHA-256, and submits an `updateidentity` transaction for a VerusID. The daemon wallet must contain the identity's private key, and each write incurs a transaction fee. Use it when an agent needs to record document or attestation hashes on a VerusID rather than only read existing timestamps.

Use cases

  • Timestamp a report file on a VerusID
  • Record an attestation hash on-chain
  • Create proofs for text supplied by an agent
  • Submit timestamps through a remote Verus daemon

Key features

  • Creates Verus blockchain timestamp proofs
  • Accepts files or text as input
  • Computes SHA-256 hashes automatically
  • Supports local and remote Verus daemons
  • Stores timestamp metadata under a VerusID
  • Allows configurable funding addresses and fees

Tools1

What Vtimestamp Write lets your agent do. Expand a tool for its parameters.

Self-reported~3 tokens of context

Security & health

What it can reach and how reliably it runs — from our own checks, not the maintainer’s claims.

ActiveLast checked Today

Recent health check succeeded.

7/7 checks healthy over the last 44d

Supply-chain signal

No high-severity advisories surfaced by our automated scan.

Critical 0High 0Medium 0Low 0

Scanned 6d ago via OSV.dev · vtimestamp-mcp-write@latest (npm)

Adoption & maintenance

Factual signals from GitHub, npm, and our automated checks — not a rating.

npm downloads112Package downloads in the last 30 days.
Last commit5mo agoMost recent push to the default branch.
Tools exposed1Callable tools this server registers over MCP.

How Vtimestamp Write works

What vtimestamp-write MCP server does

The vtimestamp-write MCP server lets an MCP-compatible agent create timestamp proofs for content associated with a VerusID.

Each request requires an identity name and title. Optional metadata includes a description, original filename, file size, funding source, and fee offer. A successful result includes the identity, calculated hash, title, transaction ID, and a success indicator. Duplicate hashes, missing files, unknown identities, and daemon failures are reported as errors.

The server is intended for write operations. A separate read-only vtimestamp-mcp package is referenced for inspecting and verifying timestamps.

How vtimestamp-write MCP server works

The agent communicates with the locally running MCP process over stdio using JSON-RPC. The process then calls the Verus daemon over authenticated HTTP JSON-RPC. The daemon signs and broadcasts the updateidentity transaction, so the identity's private key must already be imported into the daemon wallet.

The server can write through a daemon on the same machine or through a remote daemon. Since the write is recorded on-chain, it requires a fee; the default fee offer is 0.0001 VRSC. The sourceoffunds option can select the address that pays the fee.

From version 1.2.0, vtimestamp-write stores timestamp metadata as a publicly decryptable entry under the VerusID's contentmultimap. The metadata is grouped into one encrypted message containing fields such as the hash, title, description, filename, and file size. The encryption is public, so readers do not need wallet access or shared keys, but recovering the fields requires the originating transaction ID and a daemon decryptdata call. Older plaintext entries remain readable by the corresponding read server.

Setup and configuration

The vtimestamp-write MCP server requires Node.js 18 or newer and a running verusd instance with RPC access enabled. For local use, it reads credentials automatically from VRSC.conf. The expected locations are the Komodo application-data path on macOS and Windows, or ~/.komodo/VRSC/VRSC.conf on Linux.

Install it with an MCP client using the package command npx vtimestamp-mcp-write@latest. The README provides configurations for Claude Desktop, Claude Code, and VS Code.

For a remote daemon, configure the daemon to allow the client IP and make RPC port 27486 reachable. Set VERUS_RPC_URL, VERUS_RPC_USER, and VERUS_RPC_PASSWORD for the connection, or set VERUS_CONF_PATH when the configuration file is stored in a nonstandard location. RPC credentials are sent over plain HTTP; an SSH tunnel is recommended when the daemon is reached over the public internet.

Tools and capabilities

vtimestamp_create creates one timestamp for a VerusID. Supply exactly one of these inputs:

  • file_path: a file to hash; filename and size can be detected automatically.
  • text: text such as an attestation or report to hash.

The tool also accepts identity, title, optional description, filename, filesize, sourceoffunds, and feeoffer. A file path and text cannot be used together. The server reports an invalid-parameter error when a referenced file is unavailable.

Limitations and notes

The daemon must hold the identity's private key because creating a timestamp signs an on-chain transaction. Writes cost VRSC and can fail if the identity is unavailable, the hash already exists, or the daemon returns an RPC error. The server connects only to the configured daemon; remote deployments should avoid exposing unauthenticated RPC directly. Public-encrypted entries are readable by anyone with daemon access capable of performing the required decryption, so this server should not be treated as a mechanism for keeping timestamp metadata private.

Read the full README View source on GitHub

Reviews

No reviews yet — be the first to share how it worked for you.

Frequently Asked Questions about Vtimestamp Write

vtimestamp-write is an MCP server that connects AI agents to a local or remote Verus daemon and creates on-chain timestamp proofs. Its main tool, `vtimestamp_create`, hashes a file or text with SHA-256 and writes the result to a VerusID. The daemon wallet must hold the identity's private key.

Install it through an MCP client with `npx vtimestamp-mcp-write@latest`. The README includes stdio configurations for Claude Desktop, Claude Code, and VS Code. Node.js 18 or newer and a running Verus daemon with RPC access are required.

Set `VERUS_RPC_URL`, `VERUS_RPC_USER`, and `VERUS_RPC_PASSWORD` in the MCP configuration. The daemon must allow the client IP and expose RPC port 27486. Because credentials use plain HTTP, the documentation recommends an SSH tunnel for connections over the public internet.

Yes, it accepts either `file_path` or `text`, but not both in the same request. The server computes the SHA-256 hash automatically and can infer a file's filename and size when a file path is used.

Related MCP servers

All in Cryptography All alternatives
Add a badge to your READMEShow it’s listed — live SVG, Markdown or HTML.

AllMCPs Directory Badge

Full Badge Customizer

Showcase your server listing on GitHub or your project documentation. Embed this dynamic SVG badge to highlight official listing status and live engagement.

Badge Style:
Live Dynamic SVG PreviewVtimestamp Write AllMCPs Directory Badge
Markdown (GitHub README)
[![AllMCPs](https://allmcps.com/api/badge/vtimestamp-write?style=directory)](https://allmcps.com/mcp/vtimestamp-write)
HTML Embed
<a href="https://allmcps.com/mcp/vtimestamp-write"><img src="https://allmcps.com/api/badge/vtimestamp-write?style=directory" alt="Vtimestamp Write on AllMCPs" /></a>