Vtimestamp

Name: Vtimestamp
Author: vdappdev2

by vdappdev2version 1.0.1i★ –iRuns on your computer

Registry nameio.github.vdappdev2/vtimestamp

Install

Overview

Description from the maker (original English)

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

PopNx MCP’s three pillars

These three are never merged into one score: opinions, measurements and popularity are different things.

User voiceiNo reviews yetReviews open together with accounts in a later step
Our basic checksi1 of 1 passedChecked from public information; code not scanned yet
UsageiNot measured yet★ –

What you can do with it

We have not written a plain-language summary for this one yet. Below are the facts we read from the registry.

Connection: Runs on your computer
Transport: stdio
Category: Other

Install

Pick the AI app you use, then copy the settings.

Before you install

Basic checks: 1 of 1 passed
Runs on your computer with your user’s permissions (files, network, apps).
The registry lists no key to fill in.

You need

npmNode.js installed (for the npx command)

Which app do you use?

ClaudeClaude CodeCursorVS CodeChatGPT

Pick your app above. We remember it, so next time the button says “Install in …”.

Open Claude Desktop → Settings → Developer → Edit Config, and paste this into claude_desktop_config.json

{
  "mcpServers": {
    "vtimestamp": {
      "command": "npx",
      "args": [
        "-y",
        "vtimestamp-mcp"
      ]
    }
  }
}

Run this in your terminal

claude mcp add vtimestamp -- npx -y vtimestamp-mcp

Open in Cursor

Or copy the settings yourself

Paste into .cursor/mcp.json in your project, or ~/.cursor/mcp.json

{
  "mcpServers": {
    "vtimestamp": {
      "command": "npx",
      "args": [
        "-y",
        "vtimestamp-mcp"
      ]
    }
  }
}

Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.

Open in VS Code

Or copy the settings yourself

Paste into .vscode/mcp.json in your project

{
  "servers": {
    "vtimestamp": {
      "type": "stdio",
      "command": "npx",
      "args": [
        "-y",
        "vtimestamp-mcp"
      ]
    }
  }
}

Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.

This one runs on your computer, and ChatGPT can only connect to servers on the internet. Pick another app.

Your choice stays on this device in a cookie; no account needed.

These settings are generated from the maker’s registry entry. If the README says otherwise, follow the README.

What it can do

Runs on your computer; the tool list appears in your AI app after you install it.

Basic checksi

We check information anyone can see; we have not read the code. Checks that do not apply are left out of the count. · Checked Nov 6, 2026

✓ Pass
Maker matches the repo
The registry name was verified with the GitHub account vdappdev2, which owns the repo
… Not checked yet
Still maintained
We have not read this repo from GitHub yet
… Not checked yet
Has a licence
We have not read this repo from GitHub yet
– Not applicable
Endpoint responds
This one runs on your computer; there is no internet endpoint
– Not applicable
Sign-in with OAuth
Runs on your computer and uses local settings instead
… Not checked yet
No hidden instructions in tool descriptions
Runs on your computer; we can only read tool lists from internet endpoints

Compared with others in Otheri

More stars than 0% of the other 32384 servers in this category
Published to the registry more recently than 3% of the other 32384 servers in this category
Basic checks equal to or better than 100% of the other 32384 servers in this category

Compared with every active server in this category in the registry. Stars count only when the publisher owns the repo.

Common questions

Is Vtimestamp safe?

It passed 1 of 1 applicable basic checks. We have not read the code. Before adding a key or token, see what access the server asks for and use a key with only the permissions you need.

What keys or codes does it need?

The registry does not list a required key, though some servers ask you to sign in on first use.

Does it run on my computer or in the cloud?

It runs on your computer. Your AI app starts it when needed, and data does not pass through the maker’s servers (unless it calls an online service itself).

Is it still maintained?

The GitHub repo last changed –, and the latest version (1.0.1) reached the registry 8 months ago.

Which apps can use it?

Apps that support MCP, such as Claude Desktop, Claude Code, Cursor and VS Code. You also need Node.js on your computer.

What can I use instead?

