Spec Driven Development
MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.
作者提供的说明(英文原文)
Bitcoin-anchored, tamper-evident audit log for AI agents — record, disclose and verify actions.
这三项永远不会合并成一个分数:意见、测量和人气是不同的东西。
我们还没有为它写通俗的介绍。下面是我们从注册中心读取到的事实。
选择你使用的 AI 应用,然后复制设置。
TOUCHSTONE_RECORDER, TOUCHSTONE_SUBJECT, TOUCHSTONE_API_KEY, TOUCHSTONE_SIGNING_KEY, TOUCHSTONE_KEY_FILE, TOUCHSTONE_BASE_URL, Authorization标为机密的值是你账户的钥匙。千万不要分享给别人,也不要粘贴到聊天里。
你需要
你用的是哪个应用?
在上方选择你的应用。我们会记住它,下次按钮会显示“安装到 …”。
这个地址需要在请求的 header 中放入密钥,而添加连接器的菜单无法设置。请改用 Claude Code、Cursor 或 VS Code。
打开 Claude Desktop → Settings → Developer → Edit Config,把下面的内容粘贴到 claude_desktop_config.json
{
"mcpServers": {
"touchstone": {
"command": "npx",
"args": [
"-y",
"@touchstone-cv/mcp"
],
"env": {
"TOUCHSTONE_RECORDER": "your-value",
"TOUCHSTONE_SUBJECT": "your-value",
"TOUCHSTONE_API_KEY": "your-value",
"TOUCHSTONE_SIGNING_KEY": "your-value",
"TOUCHSTONE_KEY_FILE": "your-value",
"TOUCHSTONE_BASE_URL": "your-value"
}
}
}
}在终端中运行这条命令
claude mcp add --transport http touchstone https://touchstone.cv/mcp --header 'Authorization: your-value'claude mcp add touchstone --env TOUCHSTONE_RECORDER=your-value --env TOUCHSTONE_SUBJECT=your-value --env TOUCHSTONE_API_KEY=your-value --env TOUCHSTONE_SIGNING_KEY=your-value --env TOUCHSTONE_KEY_FILE=your-value --env TOUCHSTONE_BASE_URL=your-value -- npx -y @touchstone-cv/mcp运行前请先填写空着的值。
粘贴到项目中的 .cursor/mcp.json,或 ~/.cursor/mcp.json
{
"mcpServers": {
"touchstone": {
"url": "https://touchstone.cv/mcp",
"headers": {
"Authorization": "your-value"
}
}
}
}粘贴到项目中的 .cursor/mcp.json,或 ~/.cursor/mcp.json
{
"mcpServers": {
"touchstone": {
"command": "npx",
"args": [
"-y",
"@touchstone-cv/mcp"
],
"env": {
"TOUCHSTONE_RECORDER": "your-value",
"TOUCHSTONE_SUBJECT": "your-value",
"TOUCHSTONE_API_KEY": "your-value",
"TOUCHSTONE_SIGNING_KEY": "your-value",
"TOUCHSTONE_KEY_FILE": "your-value",
"TOUCHSTONE_BASE_URL": "your-value"
}
}
}
}浏览器会先询问是否打开应用,然后应用会显示设置并请你确认。密钥的值会留空,由你自己填写。
粘贴到项目中的 .vscode/mcp.json
{
"servers": {
"touchstone": {
"type": "http",
"url": "https://touchstone.cv/mcp",
"headers": {
"Authorization": "your-value"
}
}
}
}粘贴到项目中的 .vscode/mcp.json
{
"servers": {
"touchstone": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"@touchstone-cv/mcp"
],
"env": {
"TOUCHSTONE_RECORDER": "your-value",
"TOUCHSTONE_SUBJECT": "your-value",
"TOUCHSTONE_API_KEY": "your-value",
"TOUCHSTONE_SIGNING_KEY": "your-value",
"TOUCHSTONE_KEY_FILE": "your-value",
"TOUCHSTONE_BASE_URL": "your-value"
}
}
}
}浏览器会先询问是否打开应用,然后应用会显示设置并请你确认。密钥的值会留空,由你自己填写。
这个地址需要在请求的 header 中放入密钥,而添加连接器的菜单无法设置。请改用 Claude Code、Cursor 或 VS Code。
你的选择通过 Cookie 保存在这台设备上,无需账户。
TOUCHSTONE_KEY_FILE envTOUCHSTONE_BASE_URL envAuthorization 机密 必填 HTTP header这些设置是根据作者在注册中心的条目生成的。如果 README 的写法不同,请以 README 为准。
我们还没有读取这个服务器的工具列表;我们会轮流检查各个端点。
我们检查的是任何人都能看到的信息;我们没有阅读代码。不适用的检查项不计入总数。 · 检查于 2026年11月6日
注册名称已通过域名 touchstone.cv 验证(注册中心会核实域名所有权)
我们还没有从 GitHub 读取这个仓库
我们还没有从 GitHub 读取这个仓库
尚未检查;我们会轮流检查各个端点
尚未检查;我们会轮流检查各个端点
尚未检查;我们会在检查端点时读取工具列表
与注册中心里这个分类中所有活跃的服务器比较。只有当发布者拥有该仓库时,星标数才计入。
它在 1 项适用的基础检查中通过了 1 项。我们没有阅读代码。在添加密钥或令牌之前,请先看看这个服务器要求哪些权限,并使用只具备所需权限的密钥。
你需要填写:TOUCHSTONE_RECORDER, TOUCHSTONE_SUBJECT, TOUCHSTONE_API_KEY, TOUCHSTONE_SIGNING_KEY, Authorization
两种方式都可以:安装在你的电脑上,或者连接云端版本。
GitHub 仓库最后更新于–,最新版本(1.1.0)于4个月前进入注册中心。
支持 MCP 的应用,例如 Claude Desktop、Claude Code、Cursor 和 VS Code。它通过 URL 连接,所以接受远程 MCP 服务器的应用也可以使用,例如开启开发者模式的 ChatGPT。
同一分类中有:Spec Driven Development, Remote Desktop Commander, Whisper
同一分类中其他作者的服务器,按星标数排序。
如何看卡片:★ GitHub 星标i三大支柱:评价 · 检查 · 使用情况i更新 = 最新版本发布到注册中心的时间i
MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.
Remote Desktop Commander: use files, terminal and processes on your own computers from any AI app.
One routable IPv6 per AI agent, verifiable from the DNS root. Keyless tools need no signup.
按原文从作者的仓库复制。PopNx MCP 没有审查或背书其内容。HTML、图片和脚本已被移除。链接会离开本站。
Local MCP server for [Touchstone](https://touchstone.cv) — record what your agent did into a tamper-evident, externally-anchored log.
This server runs on your machine and holds your Ed25519 signing key. It signs each event locally and appends it to your recorder, so an agent only has to call touchstone_record({ event_type, payload }). The key never leaves this process. Canonicalization (JCS / RFC 8785) is done locally too, so a malicious or compromised server can't trick you into signing a different commitment than you intended.
Zero dependencies — Node 18+ built-ins only. It's a single file: read it before you trust it.
The remote MCP at
https://touchstone.cv/mcpcan't sign for you (Touchstone never holds your
key), so its
touchstone_recordexpects a signature you computed yourself. Run this server
when you want frictionless local signing.
# one-off, no install:
npx -y @touchstone-cv/mcp
curl -O https://touchstone.cv/touchstone-mcp.mjs
git clone https://github.com/Touchstone-CV/touchstone-mcp && cd touchstone-mcp
Point your MCP client at it over stdio:
{
"mcpServers": { "touchstone": { "command": "npx", "args": ["-y", "@touchstone-cv/mcp"], "env": { "TOUCHSTONE_RECORDER": "rec_...", "TOUCHSTONE_SUBJECT": " ", "TOUCHSTONE_API_KEY": "tsk_...", "TOUCHSTONE_SIGNING_KEY": " " } } } }
| Env var | Required | Meaning |
|---|---|---|
TOUCHSTONE_RECORDER | yes | Your recorder public id (rec_…) |
TOUCHSTONE_SUBJECT | to record | Your Colony sub — the recorder's subject |
TOUCHSTONE_API_KEY | yes | API key minted on the recorder (tsk_…) |
TOUCHSTONE_SIGNING_KEY | to record | base64 Ed25519 32-byte seed — kept by you, never sent |
TOUCHSTONE_KEY_FILE | alt | Path to JSON {"seed_b64":"…"} instead of the inline seed |
TOUCHSTONE_BASE_URL | no | Defaults to https://touchstone.cv |
To get a recorder + key, see [touchstone.cv/developers](https://touchstone.cv/developers) — agents can self-provision one with their own Colony token (OAuth Token Exchange, RFC 8693), no browser required.
| Tool | What it does |
|---|---|
touchstone_record | JCS-canonicalizes payload, signs the commitment locally, appends the entry |
touchstone_disclose | Create a shareable /d/ disclosure link (proxies to the service) |
touchstone_verify | Verify a disclosure bundle (proxies to the service) |
touchstone_recorder_info | Fetch your recorder's public info / checkpoint state |
Only touchstone_record uses your signing key; the rest proxy to the remote service over your API key.
Call touchstone_record({ event_type, payload, selective_disclosure: true }) to commit each payload field separately — the client computes a salted-field Merkle root locally and signs *that* as payload_hash, storing the per-field salts. Later you can reveal only a subset:
touchstone_disclose({ seqs: [n], reveal: { n: ["field_a", "field_b"] } })
Revealed fields ship with Merkle proofs against payload_hash (which your signature already covers); withheld fields are salt-bound and their values never appear in the disclosure. The root computation matches the server and the verifiers byte-for-byte.
A disclosure can be checked by anyone, with no trust in Touchstone — in the browser verifier, the standalone verify.php, or the gossip_check.py split-view checker. Those tools are served from the site (and are each a single auditable file); this repo is just the recording client.
Apache-2.0.