Spec Driven Development
MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.
作者提供的说明(英文原文)
Portable signed records for agent, API, MCP, and cross-runtime interactions.
这三项永远不会合并成一个分数:意见、测量和人气是不同的东西。
我们还没有为它写通俗的介绍。下面是我们从注册中心读取到的事实。
选择你使用的 AI 应用,然后复制设置。
你需要
你用的是哪个应用?
在上方选择你的应用。我们会记住它,下次按钮会显示“安装到 …”。
打开 Claude Desktop → Settings → Developer → Edit Config,把下面的内容粘贴到 claude_desktop_config.json
{
"mcpServers": {
"peac": {
"command": "npx",
"args": [
"-y",
"@peac/mcp-server"
]
}
}
}在终端中运行这条命令
claude mcp add peac -- npx -y @peac/mcp-server粘贴到项目中的 .cursor/mcp.json,或 ~/.cursor/mcp.json
{
"mcpServers": {
"peac": {
"command": "npx",
"args": [
"-y",
"@peac/mcp-server"
]
}
}
}浏览器会先询问是否打开应用,然后应用会显示设置并请你确认。密钥的值会留空,由你自己填写。
粘贴到项目中的 .vscode/mcp.json
{
"servers": {
"peac": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"@peac/mcp-server"
]
}
}
}浏览器会先询问是否打开应用,然后应用会显示设置并请你确认。密钥的值会留空,由你自己填写。
这个服务器在你的电脑上运行,而 ChatGPT 只能连接互联网上的服务器。请选择其他应用。
你的选择通过 Cookie 保存在这台设备上,无需账户。
这些设置是根据作者在注册中心的条目生成的。如果 README 的写法不同,请以 README 为准。
它在你的电脑上运行;安装后,工具列表会显示在你的 AI 应用中。
我们检查的是任何人都能看到的信息;我们没有阅读代码。不适用的检查项不计入总数。 · 检查于 2026年11月6日
注册名称已通过 GitHub 账户 peacprotocol 验证,该账户拥有此仓库
我们还没有从 GitHub 读取这个仓库
我们还没有从 GitHub 读取这个仓库
它在你的电脑上运行,没有互联网端点
在你的电脑上运行,改用本地设置
它在你的电脑上运行;我们只能读取互联网端点的工具列表
与注册中心里这个分类中所有活跃的服务器比较。只有当发布者拥有该仓库时,星标数才计入。
它在 1 项适用的基础检查中通过了 1 项。我们没有阅读代码。在添加密钥或令牌之前,请先看看这个服务器要求哪些权限,并使用只具备所需权限的密钥。
注册中心没有列出必需的密钥,不过有些服务器会在首次使用时要求你登录。
它在你的电脑上运行。你的 AI 应用会在需要时启动它,数据不会经过作者的服务器(除非它自己调用在线服务)。
GitHub 仓库最后更新于–,最新版本(0.15.0)于5个月前进入注册中心。
支持 MCP 的应用,例如 Claude Desktop、Claude Code、Cursor 和 VS Code。你的电脑上还需要有 Node.js。
同一分类中有:Spec Driven Development, Remote Desktop Commander, SSTracker free youth training
同一分类中其他作者的服务器,按星标数排序。
如何看卡片:★ 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.
Free youth sports drills, practice plans and age-group answers for parents and coaches.
按原文从作者的仓库复制。PopNx MCP 没有审查或背书其内容。HTML、图片和脚本已被移除。链接会离开本站。
Local MCP server for PEAC signed interaction records. It exposes tools to verify, inspect, decode, issue, and bundle PEAC records through stdio or the local Streamable HTTP transport.
pnpm add @peac/mcp-server
Or run directly:
npx @peac/mcp-server
@peac/mcp-server exposes PEAC signed interaction record operations as Model Context Protocol (MCP) tools that AI agents and LLM-based applications can call. It supports both stdio and Streamable HTTP transports, with static policy checks, concurrency limits, input size guards, and structured error responses with recovery hints.
Add to ~/Library/Application Support/Claude/claude_desktop_config.json:
{
"mcpServers": { "peac": { "command": "npx", "args": ["-y", "@peac/mcp-server"] } } }
Add to .mcp.json at your project root:
{
"mcpServers": { "peac": { "command": "npx", "args": ["-y", "@peac/mcp-server"] } } }
npx @peac/mcp-server --transport http --port 3000
HTTP transport provides per-session isolation, rate limiting, and RFC 9728 PRM discovery. Binds to 127.0.0.1 by default. See examples/mcp-http-quickstart/ for an end-to-end demo.
npx @peac/mcp-server \
--issuer-key env:PEAC_ISSUER_KEY \ --issuer-id https://example.com
npx @peac/mcp-server --transport http --port 3000
| Flag | Description | Default |
|---|---|---|
--transport | Transport: stdio or http | stdio |
--port | HTTP port | 3000 |
--host | HTTP bind address | 127.0.0.1 |
--issuer-key | Issuer key reference (env:VAR or file:/path) | None |
--issuer-id | Issuer identifier URI | None |
--policy | Policy configuration file path | Built-in default |
--jwks-file | JWKS file for verifier key resolution | None |
--bundle-dir | Directory for evidence bundle output | None |
--cors-origins | Allowed CORS origins (comma-separated, HTTP only) | None |
--trust-proxy | Trust X-Forwarded-For (off, loopback, private) | off |
Handlers can be used directly without the MCP server binding:
import { createPeacMcpServer, handleVerify } from '@peac/mcp-server';
import { getDefaultPolicy, computePolicyHash } from '@peac/mcp-server';
const policy = getDefaultPolicy(); const policyHash = await computePolicyHash(JSON.stringify(policy));
const result = await handleVerify({ input: { jws: 'eyJ...', public_key_base64url: '...' }, policy, context: { version: '0.16.5', policyHash, protocolVersion: '2025-11-25', }, });
| Tool | Description | Availability |
|---|---|---|
peac_verify | Verify a PEAC signed interaction record. | Always |
peac_inspect | Inspect a PEAC signed interaction record without verification. | Always |
peac_decode | Decode a PEAC receipt JWS header and payload for diagnostics. | Always |
peac_issue | Issue a PEAC signed interaction record from provided claims. | Requires --issuer-key and --issuer-id |
peac_create_bundle | Create a PEAC bundle from signed records and related artifacts. | Requires --issuer-key, --issuer-id, and --bundle-dir |
All structured tool outputs include a schema-declared _meta audit block with serverVersion, policyHash, protocolVersion, and registeredTools. This is separate from the top-level MCP _meta carrier used by @peac/mappings-mcp to attach PEAC receipt references.
@peac/protocol (Layer 3): signed-record issuance and verification@peac/crypto (Layer 2): JWS signing and decoding@peac/schema (Layer 1): Receipt schema validation@peac/kernel (Layer 0): Error codes and constants@modelcontextprotocol/sdk: MCP server and transport bindingsConnect your agent to this server over stdio or HTTP to gain signed-record verification, receipt decoding, and issuance capabilities. The tools use structured outputs with error codes and next_action recovery hints so your agent can handle failures programmatically. Every response includes _meta for audit and traceability.
Read-only tools (peac_verify, peac_inspect, peac_decode) are available with no configuration. To enable issuance, provide an Ed25519 signing key via --issuer-key and --issuer-id.
The server applies static policy checks with configurable concurrency limits, input size bounds, JWS size caps, and tool timeouts. HTTP transport binds to localhost by default with CORS deny-all. The stdout fence prevents non-JSON-RPC output from corrupting the stdio transport.
Security properties: no ambient key discovery (keys must be explicitly provided), no implicit network fetches from tool handlers, path traversal prevention on bundle output, and session isolation on HTTP transport.
Apache-2.0
PEAC Protocol is an open source project stewarded by Originary and community contributors.