Vtimestamp logo

Vtimestamp

Verifies Verus document timestamps, lists identity history, and reads public or local Verus blockchain data.

Install Vtimestamp

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": {
      "command": "npx",
      "args": [
        "-y",
        "vtimestamp-mcp@latest"
      ],
      "env": {
        "VERUS_RPC_URL": "YOUR_VALUE_HERE",
        "VERUS_CONF_PATH": "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

The vtimestamp MCP server verifies files and text against timestamp records on the Verus blockchain. It computes SHA-256 hashes locally, queries Verus identity history, and lists timestamps associated with a VerusID. Use it when an agent needs to check document provenance or inspect an identity's timestamp records without writing new records. Default operation uses a public mainnet RPC and requires no wallet or API credentials.

Use cases

  • Verify a PDF or other local file against a VerusID
  • Check whether text was timestamped on-chain
  • List all timestamps associated with a VerusID
  • Inspect encrypted testnet records through a local daemon

Key features

  • Verify files and text with SHA-256 hashing
  • Query timestamp records by VerusID
  • Read legacy plaintext and public-encrypted entries
  • Use public mainnet RPC endpoints by default
  • Connect to a local Verus daemon
  • Support mainnet and configured testnet reads

Security & health

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

ActiveLast checked 1d ago

Recent health check succeeded.

10/10 checks healthy over the last 57d

Supply-chain signal

No high-severity advisories surfaced by our automated scan.

Critical 0High 0Medium 0Low 0

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

Adoption & maintenance

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

npm downloads134Package downloads in the last 30 days.
Last commit5mo agoMost recent push to the default branch.

How Vtimestamp works

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.

Reviews

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

Frequently Asked Questions about Vtimestamp

vtimestamp is an MCP server that connects AI agents to vtimestamp records on the Verus blockchain. Its main tools verify a file or text against a VerusID, list timestamps recorded for that identity, and provide service information. It reads through public or configured local Verus RPC endpoints.

Install it through your MCP client with `npx vtimestamp-mcp@latest`. Claude Code uses `claude mcp add` with stdio, while Claude Desktop and VS Code use JSON configuration containing the `npx` command and package argument.

Yes, vtimestamp works with Claude Desktop through a standard stdio MCP configuration. Add a server entry that runs `npx -y vtimestamp-mcp@latest`, or use the documented Yarn or pnpm command alternatives.

Yes, the `vtimestamp_verify` tool accepts either a file path or text and requires a VerusID. It computes a SHA-256 hash and checks that value against the identity's on-chain timestamp records; the two input modes are mutually exclusive.

Use a local Verus daemon for testnet, because public testnet RPC endpoints do not support encrypted record decryption. Set `VERUS_CONF_PATH`, or provide `VERUS_RPC_URL` with RPC credentials, and ensure a VRSCTEST daemon is running.

Related MCP servers

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 AllMCPs Directory Badge
Markdown (GitHub README)
[![AllMCPs](https://allmcps.com/api/badge/vtimestamp?style=directory)](https://allmcps.com/mcp/vtimestamp)
HTML Embed
<a href="https://allmcps.com/mcp/vtimestamp"><img src="https://allmcps.com/api/badge/vtimestamp?style=directory" alt="Vtimestamp on AllMCPs" /></a>