# vtimestamp-write [Health: Active]

**Category:** 🔑 Cryptography  
**Repository:** https://github.com/vdappdev2/vtimestamp-mcp-write  
**GitHub Stars:** 0  
**npm Downloads (last month):** 112  
**Views:** 0  
**Installs:** 0  
**Upvotes:** 0  
**Directory Page:** https://allmcps.com/mcp/vtimestamp-write

## Description
MCP server for creating vtimestamp proofs on the Verus blockchain via a local or remote daemon

## Tools
Capabilities this server exposes over MCP:

- **InvalidParams**

## Claude Desktop Quick Installation
Install path detected from listing signals. Uses `npx` (confidence: high):

```json
"mcpServers": {
  "vtimestamp-write": {
    "command": "npx",
    "args": ["-y","vtimestamp-mcp-write@latest"],
    "env": {
      "VERUS_CONF_PATH": "",
      "VERUS_RPC_URL": "",
      "VERUS_RPC_USER": "",
      "VERUS_RPC_PASSWORD": ""
    }
  }
}
```

**Requires environment variables:** `VERUS_CONF_PATH`, `VERUS_RPC_URL`, `VERUS_RPC_USER`, `VERUS_RPC_PASSWORD` — the values above are empty placeholders; fill in real credentials before running (see the repository for what each one is for).

## Documentation

## 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.

_Full upstream README: https://allmcps.com/mcp/vtimestamp-write/readme_