mcpField
R
Rel-Time Protocol (Bitcoin & VDF Provenance)

Rel-Time Protocol (Bitcoin & VDF Provenance)

Local
rel-time.comSecurity0Updated 6d ago

About Rel-Time Protocol (Bitcoin & VDF Provenance)

Rel-Time’s MCP server lets agents anchor file hashes to Bitcoin and a VDF, then verify provenance and integrity. It supports local hashing, Passkey signing, visual stamps, and audit reports.

Key features

  1. 01Hash files locally
  2. 02Anchor hashes to Bitcoin and VDF
  3. 03Sign anchors with Passkeys
  4. 04Add Sun-Stamps to files
  5. 05Verify proofs and audit folders

Use cases

  1. 01Timestamping a document or image
  2. 02Batch anchoring a local folder
  3. 03Checking Bitcoin settlement proofs
  4. 04Generating an integrity audit report

MCP support

Exposes tools for local file and folder hashing, anchoring, Passkey linking, stamping, proof checks, account status, and audit reports to MCP clients.

Configuration

Local server config is the same for every client. Copy it into your client’s MCP config file.

mcp.json · Universal config
{
"mcpServers": {
"relsun369-dev-rel-time": {
"command": "npx",
"args": [
"-y",
"@rel-time/mcp-server"
]
}
}
}
Run commandnpx -y @rel-time/mcp-server

Local servers need a runtime on your machine (e.g. Node.js 18+). Config file locations differ by client; see your client’s docs.

Packages
npm@rel-time/mcp-server1.2.14

Tools

10

Saved tool list · updated 6d ago

ParameterTypeRequiredDescription
api_keystringNoOptional override for RELTIME_API_KEY (Autonomous Agent, Universal Anchor, or Enterprise Superhighway key).
biometricbooleanNoIf true, performs a Biometric Anchor using your linked hardware Passkey (TouchID / FaceID / YubiKey) so the anchored hash (`SHA256(File_Hash + Passkey_PubKey)`) and Sun-Stamp mathematically prove your personal authorship. If no Passkey is linked yet, automatically opens the browser TouchID/FaceID prompt.
file_pathstringYesAbsolute path to the local file to hash and anchor.
anchor_modeenumNoUse 'standard' (default) to anchor the file/biometric SHA-256 hash into the Bitcoin Merkle tree for standalone file verification, or 'temporal' to anchor the VDF Thermodynamic Proof (T_index) for sub-second sequential ordering.standard | temporal
save_stamped_copybooleanNoIf true (default), automatically generates `reltime-stamped-<name>.pdf` or `.png` with the crisp 64-ray Sun-Stamp in the bottom-right corner when the file is a PDF or Image.
save_sun_stamp_svgbooleanNoIf true (default), saves `reltime-stamp-<filename>.svg` in the same folder as the file.
save_certificate_htmlbooleanNoIf true (default), saves the 4-Plate Sovereign Cryptographic Provenance Certificate (`reltime-certificate-<filename>.html`) in the same folder as the file.
open_certificate_in_browserbooleanNoIf true, opens the generated 4-Plate Sovereign Cryptographic Provenance Certificate HTML in the system browser.

Details

From the project README

@rel-time/mcp-server — Official Rel-Time MCP Server

Official Model Context Protocol (MCP) server for Rel-Time — enabling Claude Desktop, Cursor, Windsurf, and Google Antigravity agents to:

  1. Hash local files with 100% Zero-Knowledge (your file bytes never leave your computer).
  2. Execute both Anonymous & Biometric (Passkey) Anchors (SHA256(File_Hash + Passkey_PubKey)) using TouchID, FaceID, or YubiKey via https://rel-time.com/mcp-passkey.
  3. Anchor SHA-256 hashes to the Bitcoin Timechain & Rel-Time VDF (POST /v1/anchor).
  4. Generate & overlay 64-ray Sun-Stamps onto PDFs and Images (reltime-stamped-<name>.pdf / .png).
  5. Verify Bitcoin block settlement & Merkle proofs (GET /v1/proof/{hash}).
  6. Self-provision or Reload all 4 Rel-Time Tiers via Bitcoin Lightning or Stripe Card (Universal Anchor $3, Agent Launch Pack $5 / 25, Autonomous Agents $50 / 500, and Rel-Time Superhighway $399 / 5,000).
  7. Run a Superhighway Cryptographic Audit Trail & Local Folder Integrity Check (reltime_audit_trail), generating an interactive HTML Audit Dashboard with Corporate Hardware Passkey (signer_public_key) attribution and Bitcoin block verification.

Quick Setup (Claude Desktop / Claude Code / Cursor / Windsurf / Antigravity)

