Skip to main content
Colorado ADMT: 1 Jan 2027 · EU high-risk: 2 Dec 2027 (Annex III); 2 Aug 2028 (Annex I)
MCP governance approval gate

MCP Server Approval Gate

Decide in under 4 minutes whether an MCP server belongs in sandbox, formal review, or the reject pile.

3-4 minutes 12 scored questions No login

This is a governance gate for MCP servers. It is not a code scanner, malware verdict, penetration test, or gateway replacement.

  • Screens source trust, authorization model, tool blast radius, data exposure, logging, credentials, rollback, and approval workflow maturity.
  • Separates governable MCP servers from opaque servers that should stay out of production.
  • ACT includes supplier and subprocessor review records and proposed contract wording for local legal and procurement review. Your team verifies the evidence and resolves open issues.
Enterprise approval gate for MCP servers showing trust boundary review, authorization checks, logging, credential control, and rollback readiness.
MCP server approval triage across provenance, authorization, evidence, credentials, and lifecycle control.
MCP review gate

This is a governance gate for MCP servers. It is not a code scanner, malware verdict, penetration test, or gateway replacement.

Interactive screen

Assessment

Use this to classify a proposed MCP server as approvable with standard controls, sandbox-only, hold for governance review, or reject.

Question 1 of 12 0% complete
Question 1 of 12

What this result should change

This section classify MCP approval posture quickly, highlight the biggest gaps, and surface governance gaps and recommend an appropriate implementation path.

What this tool evaluates about an MCP server

This assessment 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.

What a sandbox-only result does not mean

Sandbox only does not automatically mean the server is malicious. It means the evidence and control posture are too weak for normal enterprise rollout.

How ACT supports an evidence review

The missing value is a repeatable MCP approval workflow, retained evidence, lifecycle controls, and policy linkage. ACT includes editable records for agent authority, tool boundaries, MCP and skill reviews, human review and incident containment. Technical owners must test the actual implementation.

Where to go next

ACT is one editable AI Controls Toolkit with eleven core files across eight workflow areas. It supports evidence collection and human decisions; it does not enforce controls or certify compliance.

This page is informational only. It does not provide legal advice, compliance certification, or an audit conclusion.

Frequently Asked Questions (FAQs)

What does this tool evaluate about an MCP server?

It evaluates maintainer trust, authorization model, tool scope, data exposure, sandbox testing, logging, credential handling, ownership, and approval workflow maturity for a proposed MCP server.

Does a sandbox-only result mean the server is malicious?

No. It means the evidence or control posture is not strong enough for standard enterprise rollout. The next step is controlled testing and stronger approval evidence, not automatic trust.

Why are authorization and rollback weighted so heavily?

Because a server with weak authorization or no reliable rollback path can expand blast radius quickly, especially when it exposes write actions, sensitive data, or shared credentials.

Why is a formal approval workflow necessary for MCP?

Because experimental MCP adoption is not the same thing as enterprise approval. A formal workflow creates retained evidence, owner accountability, and repeatable decisions across server requests.

Does this tool store anything I enter?

No. The assessment runs entirely in the browser. Answers are not stored, synced, or submitted to a server.

Use these artifacts for MCP governance evidence

MCP approval should not sit in a standalone checklist. Connect approval decisions to an operating model and incident-response artifact for rollback, override, and evidence retention.

Source review dates are stated in the relevant guides. It provides operational implementation guidance and product information only; it is not legal advice, tax advice, audit assurance, certification assurance, conformity-assessment advice, buyer-approval assurance, or security assurance. Validate legal, regulatory, contractual, tax, audit, and security decisions with qualified professionals.