In the same category: Spec Driven Development, Remote Desktop Commander, 오늘냥이 (Oneul Nyangi)

Alternatives

Servers in the same category from other makers, sorted by stars.

Reading a card:★ GitHub starsiThree pillars: reviews · checks · usageiUpdated = latest version published to the registryi

Spec Driven Development

by formulahendry

MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.

Runs on your computer★ 440MITUpdated 14 months ago

Install

Remote Desktop Commander

by desktop-commander

Remote Desktop Commander: use files, terminal and processes on your own computers from any AI app.

Runs in the cloud★ 211Updated yesterday

Install

오늘냥이 (Oneul Nyangi)

by nyangi.today

Real cat photos, diaries, profiles, age and food reference calculators, and breeds.

Runs in the cloudUpdated today

Install

README from the maker

Open the README

Copied from the maker’s repo as written. PopNx MCP has not reviewed or endorsed it. HTML, images and scripts are removed. Links lead off this site.

vtimestamp-mcp

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

Enables AI agents (Claude Desktop, VS Code, etc.) to verify document timestamps and list all timestamps on a VerusID — directly from the blockchain.

Looking for the write server? See vtimestamp-mcp-write — needs a local daemon and a wallet with the identity's private key.

Installation

Claude Code

claude mcp add --transport stdio --scope user vtimestamp-read -- npx vtimestamp-mcp@latest

Claude Desktop

Add to your claude_desktop_config.json:

"mcpServers": { "vtimestamp": { "command": "npx", "args": ["-y", "vtimestamp-mcp@latest"] } } }

Using yarn:

"mcpServers": { "vtimestamp": { "command": "yarn", "args": ["dlx", "vtimestamp-mcp"] } } }

Using pnpm:

"mcpServers": { "vtimestamp": { "command": "pnpm", "args": ["dlx", "vtimestamp-mcp"] } } }

VS Code

Add to your VS Code MCP settings:

"mcp": { "servers": { "vtimestamp": { "command": "npx", "args": ["-y", "vtimestamp-mcp@latest"] } } } }

Tools

`vtimestamp_verify`

Verify whether a file or text has been timestamped on a VerusID. Provide either a file path or text — the server computes the SHA-256 hash and checks it against the on-chain record.

Parameter	Type	Required	Description
`identity`	string	Yes	VerusID name (e.g., `alice@`)
`file_path`	string	One of	Path to a file to verify
`text`	string	One of	Text string to verify

Either file_path or text must be provided (mutually exclusive).

Example prompts:

"Check if the file at /path/to/report.pdf has been timestamped on alice@"
"Verify this text was timestamped on bob@: I attest that invoice #4521 was approved"

`vtimestamp_list`

List all timestamps recorded on a VerusID.

Parameter	Type	Required	Description
`identity`	string	Yes	VerusID name (e.g., `alice@`)

Example: "What documents has alice@ timestamped?"

`vtimestamp_info`

Get information about the vtimestamp service.

No parameters.

Example: "What is vtimestamp?"

How It Works

By default, the server queries a public Verus mainnet RPC endpoint. No wallet, no API keys, no authentication required.

AI Agent (Claude Desktop, VS Code, etc.)

│ stdio (JSON-RPC) ▼ vtimestamp-mcp (local) │ HTTPS (JSON-RPC 1.0) ▼ Public Verus Mainnet RPC (rpc.vrsc.syncproof.net, fallback api.verus.services)

You can also point this server at your own daemon — useful for testnet (where no public RPC supports decryption), high-volume agents, custom chains, or anyone who'd rather not have their inspections hit a public RPC. See Configuration below.

On-chain storage shape

vtimestamps are stored under a VerusID's contentmultimap and read via getidentityhistory (one history entry per updateidentity). This server handles two on-chain shapes transparently:

Public-encrypted (`flags: 13`, written by `vtimestamp-mcp-write@1.2.0+`) — the daemon's {data:{}} envelope produces a single ciphertext DataDescriptor with epk and ivk published on-chain. Reading these requires decryptdata + the originating txid + retrieve: true. Because the IVK is on-chain (public-encrypted mode), anyone can decrypt — no key sharing.
Legacy plaintext (`flags: 0`, written by `vtimestamp-mcp-write@1.1.x` and earlier) — per-field DataDescriptors (sha256, title, description, filename, filesize) under labeled keys. Read directly without decryptdata.

