MCP’s 493-Day Sprint: From Internal Tool to Regulated Infrastructure

▶ Watch (2:13)

It has been 493 days since Anthropic launched MCP. In that time 96 million servers have been downloaded. Protocol adoption has outpaced organizational implementation. A solo engineer spinning up a server is different from a 500-person company rolling MCP across teams without keeping the IT director up at night. Scaling brings security exposure, poor logs, and privacy concerns. Brooks argued that 2026 is the year compliance and governance take center stage.

EU AI Act: Why U.S. Teams in Regulated Industries Must Care

▶ Watch (5:18)

MCP is not named in the EU AI Act. The systems it enables are. If your LLM queries a database or triggers an action in financial services, healthcare, HR, or critical infrastructure, you must comply. The high-risk tier requires strict regulation. Prohibited uses (manipulation, social scoring) already face enforcement. Fines are high. Brooks noted that Colorado and California have state legislation percolating as pushback to the U.S. laissez-faire approach.

Three Compliance Requirements That Double as MCP Best Practices

▶ Watch (13:00)

Brooks focused on three of the eight high-risk AI requirements. First, data governance: PII should never hit the model. Microsoft Presidio integrated into an MCP gateway can redact credit cards, driver’s license plates, and addresses. Second, audit logs need structured metadata (IP, timestamp, log level) for regulators. Third, every server is a potential attack surface. A rug-pull attack changes tool descriptions after approval; a gateway can block and alert.

MCP Gateways: The Missing Layer for Enterprise Deployments

▶ Watch (19:35)

Protocols connect, but platforms enable enterprise viability. Brooks compared MCP to SAML vs. Okta. An ungoverned MCP mesh at scale is a messy web. Gateways provide a central control layer: private registries, one-click installation, runtime guardrails, tool-level provisioning, and integrations with existing systems. Brooks noted that her company sandboxes local servers that don’t need file access.

Notable Quotes

“the S of MCP stands for security cuz there is none” Becky Brooks · ▶ Watch (3:01)

“PII should absolutely never hit your model, period.” Becky Brooks · ▶ Watch (13:37)

“ungoverned MCP at scale is a messy web of connections.” Becky Brooks · ▶ Watch (20:28)

Key Takeaways

  • 2026 is the year compliance drives MCP from protocol adoption to organizational rollout.
  • Three EU AI Act high-risk requirements are MCP best practices: PII redaction, structured audit logs, and server security.
  • MCP gateways provide the central control layer that the protocol alone cannot deliver.

About the Speaker(s)

Becky Brooks is a Staff Product Marketing Manager at MCP Manager by Usercentrics, where she helps teams safely and confidently deploy MCP in real-world AI systems. She focuses on making MCP accessible and trustworthy so teams can use AI to move faster without sacrificing safety or compliance.