vtimestamp-mcp
Click on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@vtimestamp-mcp List all document timestamps for the VerusID alice@"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
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@latestClaude 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"]
}
}
}
}Related MCP server: vtimestamp-mcp-write
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 |
| string | Yes | VerusID name (e.g., |
| string | One of | Path to a file to verify |
| 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 |
| string | Yes | VerusID name (e.g., |
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 byvtimestamp-mcp-write@1.2.0+) — the daemon's{data:{}}envelope produces a single ciphertext DataDescriptor withepkandivkpublished on-chain. Reading these requiresdecryptdata+ 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 byvtimestamp-mcp-write@1.1.xand earlier) — per-field DataDescriptors (sha256, title, description, filename, filesize) under labeled keys. Read directly withoutdecryptdata.
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 |
| Notes |
| VRSC mainnet | ✅ enabled | This server's primary endpoint. |
| VRSC mainnet | ❌ disabled | Fallback only. Encrypted entries fail to decrypt here, but legacy plaintext reads still work. |
| VRSCTEST | ❌ disabled | No public testnet RPC supports |
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 |
| Daemon RPC URL (e.g., |
| Path to a |
| Override: RPC username |
| Override: RPC password |
Behavior:
(no env vars) → public RPC pair (
rpc.vrsc.syncproof.netprimary,api.verus.servicesfallback). Mainnet only.VERUS_RPC_URLset → single local endpoint at that URL. Auth fromVERUS_RPC_USER+VERUS_RPC_PASSWORD, or auto-derived fromVERUS_CONF_PATHif those are missing.VERUS_CONF_PATHset (withoutVERUS_RPC_URL) → URL =http://127.0.0.1:<rpcport>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(orverusd -chain=vrsctest) on the host you point at.
License
MIT
Available Tools
3 toolsvtimestamp_infoB
Get information about the vtimestamp service — what it is, how it works, and supported features.
Inputs: no named parameters.
vtimestamp_listC
List all timestamps recorded on a VerusID. Returns an array of timestamps with hash, title, metadata, and blockchain proof details.
Inputs: identity (required).
vtimestamp_verifyA
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. Returns blockchain proof details if found.
Inputs: identity (required), file_path, text.
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
TDQS
Scored across 3 tools
Each tool has a clearly distinct purpose: vtimestamp_info provides service information, vtimestamp_list retrieves recorded timestamps, and vtimestamp_verify checks for timestamp existence. There is no overlap in functionality, making tool selection straightforward for an agent.
All tool names follow a consistent verb_noun pattern with the prefix 'vtimestamp_' (e.g., vtimestamp_info, vtimestamp_list, vtimestamp_verify). This uniformity ensures predictable and readable naming across the toolset.
With 3 tools, the server is well-scoped for its purpose of timestamping and verification on VerusID. Each tool serves a distinct and essential function (info, list, verify), and there are no extraneous or missing tools for this focused domain.
The toolset covers core operations: getting service info, listing timestamps, and verifying timestamps. A minor gap exists in the lack of a tool to create or record new timestamps, but agents can still perform key workflows with the provided tools.
Maintenance
Related MCP Connectors
Verify VerixID proof-of-existence records and optionally prove ownership.
Tamper-evident proof creation and verification for AI agents via MCP, A2A, and REST.
Keyless, read-only checks of Intentrax AI-agent execution proofs. Never executes, signs, or writes.
Notary for AI agents: seal fingerprints, verify proofs, check mandates. Anchored in Bitcoin.
Related MCP Servers
- AlicenseAqualityBmaintenanceStamp, upgrade, and verify Bitcoin timestamps via AI agents using the OpenTimestamps protocol. No API keys required.9140 npm3MIT
- AlicenseNot gradedqualityDmaintenanceEnables AI agents to create document timestamps on a VerusID, writing directly to the Verus blockchain via a local or remote daemon.53 npmMIT

corpus.333.ecoofficial
FlicenseNot gradedqualityBmaintenanceEnables agents to search, retrieve, and list open-licensed documents with verifiable provenance, attaching sha256, DOI, and OpenTimestamps proof to every response.1,531 npm-- AlicenseBqualityBmaintenanceProof of control for AI agents, through the proof.holdings API: verify domains, phone numbers and messenger accounts, ask a human to approve an action, and issue and verify Proofs of Delegation.2201,781 npmMIT