Spec Driven Development
MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.
Description from the maker (original English)
Early access - AI governance gateway for MCP tool calls (policies, PII masking, audit).
These three are never merged into one score: opinions, measurements and popularity are different things.
We have not written a plain-language summary for this one yet. Below are the facts we read from the registry.
Pick the AI app you use, then copy the settings.
You need
Which app do you use?
Pick your app above. We remember it, so next time the button says “Install in …”.
Open Claude Desktop → Settings → Developer → Edit Config, and paste this into claude_desktop_config.json
{
"mcpServers": {
"palveron": {
"command": "npx",
"args": [
"-y",
"@palveron/mcp-server"
]
}
}
}Run this in your terminal
claude mcp add palveron -- npx -y @palveron/mcp-serverPaste into .cursor/mcp.json in your project, or ~/.cursor/mcp.json
{
"mcpServers": {
"palveron": {
"command": "npx",
"args": [
"-y",
"@palveron/mcp-server"
]
}
}
}Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.
Paste into .vscode/mcp.json in your project
{
"servers": {
"palveron": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"@palveron/mcp-server"
]
}
}
}Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.
This one runs on your computer, and ChatGPT can only connect to servers on the internet. Pick another app.
Your choice stays on this device in a cookie; no account needed.
These settings are generated from the maker’s registry entry. If the README says otherwise, follow the README.
Runs on your computer; the tool list appears in your AI app after you install it.
We check information anyone can see; we have not read the code. Checks that do not apply are left out of the count. · Checked Nov 7, 2026
The registry name was verified with the GitHub account palveron, which owns the repo
We have not read this repo from GitHub yet
We have not read this repo from GitHub yet
This one runs on your computer; there is no internet endpoint
Runs on your computer and uses local settings instead
Runs on your computer; we can only read tool lists from internet endpoints
Compared with every active server in this category in the registry. Stars count only when the publisher owns the repo.
It passed 1 of 1 applicable basic checks. We have not read the code. Before adding a key or token, see what access the server asks for and use a key with only the permissions you need.
The registry does not list a required key, though some servers ask you to sign in on first use.
It runs on your computer. Your AI app starts it when needed, and data does not pass through the maker’s servers (unless it calls an online service itself).
The GitHub repo last changed –, and the latest version (1.0.1) reached the registry 4 months ago.
Apps that support MCP, such as Claude Desktop, Claude Code, Cursor and VS Code. You also need Node.js on your computer.
In the same category: Spec Driven Development, Remote Desktop Commander, Agent Data Tools: Utilities
Servers in the same category from other makers, sorted by stars.
Reading a card:★ GitHub starsiThree pillars: reviews · checks · usageiUpdated = latest version published to the registryi
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.
103 tools: JSON repair, CSV, hashes, cron, dates, units, validators. 25 free calls.
Copied from the maker’s repo as written. PopNx MCP has not reviewed or endorsed it. HTML, images and scripts are removed. Links lead off this site.
@palveron/mcp-server Official Palveron MCP server — advisory AI-governance checks for MCP hosts and coding agents
⚡ 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](https://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.
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 | |
|---|---|---|
| Model | Voluntary pre-flight check | In-path enforcement |
| Can a call bypass it? | Yes — enforcement depends on the caller honoring the verdict | No — the proxy sits between client and target server |
| Setup | npx, one env var | Register the target server in the dashboard, point the IDE at the proxy URL |
| Use it when | You want verdicts + audit traces inside any MCP host, or wrap tool calls programmatically | You need governance that agents cannot skip |
See the MCP setup guide for the enforced path.
npm install -g @palveron/mcp-server
npx @palveron/mcp-server
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.
Add to your claude_desktop_config.json:
{
"mcpServers": { "palveron": { "command": "npx", "args": ["@palveron/mcp-server"], "env": { "PALVERON_API_KEY": "pv_live_xxx", "PALVERON_BASE_URL": "https://gateway.palveron.com" } } } }
Any MCP-capable host can launch the server via the palveron-mcp binary:
PALVERON_API_KEY=pv_live_xxx palveron-mcp
| Tool | Purpose |
|---|---|
palveron_check | Check 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_status | Governance status and diagnostics — gateway connectivity, circuit-breaker state, configured local lists. |
palveron_policy_list | List the project's active policies so the host can explain its decisions. |
The server reads its configuration from environment variables. The MCP host sets them; you never put secrets in code.
| Variable | Required | Description |
|---|---|---|
PALVERON_API_KEY | yes | API key (pv_live_…) — comes with an Early Access invite |
PALVERON_BASE_URL | no | Override the gateway endpoint (default: https://gateway.palveron.com) |
PALVERON_FAIL_OPEN | no | true = allow tool calls when the gateway is unreachable (default: false, fail-closed) |
PALVERON_LOG_LEVEL | no | debug / info / warn / error / silent (default: info) |
PALVERON_ALWAYS_BLOCK | no | Comma-separated tool names that are always denied locally, without a gateway call |
PALVERON_ALWAYS_ALLOW | no | Comma-separated tool names that always pass locally, without a gateway call |
MIT — Copyright © 2026 Palveron.