Context7
Up-to-date docs for AI agents
作者提供的说明(英文原文)
Zero-knowledge Bitcoin Mainnet & VDF timestamping, Passkey signing, Sun-Stamps, and tamper audits.
这三项永远不会合并成一个分数:意见、测量和人气是不同的东西。
我们还没有为它写通俗的介绍。下面是我们从注册中心读取到的事实。
选择你使用的 AI 应用,然后复制设置。
你需要
你用的是哪个应用?
在上方选择你的应用。我们会记住它,下次按钮会显示“安装到 …”。
打开 Claude Desktop → Settings → Developer → Edit Config,把下面的内容粘贴到 claude_desktop_config.json
{
"mcpServers": {
"rel-time": {
"command": "npx",
"args": [
"-y",
"@rel-time/mcp-server"
]
}
}
}在终端中运行这条命令
claude mcp add rel-time -- npx -y @rel-time/mcp-server粘贴到项目中的 .cursor/mcp.json,或 ~/.cursor/mcp.json
{
"mcpServers": {
"rel-time": {
"command": "npx",
"args": [
"-y",
"@rel-time/mcp-server"
]
}
}
}浏览器会先询问是否打开应用,然后应用会显示设置并请你确认。密钥的值会留空,由你自己填写。
粘贴到项目中的 .vscode/mcp.json
{
"servers": {
"rel-time": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"@rel-time/mcp-server"
]
}
}
}浏览器会先询问是否打开应用,然后应用会显示设置并请你确认。密钥的值会留空,由你自己填写。
这个服务器在你的电脑上运行,而 ChatGPT 只能连接互联网上的服务器。请选择其他应用。
你的选择通过 Cookie 保存在这台设备上,无需账户。
这些设置是根据作者在注册中心的条目生成的。如果 README 的写法不同,请以 README 为准。
它在你的电脑上运行;安装后,工具列表会显示在你的 AI 应用中。
我们检查的是任何人都能看到的信息;我们没有阅读代码。不适用的检查项不计入总数。 · 检查于 2026年11月6日
注册名称已通过 GitHub 账户 relsun369-dev 验证,该账户拥有此仓库
我们还没有从 GitHub 读取这个仓库
我们还没有从 GitHub 读取这个仓库
它在你的电脑上运行,没有互联网端点
在你的电脑上运行,改用本地设置
它在你的电脑上运行;我们只能读取互联网端点的工具列表
与注册中心里这个分类中所有活跃的服务器比较。只有当发布者拥有该仓库时,星标数才计入。
它在 1 项适用的基础检查中通过了 1 项。我们没有阅读代码。在添加密钥或令牌之前,请先看看这个服务器要求哪些权限,并使用只具备所需权限的密钥。
注册中心没有列出必需的密钥,不过有些服务器会在首次使用时要求你登录。
它在你的电脑上运行。你的 AI 应用会在需要时启动它,数据不会经过作者的服务器(除非它自己调用在线服务)。
GitHub 仓库最后更新于–,最新版本(1.2.14)于3天前进入注册中心。
支持 MCP 的应用,例如 Claude Desktop、Claude Code、Cursor 和 VS Code。你的电脑上还需要有 Node.js。
同一分类中有:Context7, Codebase Memory, Exa
同一分类中其他作者的服务器,按星标数排序。
如何看卡片:★ GitHub 星标i三大支柱:评价 · 检查 · 使用情况i更新 = 最新版本发布到注册中心的时间i
Up-to-date docs for AI agents
Codebase knowledge graph for AI agents — 162 languages, sub-ms queries, 99% fewer tokens.
Connect AI agents to Exa for web search, content fetching, and multi-step research.
按原文从作者的仓库复制。PopNx MCP 没有审查或背书其内容。HTML、图片和脚本已被移除。链接会离开本站。
@rel-time/mcp-server — Official Rel-Time MCP ServerOfficial Model Context Protocol (MCP) server for [Rel-Time](https://rel-time.com) — enabling Claude Desktop, Cursor, Windsurf, and Google Antigravity agents to:
SHA256(File_Hash + Passkey_PubKey)) using TouchID, FaceID, or YubiKey via https://rel-time.com/mcp-passkey.POST /v1/anchor).reltime-stamped- .pdf / .png).GET /v1/proof/{hash}).Universal Anchor $3, Agent Launch Pack $5 / 25, Autonomous Agents $50 / 500, and Rel-Time Superhighway $399 / 5,000).reltime_audit_trail), generating an interactive HTML Audit Dashboard with Corporate Hardware Passkey (signer_public_key) attribution and Bitcoin block verification.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:
.PDF/.PNG), 4-Plate Certificate, and .JSON Doomsday Proof.T_index sub-second VDF sequencing) and Standard Mode · Reloadable anytime (+500 credits / $50).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.
| Tool Name | Requires Key? | What It Does |
|---|---|---|
reltime_anchor_file | Yes | Computes 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- .svg, reltime-certificate- .html, and reltime-doomsday-proof- .json, and automatically outputs a clickable Stamped Copy (reltime-stamped- .pdf or .png). |
reltime_anchor_folder | Yes | Bulk 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 /_reltime_proofs/ plus a master reltime-batch-manifest.json. |
reltime_audit_trail | Yes | Fetches 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_passkey | No | Opens 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_file | No | Overlays 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_hash | Yes | Anchors any 64-char hex SHA-256 hash in standard (10-min Express / Integrity) or temporal (VDF sequence ordering) mode. |
reltime_get_sun_stamp | No | Fetches the deterministic 64-ray SVG Sun-Stamp (GET /v1/stamp/{hash}) and returns ready-to-paste Markdown/HTML badge snippets. |
reltime_check_proof | No | Queries 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_status | Yes | Checks remaining Hash Credits and tier status (GET /v1/account). |
reltime_provision_agent_key | No | Provisions 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. |