Add the following to your .mcp.json, claude_desktop_config.json, or .cursor/mcp.json (no API key or .zshrc environment variables needed to start!):

{
  "mcpServers": {
    "rel-time": {
      "command": "npx",
      "args": ["-y", "@rel-time/mcp-server@latest"]
    }
  }
}

When you start a fresh chat and ask to anchor a file or provision a key, @rel-time/mcp-server automatically prompts your agent to ask which tier and payment method (Bitcoin Lightning or Stripe Card) you want first:

  1. Universal Anchor (pack: "universal", $3 / anchor): Priority 10-Minute Bitcoin Queue · Standard Mode (Data Integrity + Biometric or Anonymous).
  2. Agent Launch Pack (pack: "launch", $5 / 25 Hashes, max 3 per key): Priority 10-Minute Bitcoin Queue · Standard Mode · Includes 64-Ray Sun-Stamp, 1-Click Stamped Copy (.PDF/.PNG), 4-Plate Certificate, and .JSON Doomsday Proof.
  3. Autonomous Agents (pack: "standard", $50 / 500 Hashes): Dynamic 6-Hour Batch Queue · Supports both Temporal Mode (T_index sub-second VDF sequencing) and Standard Mode · Reloadable anytime (+500 credits / $50).
  4. Rel-Time Superhighway (pack: "enterprise", $399 / 5,000 Hashes): Priority 10-Minute Bitcoin Queue · Temporal Mode (T_index) + Standard Mode + Data Integrity Audit & Instant Tamper Detection.

Once paid via Lightning or Stripe (or if you pass an existing rel_key_... key), the MCP server automatically saves your API key to ~/.reltime/api_key.json (0600 permissions) — no app restart or .zshrc edits required.


Available MCP Tools

Tool NameRequires Key?What It Does
reltime_anchor_fileYesComputes the SHA-256 hash of a local file on your machine (0 bytes uploaded), supports biometric: true for Biometric Anchors (TouchID/FaceID/YubiKey), anchors via POST /v1/anchor, saves reltime-stamp-<filename>.svg, reltime-certificate-<filename>.html, and reltime-doomsday-proof-<filename>.json, and automatically outputs a clickable Stamped Copy (reltime-stamped-<name>.pdf or .png).
reltime_anchor_folderYesBulk folder anchoring (10 to 5,000+ files in one call): Hashes all files in a local folder 100% locally, supports biometric: true (Passkey) or Anonymous mode, automatically skips already-anchored files (safe to resume), and keeps your directory clean by storing per-file Doomsday Proofs inside <folder>/_reltime_proofs/ plus a master reltime-batch-manifest.json.
reltime_audit_trailYesFetches the account's chronological anchor ledger (GET /v1/account/history), aggregates Bitcoin block settlements, VDF T_index ticks, and Corporate Hardware Passkey (signer_public_key) signatures, optionally verifies a local file or entire folder bit-for-bit (verify_local_path), and spins up a self-contained interactive HTML Audit Report (reltime-audit-report-*.html) in your browser.
reltime_link_passkeyNoOpens https://rel-time.com/mcp-passkey in the system browser so the user can touch TouchID / FaceID / YubiKey once, saving { public_key_hex, passkey_signature } to ~/.reltime/passkey.json for seamless Biometric Anchors.
reltime_stamp_fileNoOverlays the authentic 64-ray Sun-Stamp onto the bottom-right corner of any local PDF or Image (.png, .jpg, .jpeg, .webp, .gif) 100% locally.
reltime_anchor_hashYesAnchors any 64-char hex SHA-256 hash in standard (10-min Express / Integrity) or temporal (VDF sequence ordering) mode.
reltime_get_sun_stampNoFetches the deterministic 64-ray SVG Sun-Stamp (GET /v1/stamp/{hash}) and returns ready-to-paste Markdown/HTML badge snippets.
reltime_check_proofNoQueries GET /v1/proof/{hash} for Bitcoin TXID, Block Height, UTC Timestamp, and Merkle inclusion path, and optionally saves/updates the .json Doomsday Proof receipt on disk.
reltime_account_statusYesChecks remaining Hash Credits and tier status (GET /v1/account).
reltime_provision_agent_keyNoProvisions or reloads any of the 4 Rel-Time Tiers (universal $3, launch $5/25, standard $50/500, enterprise $399/5,000) via Bitcoin Lightning or Stripe Card.

Comments

Markdown supported

New to MCP?

From what the protocol is to installing your first server, these answers cover most first questions.

An open protocol that defines how AI applications connect to external tools and data in a uniform way. Clients talk to the model; MCP servers provide tools, resources and prompt templates. They exchange standard messages, so one server can be reused by many clients.