프로토타입 · 미리 보기: 공식 레지스트리의 모든 서버를 담고 있으며 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의 세 기둥

이 세 가지는 절대 하나의 점수로 합치지 않아요. 의견, 측정, 인기는 서로 다른 것이니까요.

할 수 있는 일

이 서버는 아직 쉬운 말로 된 요약을 쓰지 못했어요. 아래는 레지스트리에서 읽어 온 사실이에요.

  • 연결 방식: 내 컴퓨터에서 실행
  • 전송 방식: 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는 인터넷에 있는 서버에만 연결할 수 있어요. 다른 앱을 고르세요.

선택한 앱은 이 기기의 쿠키에만 저장돼요. 계정은 필요 없어요.

직접 입력할 값

  • 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

  • 이 카테고리의 다른 서버 32683개 중 0%보다 스타가 많아요
  • 이 카테고리의 다른 서버 32683개 중 43%보다 최근에 레지스트리에 공개됐어요
  • 기본 점검 결과가 이 카테고리의 다른 서버 32683개 중 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, MCP Server Autocad Lisp Helper

대안

같은 카테고리에서 다른 제작자가 만든 서버예요. 스타 순으로 정렬했어요.

카드 보는 법:★ GitHub 스타i세 기둥: 리뷰 · 점검 · 사용 정도i업데이트 = 최신 버전을 레지스트리에 공개한 날i

Spec Driven Development

제작자: formulahendry

MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.

내 컴퓨터에서 실행★ 440MIT14개월 전 업데이트
설치

Remote Desktop Commander

제작자: desktop-commander

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

클라우드에서 실행★ 211그저께 업데이트
설치

MCP Server Autocad Lisp Helper

제작자: radwanalmsora

High-precision static analysis and debug server for AutoCAD AutoLISP (.lsp) files.

내 컴퓨터에서 실행오늘 업데이트
설치

제작자의 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에게 묻기