Palveron MCP Server

io.github.palveron由 GitHub 帳號 palveron 發布v1.0.1更新於 Nov 10, 2026

Early access - AI governance gateway for MCP tool calls (policies, PII masking, audit).

已驗證STDIO僅桌面開發者工具安全與監控

概覽

AI 產生的概覽

Palveron 的諮詢式治理伺服器讓 MCP 主機在執行工具呼叫前詢問策略是否允許、遮罩或阻擋,並取得稽核追蹤 ID。

可以做什麼
  • 依治理策略檢查預計執行的工具呼叫,回傳判定結果(通過、阻擋、修改/遮蔽/匿名化並附上清理後的輸入、待核准)、發現項目與稽核追蹤 ID
  • 檢視治理狀態與診斷資訊,包括閘道連線狀態、斷路器狀態與已設定的本機清單
  • 列出專案目前生效的策略,讓主機能說明其判定
  • 使用本機的永遠阻擋與永遠允許工具清單,不需呼叫閘道
適用情境
當你希望在任何支援 MCP 的主機或程式碼代理中取得策略判定、PII 遮罩結果與稽核追蹤,或打算以程式方式包裝工具呼叫時使用。它僅屬諮詢性質,適合由代理或你自己的程式碼遵守判定結果的情境,而非需要不可繞過之強制執行的情境。
執行需求
需要 Node.js 18 或更新版本,以及支援 MCP 的用戶端。需在 PALVERON_API_KEY 提供 Palveron API 金鑰,目前須透過 Early Access 邀請取得。選用環境變數可設定閘道位址、失敗放行行為、日誌等級,以及永遠阻擋或永遠允許的工具清單。需要能連線至 Palveron 閘道的網路。
安裝前請注意
此金鑰是正式憑證,透過 PALVERON_API_KEY 傳入,請勿寫入程式碼或共用設定。檢查屬諮詢性質,無法真正阻止工具呼叫,是否執行取決於呼叫端是否遵守判定。預設在閘道無法連線時採失敗關閉;設定 PALVERON_FAIL_OPEN=true 會改為放行呼叫。工具呼叫的詳細資訊會傳送至 Palveron 閘道進行評估。

安裝

在 SourceWeft 中

  1. 開啟 儀表板中的 Palveron MCP Server,將其新增到工作區。
  2. 為需要使用其工具的對話啟用該服務。

Desktop only,透過 STDIO。 STDIO 服務會啟動本機處理程序,因此需要 SourceWeft 桌面主機。

其他 MCP 客戶端

參照 儲存庫 中的啟動說明。

README

@palveron/mcp-server

Official Palveron MCP server — advisory AI-governance checks for MCP hosts and coding agents

[npm version] [npm downloads] [License: MIT] [Documentation] [Early Access]


⚡ Early access. Palveron is launching soon and access is currently invite-gated. This server is fully functional — you just need a pv_live_ key, which comes with an Early Access invite. Join the waitlist → palveron.com/early-access

Give your MCP-capable client — Claude Code, Cursor, any other MCP host — governance tools it can call before executing an action: policy verdicts, PII-masking results, and an audit trace for every check, all from the Palveron AI Governance Gateway.

  • Drop-in MCP server — one binary, configure your MCP host, you're done
  • Advisory governance verdicts — the gateway decides allow / mask / deny / hold; the agent (or your wrapping code) acts on the verdict
  • Audit trail per check — trace IDs flow back to the Palveron dashboard
  • Built on @palveron/sdk — retry, circuit breaker, typed errors out of the box

Advisory check vs. enforced governance — which one do you need?

This package is the advisory path. It cannot physically stop a tool call: it answers the question "is this allowed?", and the calling agent (or your code via check()/wrap()) is expected to honor the answer. That is by design — it works with any MCP host, needs no network topology change, and gives you verdicts plus audit traces immediately.

