Provenza runs on your own machine — the client starts it, so there is no endpoint to ping. 762 installs a week from pypi. Last commit 31 Oct 2026.
Governed MCP gateway: approved tools only, each call policy-checked and recorded per agent
We read the source, 14 h ago · rules 995398eba69f
Things with no honest explanation: a promise that contradicts the code, code that runs at install time while hiding what it does, data leaving the machine.
r = httpx.get("http://metadata.google.internal/computeMetadata/v1/instance/service-accounts/default/identity",
Found in continuous integration, deployment or infrastructure files, or in a neighbouring package of the same monorepo. None of this is installed when you add the server: it describes how the project is built and released. We list it because a leaked key in a build pipeline is still a real problem, but it is not something this server does on your machine.
&& crontab -u "$SUDO_USER" -l 2>/dev/null | grep -Fq "$DEPLOY && ./scripts/backup.sh"; then
path := filepath.Join(o.Home, c.File)
Is this your server and something here is wrong? Tell us — corrections are free and do not require a plan.
Code changes quietly between releases, and nobody reads the diff of a dependency. We do, on every release — watch Provenza and you get told the day something new turns up.
This server runs on your own machine — install it with the package manager and the client starts it for you. Package name taken from the official registry entry.
claude mcp add provenza -e 'PROVENZA_URL=<PROVENZA_URL>' -- uvx provenza
{
"mcpServers": {
"provenza": {
"command": "uvx",
"args": [
"provenza"
],
"env": {
"PROVENZA_URL": "<PROVENZA_URL>"
}
}
}
}
[mcp_servers.provenza]
command = "uvx"
args = ["provenza"]
env = { PROVENZA_URL = "<PROVENZA_URL>" }
{
"mcpServers": {
"provenza": {
"command": "uvx",
"args": [
"provenza"
],
"env": {
"PROVENZA_URL": "<PROVENZA_URL>"
}
}
}
}
{
"servers": {
"provenza": {
"type": "stdio",
"command": "uvx",
"args": [
"provenza"
],
"env": {
"PROVENZA_URL": "<PROVENZA_URL>"
}
}
}
}
Put your own value in place of
<PROVENZA_URL> (Your self-hosted Provenza, e.g. https://provenza.example.com).
The author’s registry entry marks it as required.
Optional settings from the registry entry, left out of the block above:
PROVENZA_TOKEN (One-time enrollment token (Agents -> New agent); needed on the first start only), PROVENZA_AGENT_NAME (Agent name on this machine (default: mcp)).
MCP gateway that checks each agent tool call against a signed grant and policy, and signs a receipt
Governed MCP gateway: policy gate on every tool call, hash-chained DSSE receipt on every result.
Local MCP gateway: approved tools behind a signed authority check, per call or as exactly-once jobs
Policy checks, approvals, records, and governed HTTP capabilities for unattended agents.
Read-only evidence for the tools agents run: MCP server records, coverage and policy.
Governed MCP server: YAML-declared tools, typed effects, policy-gated and audited calls.
Policy proxy for MCP tool calls. A denied call never reaches the downstream server.
Gateway in front of MCP tools: critical arguments are checked against trusted sources and a policy.
Answers built from our own checks of this server.