thask
io.github.kimgh06/thask
Dependency-graph MCP server. Tells Claude/Cursor what breaks if you change X. Provenance guards.
Install surfaces
How thask runs, per the official MCP registry entry.
- npm
@thask-org/[email protected]
Governed execution
How KLA gates calls to thask once it is connected.
A published policy defines which thask 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.