Spec Driven Development
MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.
作者提供的说明(英文原文)
Non-custodial Kaspa policy enforcement for AI agents; signers retain custody.
这三项永远不会合并成一个分数:意见、测量和人气是不同的东西。
我们还没有为它写通俗的介绍。下面是我们从注册中心读取到的事实。
选择你使用的 AI 应用,然后复制设置。
POLICYVAULT_MCP_SERVER_URL, POLICYVAULT_MCP_TOKEN, POLICYVAULT_MCP_SCOPES标为机密的值是你账户的钥匙。千万不要分享给别人,也不要粘贴到聊天里。
你需要
你用的是哪个应用?
在上方选择你的应用。我们会记住它,下次按钮会显示“安装到 …”。
打开 Claude Desktop → Settings → Developer → Edit Config,把下面的内容粘贴到 claude_desktop_config.json
{
"mcpServers": {
"policyvault": {
"command": "npx",
"args": [
"-y",
"policyvault-mcp"
],
"env": {
"POLICYVAULT_MCP_SERVER_URL": "your-value",
"POLICYVAULT_MCP_TOKEN": "your-value",
"POLICYVAULT_MCP_SCOPES": "your-value"
}
}
}
}在终端中运行这条命令
claude mcp add policyvault --env POLICYVAULT_MCP_SERVER_URL=your-value --env POLICYVAULT_MCP_TOKEN=your-value --env POLICYVAULT_MCP_SCOPES=your-value -- npx -y policyvault-mcp运行前请先填写空着的值。
粘贴到项目中的 .cursor/mcp.json,或 ~/.cursor/mcp.json
{
"mcpServers": {
"policyvault": {
"command": "npx",
"args": [
"-y",
"policyvault-mcp"
],
"env": {
"POLICYVAULT_MCP_SERVER_URL": "your-value",
"POLICYVAULT_MCP_TOKEN": "your-value",
"POLICYVAULT_MCP_SCOPES": "your-value"
}
}
}
}浏览器会先询问是否打开应用,然后应用会显示设置并请你确认。密钥的值会留空,由你自己填写。
粘贴到项目中的 .vscode/mcp.json
{
"servers": {
"policyvault": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"policyvault-mcp"
],
"env": {
"POLICYVAULT_MCP_SERVER_URL": "your-value",
"POLICYVAULT_MCP_TOKEN": "your-value",
"POLICYVAULT_MCP_SCOPES": "your-value"
}
}
}
}浏览器会先询问是否打开应用,然后应用会显示设置并请你确认。密钥的值会留空,由你自己填写。
这个服务器在你的电脑上运行,而 ChatGPT 只能连接互联网上的服务器。请选择其他应用。
你的选择通过 Cookie 保存在这台设备上,无需账户。
POLICYVAULT_MCP_SCOPES env这些设置是根据作者在注册中心的条目生成的。如果 README 的写法不同,请以 README 为准。
它在你的电脑上运行;安装后,工具列表会显示在你的 AI 应用中。
我们检查的是任何人都能看到的信息;我们没有阅读代码。不适用的检查项不计入总数。 · 检查于 2026年11月7日
注册名称已通过 GitHub 账户 zapsoblige-hash 验证,该账户拥有此仓库
我们还没有从 GitHub 读取这个仓库
我们还没有从 GitHub 读取这个仓库
它在你的电脑上运行,没有互联网端点
在你的电脑上运行,改用本地设置
它在你的电脑上运行;我们只能读取互联网端点的工具列表
与注册中心里这个分类中所有活跃的服务器比较。只有当发布者拥有该仓库时,星标数才计入。
它在 1 项适用的基础检查中通过了 1 项。我们没有阅读代码。在添加密钥或令牌之前,请先看看这个服务器要求哪些权限,并使用只具备所需权限的密钥。
你需要填写:POLICYVAULT_MCP_SERVER_URL, POLICYVAULT_MCP_TOKEN
它在你的电脑上运行。你的 AI 应用会在需要时启动它,数据不会经过作者的服务器(除非它自己调用在线服务)。
GitHub 仓库最后更新于–,最新版本(1.6.2)于2个月前进入注册中心。
支持 MCP 的应用,例如 Claude Desktop、Claude Code、Cursor 和 VS Code。你的电脑上还需要有 Node.js。
同一分类中有:Spec Driven Development, Remote Desktop Commander, Date Math
同一分类中其他作者的服务器,按星标数排序。
如何看卡片:★ 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.
Exact date/time math for agents: business days, holidays, time zones, cron, RRULE, SLA. x402 paid.
按原文从作者的仓库复制。PopNx MCP 没有审查或背书其内容。HTML、图片和脚本已被移除。链接会离开本站。
Non-custodial delegated-spending vaults on Kaspa L1 — for people and AI agents.
PolicyVault lets a vault owner hand a spending key to an agent — an employee, a service, a bot, or an AI agent — without handing over control of the funds. The spending policy is enforced by Kaspa L1 consensus through a covenant: even an agent who bypasses this entire application and talks directly to a Kaspa node cannot exceed the owner's policy.
The authority model, stated once and everywhere enforced:
**AI MAY REQUEST. POLICYVAULT DETERMINISTICALLY DECIDES.
THE COVENANT ENFORCES. SIGNERS RETAIN CUSTODY.**
| Surface | Status |
|---|---|
| Web / Agent platform | Service at https://app.policy-vault.org; served health identifies the active build. This tree corresponds to fullscale-rc45 build 1fa26b33, the reconciliation and delegate period-start remediation successor of fullscale-rc44 (df5b8de). |
| Current production source | This tree is v1.10.11 (fullscale-rc45), image sha256:32d45a3096b29eefc0dd97f2fc1e582ee00cb32236bbd7293c6626fd8bd4652d; its published predecessor is v1.10.10. Preparation does not imply deployment; served health identifies the active build. |
| Organizational M-of-N owner root (covenant v0.7) | The existing RC40 mainnet generation policy is retained. This release does not change creation authority, covenant bytes or native-KAS status labels. |
| Rooted-vault owner operations in the browser (R7-05) + reservation/withdrawal guidance (F-6) | Retained; signing-threshold behavior is unchanged. Rooted-vault owner operations and approvals change in this release; the changelog's delegate period-start and organization-root items list the changes, among them: a delegate rule change of a policyvault-0.7-kas treasury must collect every owner approval and be finalized within the new or changed delegate's budget period minus ten minutes of the build (never less than one minute; 50 minutes for a 1-hour period), and the root request shows its finalize deadline; after it PolicyVault does not finalize the request, which can then only be withdrawn and built again (the web has no input for a later start), and such a request that was never attempted can be withdrawn although it carries owner approvals; a new delegate of a policyvault-0.7-kas treasury starts its budget period at the network position read when Build is pressed and an installed delegate's wallet on such a treasury is changed by removing and re-adding the delegate; a root request is refused when it spends an output that the node does not report unspent; hosted builds, finalize and broadcast on a treasury that Verify left UNRESOLVED are refused (an approval of an existing delegate request on it is still recorded but cannot reach the chain, and a withdrawal of a delegate request on it and a Verify of it still answer); Verify can attribute a root move broadcast outside PolicyVault to the recorded request whose transaction made it; and a finalized root request's Submit first reads its inputs and, after an input was spent by another transaction, the request can be withdrawn in two steps. Five served assets (app-v4.js, app.js, kas-vault-ui.js, org-root-ui.js, refusal-explain.js) change for v0.4-family Verify, request, delegate period-start, legacy-console and organization-root presentation. |
| Hosted tenancy for every route family + generation gate (rc11 remediation) | LIVE — closes the rc8 findings (unauthenticated hosted builds, prototype-derived version selection, unsafe mainnet creation of the non-standard v0.4 generation) |
| Post-launch live-stack review corrections (rc29: webhook target policy + DNS transport, SDK transport recovery key, legacy same-effect completion ownership, image/package LICENSE + NOTICE, privacy-safe runtime artifacts, recovery guidance) | IN THIS SOURCE and in the `fullscale-rc29` image — every finding of the independent read-only review of the running rc28 stack corrected RED-first with a permanent regression; the hosted deployment carries them once the served buildId reads f217011; installed SDK / mobile clients must upgrade for the transport correction |
| Second post-launch review corrections (rc30: webhook response-socket lifetime bound; upstream Silverscript ISC notice beside the compiler and the reference program) | IN THIS SOURCE and in the `fullscale-rc30` image — both findings of the independent read-only launch review of the running rc29 stack corrected RED-first with a permanent real-socket regression; the hosted deployment carries them once the served buildId reads 9dbc5f7; no SDK / mobile client byte changed |
| Organization UI availability correction (rc31: organizational-root creation offered only where capability discovery advertises it; generation refusals say that address/amount changes cannot enable an unsupported mainnet generation; build errors scoped to the wizard) | IN THIS SOURCE and in the `fullscale-rc31` image — the owner-observed RC30 finding, corrected RED-first with a 13-case DOM regression that drives the real page and scripts (synthetic wallet, intercepted HTTP); browser presentation only — the server / SDK generation gates are unchanged and remain the authority; no SDK / mobile client byte changed |
MCP package (policyvault-mcp on npm) | Unchanged policyvault-mcp@1.6.2, SHA256 128403f81d4af7b73ae86a31a750d39ec21c28f518d214f4e678807c3dff0c14. No genesis, signature or submission tool is exposed. Against this server, retrying the same MCP request after an uncertain outcome is refused (IDEMPOTENCY_OUTCOME_UNKNOWN, or IDEMPOTENCY_IN_PROGRESS after a server or store failure) or returns the retained result, instead of executing the operation again. The reject tool reports 403 REQUEST_FORBIDDEN when the credential's wallet takes part in the vault but is neither the request's signer nor the vault owner. A delegate period start sent through MCP is a lower bound; 422 PERIOD_START_REQUIRED reaches the caller as a REFUSED envelope (no MCP tool reaches the later checks that answer 409 PERIOD_START_STALE). |
| Flagship wave 1 (v1.6.0 / v1.7.0) and wave 2 (v1.8.0) source | INCLUDED and LIVE where applicable (see their CHANGELOG entries; v0.6 stays FIXTURE VENUE ONLY / no mainnet swap; x402 facilitator PRODUCTION-READY, NOT deployed; MCP usage telemetry OFF) |
| Covenant protocol v0.6 (atomic composability) | COVENANT-BYTE-FROZEN (2026-09-03): VM-verified on the real engine with production bytes and testnet-verified (live testnet-10 SELL + BUY). FIXTURE VENUE ONLY — no real DEX venue, no mainnet swap, no server/web/mobile/MCP surface, deadlineDaa is a pre-sign boundary and not a consensus expiry, and swaps are not economically viable below roughly 10 KAS. PolicyVault is not a DEX and will not become one. See docs/postlaunch/v0.6-covenant-byte-freeze.md |
| v0.5 token-controller covenant (byte-frozen) + least-privilege discovery / console correctives + MCP 1.4.2 (v1.5.0) | LIVE — production runtime successor fullscale-rc8 (buildId 1c02162) deployed and automated-accepted on 2026-09-02: principal-scoped capability discovery, no dev-signer probe on production, zero privileged reads while signed out, opt-in wallet diagnostics; policyvault-mcp@1.4.2 advertises only the tools a credential's scopes cover (server-side enforcement unchanged). The v0.5 TOKEN CONTROLLER covenant (contracts/PolicyVault.v0.5.sil, sha256 c693aeff…) ships as SOURCE — COVENANT-BYTE-FROZEN, VM-verified with production bytes and testnet-verified with one live lifecycle; NOT production (no v0.5 surface, no mainnet v0.5 vault). Illustrated onboarding walkthrough (presentation only). See CHANGELOG |
| Distribution: MCP registry, agent examples, self-hosting (v1.4.0) | Source/distribution release — NO runtime change (production keeps buildId 6c3177f): the MCP server is npm/registry-packaged (policyvault-mcp, io.github.zapsoblige-hash/policyvault), thin OpenAI-Agents-SDK/LangChain/CrewAI wiring examples ship in examples/agents/, and one-command self-hosting ships in deploy/selfhost.sh + docs/selfhost-quickstart.md; see CHANGELOG |
| Bearer wallet-sessions + native mobile transport (v1.3.0) | LIVE: opt-in bearer wallet-session authentication for non-browser clients (authentication only — never signing authority or custody; cookie web auth unchanged), plus the native Android transport (explicit CapacitorHttp at the platform seam; no CORS widening, web client stays strict same-origin). The full bearer lifecycle was proven from the real packaged Android runtime against live production; see CHANGELOG |
| Responsive client + quiet signed-out UX (v1.2.0) | Faster signed-in navigation (retained state, parallel reads, truthful progress states — pending is never success) and no spurious signed-out error toasts; see CHANGELOG |
| Network-identity banner fix (v1.1.1) | The web client's network banner now derives from the server's node-verified /network/status and FAILS CLOSED to an explicit UNKNOWN state — never a stale or assumed network; see CHANGELOG |
| In-app documentation discovery (v1.1.0) | Docs link + contextual help in the web client, deep-linking to https://docs.policy-vault.org — presentation-only successor; see CHANGELOG |
| External-approver discovery fix (2026-08-27) | DEPLOYED + AUTOMATED-ACCEPTED (fail-closed availability defect, no funds/authority/privacy exposure; see CHANGELOG "Fixed". Acceptance was automated; no human acceptance test is claimed) |
| Covenant protocol v0.4.1 | Mainnet-operational (real mainnet lifecycle evidence; see SECURITY.md for exactly what is proven and how) |
| Covenant protocol v0.5 (token controller) | COVENANT-BYTE-FROZEN (2026-09-02): VM-verified on the real engine with production bytes and testnet-verified (live testnet-10 lifecycle, consensus-rejected negatives); not production — no server/API/web surface, no mainnet instance; see docs/postlaunch/v0.5-covenant-byte-freeze.md |
| Python client, MCP server, x402/AP2 adapters, platform agent API | Shipped; covered by the automated conformance/integration suites in this repository |
| Native mobile (iOS/Android) | DEVELOPMENT — NOT YET PRODUCTION-CAPABLE. The Android app (full Capacitor project in mobile/, incl. the native production transport and bearer sign-in) has been validated on a real emulator against live production — reads, full bearer auth lifecycle, fail-closed negatives — but production signing, store packaging, and camera/QR capture remain pending; do not build custody workflows on it yet |
| Security assurance | INTERNAL and evidence-based only: independent internal AI falsification reviews of each exact candidate (the reviewer never repairs its own candidate), hostile / adversarial testing on the real Kaspa script engine with production bytes, RED-first reproduction with permanent regressions, production-shaped mechanical verification, live testnet-10 evidence, exact artifact and frozen-byte verification, and the owner's own live mainnet validation after each deployment. No external professional security audit has occurred and none is part of PolicyVault's process (owner policy, 2026-09-05); nothing in this repository claims otherwise |
docs/postlaunch/x402-facilitator-design-freeze.md) · IMPLEMENTED · UNIT-TESTED · ADVERSARIAL-TESTED · INTEGRATION-TESTED (real HTTP service + real PostgreSQL claim store) · TESTNET-VERIFIED (real KAS + real frozen-v0.5 token payments on testnet-10; docs/testnet-x402-facilitator-evidence.json). A separately deployed, unprivileged, READ-ONLY chain verification / settlement attestation service for the proposed Kaspa scheme pv-x402-kaspa-exact-upfront/1 (network identifiers kaspa:mainnet / kaspa:testnet-10 are PolicyVault's provisional CAIP-2-syntax只显示了开头部分;其余内容请在仓库中阅读