MCP Tools Directory
← Browse integrations

Developer tools

io.github.vdappdev2/vtimestamp-write

Free account · sign-in required

Contact io.github.vdappdev2/vtimestamp-write

Loading secure sign-in…

Tools for autonomous AI agents

Official website ↗

About this integration

MCP server for creating vtimestamp proofs on the Verus blockchain via a local or remote daemon

Transport
stdio
Authentication
client-credentials
Initial setup
credentials
Runtime
unattended
Evidence
documented
Version
1.0.0
Package
vtimestamp-mcp-write
Last compatibility test
Not independently tested

Connect your agent

vtimestamp-mcp-write

Publisher README and npm manifest reviewed offline. The package, daemon, wallet, and blockchain were not accessed or executed. This integration performs external on-chain writes that incur fees and requires an identity private key in the daemon wallet; credentials and private keys must remain outside prompts and publication artifacts.

Repository ↗Authentication & capability evidence ↗

Capabilities: Create a Verus blockchain timestamp for supplied text or a local file, Write timestamp metadata through a configured local or remote Verus daemon

Connected profiles

Developer toolsindustries

Additional details

Registry identifier

io.github.vdappdev2/vtimestamp-write

Source ↗ · Checked 2026-09-17
Published version

1.0.0

Source ↗ · Checked 2026-09-17
Metadata license

CC0-1.0; package licenses are separate

Source ↗ · Checked 2026-09-17
Package ecosystem

npm

Source ↗ · Checked 2026-09-17
Required configuration names

VERUS_RPC_URL

Source ↗ · Checked 2026-09-17
Source artifact

vtimestamp-mcp-write

Source ↗ · Checked 2026-09-20
Source manifest version

1.2.0

Source ↗ · Checked 2026-09-20
Unattended configuration

The publisher documents a Node.js 18+ stdio server launched by npx from MCP client configuration. Once its separately running Verus daemon and wallet prerequisites are configured, the server can be client-managed without an interactive launch step; this was not runtime-tested.

Source ↗ · Checked 2026-09-20
Authentication and prerequisites

The server uses Verus daemon RPC credentials auto-detected from VRSC.conf or supplied through documented overrides, and the daemon wallet must contain the identity private key. This is classified as client credentials with credential setup; no credentials were read or tested.

Source ↗ · Checked 2026-09-20
Connection configuration

The MCP connection is local stdio. The server then connects to a user-configured local or remote Verus daemon over authenticated HTTP JSON-RPC; there is no fixed MCP endpoint to publish.

Source ↗ · Checked 2026-09-20
Review scope

Publisher documentation reviewed; package and integration endpoint not executed or independently security-audited.

Source ↗ · Checked 2026-09-20