Server data from the Official MCP Registry
MCP server for creating vtimestamp proofs on the Verus blockchain via a local or remote daemon
MCP server for creating vtimestamp proofs on the Verus blockchain via a local or remote daemon
Valid MCP server (3 strong, 4 medium validity signals). No known CVEs in dependencies. Package registry verified. Imported from the Official MCP Registry.
7 files analyzed · 1 issue found
Security scores are indicators to help you make informed decisions, not guarantees. Always review permissions before connecting any MCP server.
This plugin requests these system permissions. Most are normal for its category.
Set these up before or after installing:
Environment variable: VERUS_RPC_URL
Environment variable: VERUS_RPC_USER
Environment variable: VERUS_RPC_PASSWORD
Environment variable: VERUS_NETWORK
Add this to your MCP configuration file:
{
"mcpServers": {
"io-github-vdappdev2-vtimestamp-write": {
"env": {
"VERUS_NETWORK": "your-verus-network-here",
"VERUS_RPC_URL": "your-verus-rpc-url-here",
"VERUS_RPC_USER": "your-verus-rpc-user-here",
"VERUS_RPC_PASSWORD": "your-verus-rpc-password-here"
},
"args": [
"-y",
"vtimestamp-mcp-write"
],
"command": "npx"
}
}
}From the project's GitHub README.
MCP server for creating vtimestamp proofs on the Verus blockchain.
Enables AI agents (Claude Desktop, VS Code, etc.) to create document timestamps on a VerusID — writing directly to the Verus blockchain via a local or remote daemon.
Looking for the read-only server? See vtimestamp-mcp — no daemon or wallet required.
verusd) running with:
claude mcp add --transport stdio --scope user vtimestamp-write -- npx vtimestamp-mcp-write@latest
Add to your claude_desktop_config.json:
{
"mcpServers": {
"vtimestamp-write": {
"command": "npx",
"args": ["-y", "vtimestamp-mcp-write@latest"]
}
}
}
That's it — the server auto-detects your RPC credentials from VRSC.conf (see Configuration below).
Add to your VS Code MCP settings:
{
"mcp": {
"servers": {
"vtimestamp-write": {
"command": "npx",
"args": ["-y", "vtimestamp-mcp-write@latest"]
}
}
}
}
The server automatically reads RPC credentials from your local VRSC.conf file. No manual configuration is needed for most users.
Auto-detected VRSC.conf paths:
~/Library/Application Support/Komodo/VRSC/VRSC.conf~/.komodo/VRSC/VRSC.conf%AppData%\Roaming\Komodo\VRSC\VRSC.confAll optional — only needed for non-standard setups or remote daemons.
| Variable | Description |
|---|---|
VERUS_CONF_PATH | Custom path to VRSC.conf |
VERUS_RPC_URL | Override: daemon RPC URL (for remote daemons) |
VERUS_RPC_USER | Override: RPC username (for remote daemons) |
VERUS_RPC_PASSWORD | Override: RPC password (for remote daemons) |
vtimestamp_createCreate a new timestamp on a VerusID. Provide either a file path or text — the server computes the SHA-256 hash automatically.
| Parameter | Type | Required | Description |
|---|---|---|---|
identity | string | Yes | VerusID name (e.g., alice@) |
file_path | string | One of | Path to a file to hash and timestamp |
text | string | One of | Text to hash and timestamp (e.g., an attestation or report) |
title | string | Yes | Title for the timestamp |
description | string | No | Description of the content |
filename | string | No | Original filename (auto-detected when using file_path) |
filesize | number | No | File size in bytes (auto-detected when using file_path) |
sourceoffunds | string | No | Funding address (R-address, z-address, or ID@) |
feeoffer | number | No | Fee offer in VRSC (default: 0.0001) |
Either file_path or text must be provided (mutually exclusive).
Example prompts:
Success response:
{
"success": true,
"identity": "alice@",
"hash": "a7f3b2c1...",
"title": "Q4 Report",
"transaction_id": "abc123...",
"message": "Timestamp created successfully"
}
Error cases:
InvalidParams errorThe server connects to your Verus daemon (local or remote) to create on-chain timestamps. The daemon must have the identity's private key in its wallet to sign the updateidentity transaction.
AI Agent (Claude Desktop, VS Code, etc.)
│ stdio (JSON-RPC)
▼
vtimestamp-mcp-write (local)
│ HTTP (JSON-RPC 1.0, with auth)
▼
Your Verus Daemon (verusd)
├── Has identity's private key in wallet
├── Signs and broadcasts updateidentity tx
└── Local (127.0.0.1) or remote (VPS)
The simplest setup — verusd runs on the same machine as the MCP server. No configuration needed — credentials are auto-detected from VRSC.conf.
You can point the MCP server at a verusd instance running on another machine (e.g., a VPS). The daemon needs two config changes in its VRSC.conf:
rpcallowip=<your-ip> (the daemon only accepts localhost by default)Then set the env var overrides (VERUS_RPC_URL, VERUS_RPC_USER, VERUS_RPC_PASSWORD) in your MCP config.
Important: RPC credentials are sent over plain HTTP. If connecting over the open internet (not a local network), use an SSH tunnel to secure the connection:
ssh -L 27486:127.0.0.1:27486 user@your-vps
Then use VERUS_RPC_URL=http://127.0.0.1:27486 as if it were local — the tunnel handles the rest.
VRSC.conf to auto-detect RPC credentials — no secrets are copied or stored elsewheresourceoffunds parameter can be used to control which address pays feesMIT
Be the first to review this server!
by Modelcontextprotocol · Developer Tools
Web content fetching and conversion for efficient LLM usage
by Modelcontextprotocol · Developer Tools
Read, search, and manipulate Git repositories programmatically
by Toleno · Developer Tools
Toleno Network MCP Server — Manage your Toleno mining account with Claude AI using natural language.
by mcp-marketplace · Developer Tools
Create, build, and publish Python MCP servers to PyPI — conversationally.