Palveron Governance Gateway

io.github.palveronPublished by GitHub account palveronv1.0.4Updated Oct 24, 2026

Advisory governance checks for MCP hosts; enforcement runs in the Palveron remote MCP proxy.

VerifiedSTDIODesktop onlyDeveloper ToolsSecurity & Monitoring

Overview

AI-generated overview

A local MCP server that gives assistants advisory Palveron governance checks — policy verdicts, PII masking results and audit trace IDs — before a tool call.

What you can do
Check a proposed tool call against governance policies and get a verdict (passed, blocked, modified/redacted/anonymized with sanitized input, pending approval), findings and an audit trace ID. Query governance status and diagnostics such as gateway connectivity, circuit-breaker state and configured local lists. List the project's active policies so the host can explain decisions. Apply local always-block and always-allow tool lists without calling the gateway.
When to use it
Use it when you want policy verdicts and audit traces inside any MCP host, or want to wrap tool calls programmatically with Palveron checks. It is advisory only: the calling agent or your code must honor the verdict. For non-bypassable enforcement, the vendor points to its separate remote MCP proxy instead.
Requirements
Runs locally via npm package @palveron/mcp-server (npx or global install) on Node.js 18 or newer, with an MCP-capable client. Requires a Palveron API key in PALVERON_API_KEY, which is invite-gated through Early Access. Optional settings: PALVERON_BASE_URL, PALVERON_FAIL_OPEN, PALVERON_LOG_LEVEL, PALVERON_ALWAYS_BLOCK, PALVERON_ALWAYS_ALLOW. Network access to the Palveron gateway.
Before you install
The API key PALVERON_API_KEY is a secret set through the host's environment configuration. Checks are advisory and can be bypassed if the agent ignores the verdict; by default the server fails closed when the gateway is unreachable, and PALVERON_FAIL_OPEN=true allows calls instead. Tool call details, including inputs that may contain personal data, are sent to the Palveron gateway, and trace IDs link back to the Palveron dashboard.

Installation

In SourceWeft

  1. Open Palveron Governance Gateway in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.

Other MCP clients

Follow the launch instructions in the repository.

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.

Source: README.md at commit 536ec7d

Tools

0
SourceWeft has not started this package in its sandbox yet, so its tools are not known.

Version history

1
  1. v1.0.4LatestSep 16, 2026

Score

50% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 days25 pts

    Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.

  • Auth declared10 pts

    Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.

  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts
  • License10 pts