Every MCP server reviewed like code — tools, permissions, description drift — before it holds production scope.
An MCP server asks for production access: its manifest declares tools, permissions, and descriptions.
Rules TK-MCP-001..009 check declared scope against what the tools actually need — and flag description drift.
Each server gets a risk score and a safer-manifest diff: the least-privilege version, ready to apply.
No server — and no scope widening — holds production scope without a security approval on record.
An over-scoped sample manifest goes in; a risk score and a safer manifest come out.
7 findings — scope the server never uses
Write and delete scope on tools that only read, unrestricted network egress, and a token passed in plain text. Each finding cites the rule and the line.
Re-scan verifies clean — the least-privilege manifest passes the same rules with zero findings
Per MCP server