Periphery Code Audit
io.github.zyntx-lab/periphery-mcp-server
Swift code analysis with Periphery - detect unused code and improve code quality
Install surfaces
How Periphery Code Audit runs, per the official MCP registry entry.
- mcpb
binary https://github.com/zyntx-lab/periphery-mcp-server/releases/download/v1.0.0/[email protected]
Governed execution
How KLA gates calls to Periphery Code Audit once it is connected.
A published policy defines which Periphery Code Audit actions an agent may take and under what conditions. Each call passes through a policy gate at the tool-call boundary. Permitted actions execute, with the policy basis recorded. Flagged actions execute and are sampled for scheduled human review. High-stakes actions pause and route to a named reviewer on the Decision Desk. The call, the policy decision, and any approval are sealed as an evidence record.
KLA also governs the agent frameworks and model providers you already run. See integrations.