AnchorRegistry vs Vtimestamp
A side-by-side look at the AnchorRegistry and Vtimestamp MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
Verdict: choose AnchorRegistry for cryptography work over a hosted endpoint; choose Vtimestamp for cryptography as a local process. You can also run both side by side in one mcpServers block.
Which MCP server should you choose?
Choose AnchorRegistry when
- You need dedicated capabilities in the Cryptography domain.
- You prefer a remote HTTP/SSE transport.
- You want tools like
ar_verify_arid, ar_verify_by_hash, ar_resolve_tree.
Choose Vtimestamp when
- You need dedicated capabilities in the Cryptography domain.
- You prefer a local stdio subprocess transport.
- You have the keys it needs:
VERUS_RPC_URL, VERUS_CONF_PATH, VERUS_RPC_USER, VERUS_RPC_PASSWORD.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | ||
|---|---|---|
| Category | Cryptography | Cryptography |
| Quality signal | 41/100 · Fair | 35/100 · Fair |
| Install command | Confirmed | Confirmed |
| Transport | Remote HTTP/SSE | Local subprocess (stdio) |
| Auth | Not declared | Not declared |
| Pricing | Not declared | Not declared |
| Required env vars | None listed | VERUS_RPC_URLVERUS_CONF_PATHVERUS_RPC_USERVERUS_RPC_PASSWORD |
| Verified owner | Community listing | Community listing |
| GitHub stars | 0 | 0 |
| Directory activity | 0 views 0 installs 0 upvotes | 0 views 0 installs 0 upvotes |
| Tools | 3 | Not listed |
| Full listing | View AnchorRegistry | View Vtimestamp |
Tools & capabilities
AnchorRegistry tools 3
ar_verify_aridResolves an AR-ID to its full provenance record.ar_verify_by_hashResolves an artifact by SHA-256 manifest hash.ar_resolve_treeReturns the full provenance tree for any AR-ID.
Vtimestamp tools
No tool names declared yet. Check the project README from the listing page.
Ready-to-paste client configs
Paste either block (or both) into your client config, e.g. claude_desktop_config.json or ~/.cursor/mcp.json. We only show a config when the install command is confirmed.
AnchorRegistry
{
"mcpServers": {
"anchorregistry": {
"url": "https://mcp.anchorregistry.ai/mcp"
}
}
}
Vtimestamp
{
"mcpServers": {
"vtimestamp": {
"command": "npx",
"args": [
"-y",
"vtimestamp-mcp@latest"
],
"env": {
"VERUS_RPC_URL": "YOUR_VERUS_RPC_URL_HERE",
"VERUS_CONF_PATH": "YOUR_VERUS_CONF_PATH_HERE",
"VERUS_RPC_USER": "YOUR_VERUS_RPC_USER_HERE",
"VERUS_RPC_PASSWORD": "YOUR_VERUS_RPC_PASSWORD_HERE"
}
}
}
}
Frequently asked questions
AnchorRegistry is categorized under Cryptography and uses a remote HTTP/SSE transport. Vtimestamp belongs to Cryptography and uses a local stdio subprocess. Pick AnchorRegistry for cryptography work and Vtimestamp for cryptography.
Copy the mcpServers block from the config section on this page into your client's config (for example claude_desktop_config.json or ~/.cursor/mcp.json), then fully restart the client.
AnchorRegistry has no declared pricing — check the project's own site. Vtimestamp has no declared pricing — check the project's own site. If a server needs environment variables such as API keys, define them under the env key in your client's MCP config.
Yes. MCP clients support multiple servers: add anchorregistry and vtimestamp as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, AnchorRegistry has a quality signal of 41/100 (Fair) with 0 views, 0 installs and 0 GitHub stars. Vtimestamp has 35/100 (Fair) with 0 views, 0 installs and 0 GitHub stars.