Decide in under 4 minutes whether an MCP server belongs in sandbox, formal review, or the reject pile.
This is a governance gate for MCP servers. It is not a code scanner, malware verdict, penetration test, or gateway replacement.
This is a governance gate for MCP servers. It is not a code scanner, malware verdict, penetration test, or gateway replacement.
Use this to classify a proposed MCP server as approvable with standard controls, sandbox-only, hold for governance review, or reject.
The purpose of this screen is to classify MCP approval posture quickly, highlight the biggest gaps, and route the organization to the correct next step without giving away the paid implementation layer.
It evaluates whether a proposed MCP server is governable from an approval and lifecycle standpoint, including provenance, authorization, testing, credentials, logging, rollback, and approval workflow discipline.
Sandbox only does not automatically mean the server is malicious. It means the evidence and control posture are too weak for normal enterprise rollout.
The missing value is a repeatable MCP approval workflow, retained evidence, lifecycle controls, and policy linkage. That sits in ACT Tier 2, not in a free triage page.
Use the paid bridge when the screening result shows structural control gaps that need policy, procedure, evidence, lifecycle discipline, and implementation ownership rather than another free quiz.
See the paid implementation system for MCP policy, evidence, lifecycle, and vendor governance.
Use the broader agentic deployment screen alongside this MCP approval gate.
Review the paid tier that includes the MCP Security Governance Checklist and linked implementation assets.