Config is the same across clients — only the file and path differ.
{
"mcpServers": {
"vtimestamp": {
"args": [
"-y",
"vtimestamp-mcp@latest"
],
"command": "npx"
}
}
}Are you the author?
Add this badge to your README to show your security score and help users find safe servers.
MCP server for verifying and querying vtimestamp proofs on the Verus blockchain.
Run this in your terminal to verify the server starts. Then let us know if it worked — your result helps other developers.
npx -y 'vtimestamp-mcp' 2>&1 | head -1 && echo "✓ Server started successfully"
After testing, let us know if it worked:
Five weighted categories — click any category to see the underlying evidence.
No known CVEs.
Checked vtimestamp-mcp against OSV.dev.
Click any tool to inspect its schema.
Be the first to review
Have you used this server?
Share your experience — it helps other developers decide.
Sign in to write a review.
Others in finance / security
Real-time financial market data: stocks, forex, crypto, commodities, and economic indicators
An evil MCP server used for redteam testing
A Model Context Protocol server for building an investor agent
AI-powered reverse engineering assistant that bridges IDA Pro with language models through MCP.
MCP Security Weekly
Get CVE alerts and security updates for io.github.vdappdev2/vtimestamp and similar servers.
Start a conversation
Ask a question, share a tip, or report an issue.
Sign in to join the discussion.
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.
claude mcp add --transport stdio --scope user vtimestamp-read -- npx vtimestamp-mcp@latest
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"]
}
}
}
Add to your VS Code MCP settings:
{
"mcp": {
"servers": {
"vtimestamp": {
"command": "npx",
"args": ["-y", "vtimestamp-mcp@latest"]
}
}
}
}
vtimestamp_verifyVerify 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:
vtimestamp_listList 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_infoGet information about the vtimestamp service.
No parameters.
Example: "What is vtimestamp?"
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.
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:
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.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 b