Microsoft Entra MCP Server

The materials say no keys/environment variables are required, but access to Microsoft Entra via Microsoft Graph typically implies some Microsoft authentication context or token in practice. The docs do not explain credential acquisition, storage, or permission scope, creating caution around opaque credential handling or over-privileged auth.

The description explicitly states it uses the Microsoft Graph API, so directory queries will be sent to Microsoft services. No unrelated third-party endpoints or obvious exfiltration red flags are stated, but user queries and directory metadata are expected to leave the local environment to Graph.

The system flags executes-code, indicating the MCP server runs code locally. The provided materials do not show requests for unusual system privileges or dangerous actions unrelated to its stated purpose, so this is a normal caution-level capability rather than a specific high-risk red flag.

Its stated functions include searching users, groups, and memberships, which implies access to organizational identity directory data. The materials do not show local file read/write needs or access beyond directory-query use cases; however, directory data is often sensitive, so the actual Graph permission scope should be reviewed carefully.

A public GitHub repository is available for audit, which is a positive risk-reducing factor. However, it comes from a third-party registry, has no declared license, shows 0 stars, and has unknown maintenance status, indicating weak maturity and maintenance signals and justifying source/dependency review before use.