プロトタイプ · プレビュー版:公式レジストリのすべてのサーバーを掲載し、30分ごとに同期しています。レビューとアカウント機能は今後のステップで始まります。
PopNx MCPAIを使う人のためのMCPサーバー · やさしい言葉で解説

Policyvault

作者:zapsoblige-hashバージョン 1.6.2i★ –iパソコンで動く
レジストリ名io.github.zapsoblige-hash/policyvault

インストール

概要

作者による説明(英語の原文)

Non-custodial Kaspa policy enforcement for AI agents; signers retain custody.

PopNx MCPの3つの柱

この3つを1つのスコアにまとめることはしません。意見、測定、人気はそれぞれ別のものだからです。

できること

このサーバーのやさしい解説はまだ書いていません。以下はレジストリから読み取った事実です。

  • 接続方法: パソコンで動く
  • トランスポート: stdio
  • カテゴリ: その他
  • 入力が必要なもの:POLICYVAULT_MCP_SERVER_URL, POLICYVAULT_MCP_TOKEN

インストール

使っているAIアプリを選んで、設定をコピーしてください。

インストールの前に

  • 基本チェック:1項目中1項目に合格
  • あなたのパソコンで、あなたのユーザーと同じ権限(ファイル、ネットワーク、アプリ)で動きます。
  • 自分で入力するもの: POLICYVAULT_MCP_SERVER_URL, POLICYVAULT_MCP_TOKEN, POLICYVAULT_MCP_SCOPES

「秘密」と表示された値は、あなたのアカウントの鍵です。絶対に人に教えたり、チャットに貼り付けたりしないでください。

必要なもの

  • npmNode.jsのインストール(npxコマンドに必要)

どのアプリを使っていますか?

上でアプリを選んでください。選んだアプリを覚えておくので、次からはボタンに「…にインストール」と表示されます。

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で開く

または、設定を自分でコピーする

プロジェクトの .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"
      }
    }
  }
}

ブラウザがアプリを開いてよいか確認し、そのあとアプリが設定を表示して確認を求めます。キーの値は空欄のままなので、自分で入力してください。

VS Codeで開く

または、設定を自分でコピーする

プロジェクトの .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_SERVER_URL 必須 env
    Bare origin of the PolicyVault server (e.g. https://app.policy-vault.org, or your self-hosted origin). Refused if it embeds credentials or a path.
  • POLICYVAULT_MCP_TOKEN 秘密 必須 env
    Machine-identity bearer credential (pvmk_...), minted by the vault operator in the PolicyVault app with exactly the scopes the agent should hold. Never logged; deleted from the process environment af…
  • POLICYVAULT_MCP_SCOPES env
    Optional comma-separated scope list to narrow which tools are advertised (display-side only; enforcement is always server-side).

この設定は、作者のレジストリ登録情報から作成しています。READMEと違う場合は、READMEに従ってください。

できること

パソコンで動くサーバーです。インストールすると、ツール一覧がAIアプリに表示されます。

基本チェックi

誰でも見られる情報をチェックしており、コードは読んでいません。当てはまらない項目は数に入れていません。 · 2026年11月7日にチェック

  • ✓ 合格

    作者とリポジトリが一致

    レジストリ名は、リポジトリを所有するGitHubアカウント zapsoblige-hash で確認済みです

  • … 未チェック

    今もメンテナンスされている

    このリポジトリはまだGitHubから読み取っていません

  • … 未チェック

    ライセンスがある

    このリポジトリはまだGitHubから読み取っていません

  • – 対象外

    エンドポイントが応答する

    これはパソコンで動くため、インターネット上のエンドポイントはありません

  • – 対象外

    OAuthでサインイン

    パソコンで動き、代わりにローカルの設定を使います

  • … 未チェック

    ツールの説明に隠れた指示がない

    パソコンで動くサーバーです。ツール一覧を読み取れるのは、インターネット上のエンドポイントがある場合だけです

その他のほかのサーバーとの比較i

  • このカテゴリのほかの32691件のうち0%よりスターが多い
  • このカテゴリのほかの32691件のうち43%より最近レジストリに公開
  • 基本チェックの結果が、このカテゴリのほかの32691件のうち100%と同じかそれ以上

レジストリでこのカテゴリにある有効なすべてのサーバーと比較しています。スターは、公開者がリポジトリの所有者である場合だけ数えます。

よくある質問

Policyvaultは安全ですか?

当てはまる基本チェック1項目のうち1項目に合格しました。コードは読んでいません。キーやトークンを追加する前に、サーバーがどんなアクセスを求めているかを確認し、必要な権限だけを持つキーを使ってください。

どんなキーやコードが必要ですか?

入力が必要なもの:POLICYVAULT_MCP_SERVER_URL, POLICYVAULT_MCP_TOKEN

パソコンで動きますか、それともクラウドですか?

あなたのパソコンで動きます。必要なときにAIアプリが起動し、データは作者のサーバーを通りません(サーバー自体がオンラインサービスを呼び出す場合を除きます)。

今もメンテナンスされていますか?

GitHubリポジトリの最終更新は–、最新バージョン(1.6.2)がレジストリに届いたのは2 か月前です。

どのアプリで使えますか?

Claude Desktop、Claude Code、Cursor、VS CodeなどのMCP対応アプリで使えます。パソコンにNode.jsも必要です。

代わりに使えるものは?

同じカテゴリには:Spec Driven Development, Remote Desktop Commander, Dialyne

代わりの候補

同じカテゴリで、ほかの作者が作ったサーバー。スターの多い順。

カードの見方:★ GitHubスターi3つの柱:レビュー · チェック · 利用状況i更新=最新バージョンをレジストリに公開した日i

Remote Desktop Commander

作者:desktop-commander

Remote Desktop Commander: use files, terminal and processes on your own computers from any AI app.

クラウドで動く★ 211一昨日更新
インストール

Dialyne

作者:dialyne

Real phone calls in France for AI agents: dial +33 numbers, menus, hold, AI disclosure.

クラウドで動く今日更新
インストール

作者のREADME

READMEを開く

作者のリポジトリから書かれたとおりにコピーしたものです。PopNx MCPは内容を確認・推奨していません。HTML、画像、スクリプトは取り除いています。リンクはこのサイトの外へ移動します。

PolicyVault

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.**

Production status (honest labels)

SurfaceStatus
Web / Agent platformService 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 sourceThis 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) sourceINCLUDED 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.1Mainnet-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 APIShipped; 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 assuranceINTERNAL 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
  • x402 FACILITATOR (`integrations/x402-facilitator/`, 2026-09-02): DESIGN FROZEN (owner-authorized; 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

冒頭だけを表示しています。続きはリポジトリで読めます

PopNxに聞く