The reader branches on each entry's flags. Mixed identities (legacy entries from older writes alongside new encrypted entries) are handled correctly — both surface in vtimestamp_list output.

For background, see How to Publish Encrypted Data on an Identity.

Public RPC requirement

decryptdata is a daemon RPC method that public Verus RPCs do not all whitelist. As of writing:

Endpoint	Chain	`decryptdata`	Notes
`https://rpc.vrsc.syncproof.net`	VRSC mainnet	✅ enabled	This server's primary endpoint.
`https://api.verus.services`	VRSC mainnet	❌ disabled	Fallback only. Encrypted entries fail to decrypt here, but legacy plaintext reads still work.
`https://api.verustest.net`	VRSCTEST	❌ disabled	No public testnet RPC supports `decryptdata`. Testnet encrypted reads require a local daemon.

If syncproof is unreachable and the call falls back to api.verus.services, encrypted entries will gracefully surface as un-decryptable rather than crashing.

Configuration

For default public-RPC use, no configuration is needed. To point the server at your own daemon (required for testnet, recommended for high-volume use), set environment variables.

Environment Variables

All optional. Setting any of these switches the server from public-RPC mode to local-daemon mode.

Variable	Description
`VERUS_RPC_URL`	Daemon RPC URL (e.g., `http://127.0.0.1:27486` for mainnet, `http://127.0.0.1:18843` for testnet)
`VERUS_CONF_PATH`	Path to a `VRSC.conf` / `vrsctest.conf` file. Auto-derives URL (`http://127.0.0.1:` ) and credentials.
`VERUS_RPC_USER`	Override: RPC username
`VERUS_RPC_PASSWORD`	Override: RPC password

Behavior:

*(no env vars)* → public RPC pair (rpc.vrsc.syncproof.net primary, api.verus.services fallback). Mainnet only.
VERUS_RPC_URL set → single local endpoint at that URL. Auth from VERUS_RPC_USER + VERUS_RPC_PASSWORD, or auto-derived from VERUS_CONF_PATH if those are missing.
VERUS_CONF_PATH set (without VERUS_RPC_URL) → URL = http://127.0.0.1: from the conf, with credentials from the conf.

Local daemon example (testnet)

"mcpServers": { "vtimestamp": { "command": "npx", "args": ["-y", "vtimestamp-mcp@latest"], "env": { "VERUS_CONF_PATH": "/Users/you/Library/Application Support/Komodo/vrsctest/vrsctest.conf" } } } }

Or pin everything explicitly:

"mcpServers": { "vtimestamp": { "command": "npx", "args": ["-y", "vtimestamp-mcp@latest"], "env": { "VERUS_RPC_URL": "http://127.0.0.1:18843", "VERUS_RPC_USER": "rpc-user-from-conf", "VERUS_RPC_PASSWORD": "rpc-password-from-conf" } } } }

Requirements

Node.js 18+
For default operation: nothing else — uses public mainnet RPC.
For testnet or local-daemon mode: a running verusd (or verusd -chain=vrsctest) on the host you point at.

License

MIT

Vtimestamp

Overview

PopNx MCP’s three pillars

What you can do with it

Install

Before you install

What it can do

Basic checksi

Maker matches the repo

Still maintained

Has a licence

Endpoint responds

Sign-in with OAuth

No hidden instructions in tool descriptions

Compared with others in Otheri

Common questions

Alternatives

Spec Driven Development

Remote Desktop Commander

오늘냥이 (Oneul Nyangi)

README from the maker

vtimestamp-mcp

Installation

Claude Code

Claude Desktop

VS Code

Tools

vtimestamp_verify

vtimestamp_list

vtimestamp_info

How It Works

On-chain storage shape

Public RPC requirement

Configuration

Environment Variables

Local daemon example (testnet)

Requirements

License

`vtimestamp_verify`

`vtimestamp_list`

`vtimestamp_info`