Find out in under 4 minutes whether unapproved MCP servers are already operating inside your enterprise perimeter.
This is a governance visibility screen for unmanaged, local, containerized, or otherwise unapproved MCP deployments. It is not a network scanner, gateway, or telemetry product.
This screen classifies shadow MCP exposure quickly. It does not scan your network, enumerate servers, or export an inventory.
Use this to classify whether MCP usage is tightly controlled, drifting into shadow deployment, materially exposed, or already in an uncontrolled state.
This section classify shadow MCP exposure quickly, surface the most significant gaps, and recommend an appropriate implementation path.
Shadow MCP means unmanaged, local, containerized, unapproved, or weakly governed MCP usage that sits outside a defendable registry, ownership model, logging baseline, or disable path.
A green result does not prove shadow usage is impossible. It means the current footprint appears more governable than the other states and still needs discipline to stay that way.
Green and amber results usually need baseline visibility, inventory, and gap analysis first, which sit in AI Controls Starter. Severe red states need formal governance, evidence, and response controls, which sit in AI Controls Professional.
When the assessment reveals structural visibility gaps, control drift, or containment weakness, AI Controls Professional provides the full implementation evidence pack.
Structure the visibility baseline, inventory, gap analysis, and dashboard layer for shadow MCP cleanup.
Move to the formal governance, evidence, incident, and implementation layer when shadow MCP is materially exposed or uncontrolled.
Use the approval-focused screen when the issue is vetting a proposed server rather than discovering unmanaged MCP usage.
It classifies unmanaged, local, containerized, unapproved, or weakly governed MCP usage that sits outside a defendable enterprise registry, ownership model, logging baseline, or disable path.
No. It means the current MCP footprint appears more governable than the other states. Drift can still emerge if visibility, registry discipline, or approval controls weaken.
Because they can spread faster than central governance, especially when teams run MCP locally, in containers, or through personal setups that bypass registry and ownership controls.
Earlier-maturity results usually need baseline visibility, inventory, and gap analysis first, which sit in AI Controls Starter. Severe red states need formal governance, evidence, and response controls, which sit in AI Controls Professional.
No. The assessment runs entirely in the browser. Answers are not stored, synced, or submitted to a server.
Source and review note: This page was last reviewed on 6 May 2026 against the current Move78 public site baseline and relevant official or authoritative sources where laws, standards, frameworks, cybersecurity controls, product scope, pricing, support policy, or implementation guidance are discussed. 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.