vtimestamp-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| 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. |
| vtimestamp_listC | List all timestamps recorded on a VerusID. Returns an array of timestamps with hash, title, metadata, and blockchain proof details. |
| vtimestamp_infoB | Get information about the vtimestamp service — what it is, how it works, and supported features. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
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.