Vetting an MCP Server and Understanding What Managed MCP Changes

Your team wants to connect a third-party MCP server that gives Claude Code access to your company's internal ticketing system, so Claude can read and update tickets during a session.

1. Walk through a vetting checklist for this server before anyone connects it, covering at least three distinct dimensions of risk.
2. Explain specifically why "it's listed in the Anthropic Directory" is not sufficient vetting on its own.
3. Your organization decides to deploy managed-mcp.json restricting every engineer to a fixed, approved server set. Explain what concretely changes for engineers, including one thing that stays true even under this restriction (i.e., what managed MCP does not protect against).