Enforced, non-bypassable governance for MCP tool calls is a different product surface: the Palveron remote MCP proxy. There you register the target MCP server in the Palveron dashboard and point your IDE at POST {gateway}/api/v1/mcp/proxy/{server_id} instead of the target — every tools/call then structurally passes through policy checks, approval holds, and drift detection before it can reach the target server. No cooperation from the agent required.

This package (@palveron/mcp-server)Remote MCP proxy
ModelVoluntary pre-flight checkIn-path enforcement
Can a call bypass it?Yes — enforcement depends on the caller honoring the verdictNo — the proxy sits between client and target server
Setupnpx, one env varRegister the target server in the dashboard, point the IDE at the proxy URL
Use it whenYou want verdicts + audit traces inside any MCP host, or wrap tool calls programmaticallyYou need governance that agents cannot skip

See the MCP setup guide for the enforced path.

Installation

bash
npm install -g @palveron/mcp-server# or use directly via npxnpx @palveron/mcp-server

Quick Start

The pv_live_… key in the examples below requires an Early Access invite — request one here. Once you have a key, everything works out of the box.

Claude Code

Add to your claude_desktop_config.json:

json
{  "mcpServers": {    "palveron": {      "command": "npx",      "args": ["@palveron/mcp-server"],      "env": {        "PALVERON_API_KEY": "pv_live_xxx",        "PALVERON_BASE_URL": "https://gateway.palveron.com"      }    }  }}

Other MCP hosts

Any MCP-capable host can launch the server via the palveron-mcp binary:

bash
PALVERON_API_KEY=pv_live_xxx palveron-mcp

Tools exposed via MCP

ToolPurpose
palveron_checkCheck a tool call against governance policies before execution. Returns the decision (PASSED, BLOCKED, MODIFIED/REDACTED/ANONYMIZED with the sanitized input, PENDING_APPROVAL, …), whether the call may proceed, findings, and the audit trace ID.
palveron_statusGovernance status and diagnostics — gateway connectivity, circuit-breaker state, configured local lists.
palveron_policy_listList the project's active policies so the host can explain its decisions.

Configuration

The server reads its configuration from environment variables. The MCP host sets them; you never put secrets in code.

VariableRequiredDescription
PALVERON_API_KEYyesAPI key (pv_live_…) — comes with an Early Access invite
PALVERON_BASE_URLnoOverride the gateway endpoint (default: https://gateway.palveron.com)
PALVERON_FAIL_OPENnotrue = allow tool calls when the gateway is unreachable (default: false, fail-closed)
PALVERON_LOG_LEVELnodebug / info / warn / error / silent (default: info)
PALVERON_ALWAYS_BLOCKnoComma-separated tool names that are always denied locally, without a gateway call
PALVERON_ALWAYS_ALLOWnoComma-separated tool names that always pass locally, without a gateway call

Requirements

  • Node.js 18 or newer
  • An MCP-capable client (Claude Code 0.4+, Cursor, etc.)

Links

License

MIT — Copyright © 2026 Palveron.

來源:README.md,提交 536ec7d

工具

0
SourceWeft 尚未在沙箱中啟動過該軟體包,因此其工具未知。

版本歷史

1
  1. v1.0.1最新Sep 16, 2026

評分

已滿足適用檢查項的 50%

該評分衡量此收錄條目的完整程度,依據註冊中心條目、端點與公開來源計算得出。它不是對伺服器本身的評價,也不表示伺服器安全或目前可用:可連通性是帶日期的檢查結果,評分也不包含安裝量或使用者評價。

  • 近 30 天內可連通25 分

    請保持端點能夠回應 MCP 握手;SourceWeft 每 30 天探測一次。

  • 已宣告認證方式10 分

    請在註冊中心條目中宣告憑證請求標頭,或保持端點能夠回應探測,以便判定其認證方式。

  • 已列出工具15 分

    請讓伺服器在無憑證時回應 tools/list,或發布可在沙箱中無憑證啟動的軟體包。

  • 描述必需15 分
  • 圖示10 分
  • 文件15 分
  • 授權條款10 分