Infraveil Control Plane runs on your own machine — the client starts it, so there is no endpoint to ping. 2 installs a week from pypi.
Govern your backend control plane from your AI agent - signed, human-approval-gated.
The linked repository no longer exists on GitHub — it was deleted or made private.
This one has been quiet for a while
Quiet is not dead — but it is worth knowing when it wakes up, or when someone else takes it over. We watch the repository and tell you either way.
Connect this server
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 control-plane -e 'INFRAVEIL_BASE_URL=<INFRAVEIL_BASE_URL>' -e 'INFRAVEIL_CLIENT_ID=<INFRAVEIL_CLIENT_ID>' -e 'INFRAVEIL_AGENT_ID=<INFRAVEIL_AGENT_ID>' -e 'INFRAVEIL_AGENT_TOKEN=<INFRAVEIL_AGENT_TOKEN>' -- uvx infraveil-mcp{
"mcpServers": {
"control-plane": {
"command": "uvx",
"args": [
"infraveil-mcp"
],
"env": {
"INFRAVEIL_AGENT_ID": "<INFRAVEIL_AGENT_ID>",
"INFRAVEIL_AGENT_TOKEN": "<INFRAVEIL_AGENT_TOKEN>",
"INFRAVEIL_BASE_URL": "<INFRAVEIL_BASE_URL>",
"INFRAVEIL_CLIENT_ID": "<INFRAVEIL_CLIENT_ID>"
}
}
}
}[mcp_servers.control-plane]
command = "uvx"
args = ["infraveil-mcp"]
env = { INFRAVEIL_BASE_URL = "<INFRAVEIL_BASE_URL>", INFRAVEIL_CLIENT_ID = "<INFRAVEIL_CLIENT_ID>", INFRAVEIL_AGENT_ID = "<INFRAVEIL_AGENT_ID>", INFRAVEIL_AGENT_TOKEN = "<INFRAVEIL_AGENT_TOKEN>" }{
"mcpServers": {
"control-plane": {
"command": "uvx",
"args": [
"infraveil-mcp"
],
"env": {
"INFRAVEIL_AGENT_ID": "<INFRAVEIL_AGENT_ID>",
"INFRAVEIL_AGENT_TOKEN": "<INFRAVEIL_AGENT_TOKEN>",
"INFRAVEIL_BASE_URL": "<INFRAVEIL_BASE_URL>",
"INFRAVEIL_CLIENT_ID": "<INFRAVEIL_CLIENT_ID>"
}
}
}
}{
"servers": {
"control-plane": {
"type": "stdio",
"command": "uvx",
"args": [
"infraveil-mcp"
],
"env": {
"INFRAVEIL_AGENT_ID": "<INFRAVEIL_AGENT_ID>",
"INFRAVEIL_AGENT_TOKEN": "<INFRAVEIL_AGENT_TOKEN>",
"INFRAVEIL_BASE_URL": "<INFRAVEIL_BASE_URL>",
"INFRAVEIL_CLIENT_ID": "<INFRAVEIL_CLIENT_ID>"
}
}
}
}Put your own values in place of
<INFRAVEIL_BASE_URL> (Control-plane base URL, e.g. https://api.infraveil.com), <INFRAVEIL_CLIENT_ID> (Your Infraveil client id (same one the agent uses)), <INFRAVEIL_AGENT_ID> (The agent id this MCP server speaks for), <INFRAVEIL_AGENT_TOKEN> (The agent's existing token; used to sign requests. Never minted here).
The author’s registry entry marks them as required.
Optional settings from the registry entry, left out of the block above:
INFRAVEIL_AGENT_FILE (Alternative to the four vars above: path to your rendered agent source; ids and token are read from it), INFRAVEIL_VERIFY_RESPONSES (Verify the control plane's response signatures (default on). Set 0 only for debugging).
Alternatives to Infraveil Control Plane
same job, measured the same wayGoverned email for AI agents: a sandbox inbox to read and send from, human approval to go external.
Give your agent its own email address with graduated human oversight, from approval to autonomy.
Create, review and schedule social content from your AI agent. Approval-first.
Gate an AI agent's destructive actions behind human approval, with a tamper-evident log.
Intent-bound action authorization for AI agents: policy, human approval, and a signed audit trail.
Secure and manage MCP servers through the Speakeasy AI Control Plane from your agent.
Autonomous and governed SRE & MLOps control plane for AI agent platforms.
Troubleshoot enrolled client PCs from your AI client, with human approval and an audit trail.
Infraveil Control Plane — questions
Answers built from our own checks of this server.