# vtimestamp [Health: Active]

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

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

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

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

**Requires environment variables:** `VERUS_RPC_URL`, `VERUS_CONF_PATH`, `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 the vtimestamp MCP server does

The vtimestamp MCP server gives MCP-compatible agents read access to vtimestamp records published on the Verus blockchain. It supports two main inspection tasks: checking whether a file or text matches a timestamp associated with a VerusID, and listing all timestamps recorded for that identity. A separate information tool returns details about the vtimestamp service.

The server is read-only. It does not publish timestamps, require a wallet, or access private keys. Applications that need to create records must use the separate write server referenced by the project documentation.

## How it works

For verification, the server accepts either a local file path or a text string, but not both. It calculates the input's SHA-256 hash and compares that value with records stored under the requested VerusID. Listing uses Verus identity history to retrieve the timestamp entries associated with that identity.

The local MCP process communicates with an agent over stdio using JSON-RPC. It then sends Verus RPC requests over HTTPS by default. The public mainnet configuration uses `rpc.vrsc.syncproof.net` as its primary endpoint and `api.verus.services` as a fallback.

Records can use either the newer public-encrypted format or an older plaintext format. The reader selects the appropriate handling based on each record's flags, so identities containing entries from both writing versions can still be inspected together. Public-encrypted records use on-chain data needed for decryption; they do not require a separately shared key.

## Setup and configuration

Node.js 18 or newer is required. Install the server through an MCP client using `npx`, or use the documented Yarn or pnpm alternatives. Claude Desktop, Claude Code, and VS Code configuration examples are provided in the project documentation.

No environment variables are needed for the default public mainnet mode. To use a local Verus daemon, set `VERUS_RPC_URL`, or provide `VERUS_CONF_PATH` so the server can derive the local RPC address and credentials. `VERUS_RPC_USER` and `VERUS_RPC_PASSWORD` can override credentials when needed.

A local daemon is required for testnet encrypted reads. The daemon must be running on the host selected by the configuration, such as a `verusd` process using the VRSCTEST chain.

## Tools and capabilities

The vtimestamp MCP server exposes these tools:

- `vtimestamp_verify`: checks a file or text value against a VerusID's timestamp records. Required input includes `identity` and exactly one of `file_path` or `text`.
- `vtimestamp_list`: returns the timestamps associated with a supplied VerusID. It requires only `identity`.
- `vtimestamp_info`: returns information about the vtimestamp service and takes no parameters.

These tools are suited to agent workflows that need to validate a report, statement, or other content against an on-chain timestamp, or review what an identity has previously recorded.

## Limitations and notes

The public configuration is for Verus mainnet. The fallback endpoint does not support the `decryptdata` RPC method, so encrypted entries may be reported as unavailable if the primary endpoint cannot be reached; legacy plaintext entries can still be read. Testnet encrypted inspection therefore requires a local daemon.

The vtimestamp MCP server does not create timestamps or modify blockchain data. It also does not provide authentication, wallet management, or private-key handling. High-volume use and privacy-sensitive inspection are better directed to a local daemon rather than the public RPC endpoints.

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