Infraveil Mcp — independently scanned and version-tracked by SaferSkills.
SaferSkills independently audited Infraveil Mcp (Agent Skill) and scored it 100/100 (green). The audit ran 55 deterministic rules across Security, Supply Chain, Maintenance, Transparency, and Community; it found 0 high-severity and 0 lower-severity findings. The full rule-by-rule trace and per-finding evidence are below. Free, methodology-open.
Findings & checks · 0 flagged
Every scanned point with the score it earned and what moved between them.
First recorded scan — no prior version to compare against.
The primary manifest — the file an agent reads to learn what this artifact does.
<!-- mcp-name: io.github.infraveilhq/control-plane -->
A hardened, self-hosted Model Context Protocol server that lets your own AI agent query and govern your Infraveil control plane in-loop — read the governed state of your backend, and file deploy and remediation requests that always pass through human approval.
It is built on the same principle as the rest of Infraveil: trust by inspection, not assertion. This server adds no new authority and no new auth surface. It signs every request with the token your agent already holds, and it verifies the control plane's signed responses in return — so neither side can be forged on the wire. You can read every line here and diff the signing code against the published agent source; they are the same scheme.
The MCP ecosystem's security is, bluntly, bad — most public MCP servers require no auth at all. An MCP server that hands an AI agent operational reach into your backend is exactly the thing that should not be unauthenticated. This one:
keyed by your per-agent token; nonce + timestamp replay protection).
request_deploy and remediate enqueuea request into the control plane's human-approval queue and return the approval URL. There is no code path here that mutates your infrastructure.
enforced by the control plane. This process holds no more authority than the agent already running on the host.
pip install infraveil-mcpThe server reuses your existing Infraveil agent identity — it never mints credentials. Either set the environment variables:
export INFRAVEIL_BASE_URL=https://api.infraveil.com
export INFRAVEIL_CLIENT_ID=...
export INFRAVEIL_AGENT_ID=...
export INFRAVEIL_AGENT_TOKEN=... # your agent's existing token…or point it at your rendered agent source and let it read the ids and token straight out of the file you can already inspect:
export INFRAVEIL_AGENT_FILE=/opt/infraveil/agent.py{
"mcpServers": {
"infraveil": {
"command": "infraveil-mcp",
"env": {
"INFRAVEIL_BASE_URL": "https://api.infraveil.com",
"INFRAVEIL_CLIENT_ID": "...",
"INFRAVEIL_AGENT_ID": "...",
"INFRAVEIL_AGENT_TOKEN": "..."
}
}
}
}Read (no side effects):
| Tool | What it returns |
|---|---|
get_agent_status | Fleet/agent state: online/offline, heartbeats, CPU/mem/disk, deploy state |
get_security_findings | Active security policy + recent security events |
get_request_trace | Recent request/operation traces and outcomes |
query_runtime_truth_graph | Authoritative host ↔ agent ↔ service ↔ policy snapshot |
Governed (enqueue for human approval — never auto-applied):
| Tool | What it does |
|---|---|
evaluate_deploy_gate | Reports whether a proposed change would pass policy. Read-only. |
request_deploy | Files a deploy request into the approval queue; returns request id + approval URL |
remediate | Files a remediation proposal (respects your blocked categories); returns id + approval URL |
infraveil_mcp/client.py. The request-signingand response-verification code is plain stdlib hmac/hashlib.
_signed_headers,verify_response_signature). They implement the same protocol.
pytest tests/. It transcribes the server's verifierand asserts this client's signatures are accepted and tampering is rejected.
AGPL-3.0-or-later. The control plane (central authority graph, multi-tenant policy, audit/evidence store) is the commercial product; the code that runs on your machine is open because you should never have to trust code you can't read.
~30 seconds. Free. No account. Every finding cites a rule and a line of evidence.