EndpointRead-MCP
Related Servers
Alternatives to EndpointRead-MCP
No user-submitted related servers found.
Related Servers
- FlicenseNot gradedqualityCmaintenanceRead-only MCP server for Microsoft Entra ID (Azure AD) that enables querying user sign-in logs, group memberships, and assigned Microsoft 365 licenses via Microsoft Graph API. Provides security and audit visibility without any write operations.-
- FlicenseNot gradedqualityCmaintenanceProvides read-only access to Microsoft Intune through the Microsoft Graph API, enabling MCP clients to query managed devices, apps, compliance policies, and configuration profiles.-
- AlicenseNot gradedqualityCmaintenanceA read-only MCP server that provides tools to list and read devices, MDM servers, blueprints, configurations, apps, packages, users, and other resources from Apple Business Manager and Apple School Manager.MIT
- AlicenseAqualityAmaintenanceA local, read-only MCP server that inspects and explains Microsoft Intune assignments through Microsoft Graph /beta, with delegated sign-in and secure token caching.66 npm3MIT
- AlicenseNot gradedqualityBmaintenanceMCP server for managing Microsoft Intune and Entra ID via the Microsoft Graph API, offering 34 tools for device, app, compliance, security, identity, and reporting operations.1MIT
- FlicenseNot gradedqualityCmaintenanceRead-only MCP server providing Microsoft 365 service health status and known incident/outage information from Microsoft Graph. Enables quick answers to whether an issue is a widespread Microsoft outage or specific to a tenant.-
TDQS
Scored across 36 tools
The manage_* tools are mostly distinct domains (devices, apps, policies, users), but the authentication cluster has overlapping tools: complete_interactive_sign_in vs complete_interactive_login are functionally identical, and connect_intune_mcp_server overlaps with start_interactive_sign_in and test_connection. Device-related tools like manage_intune_devices and manage_entra_devices could also be confused despite distinct descriptions.
25 of 36 tools follow a 'manage_<domain>' pattern, which is clear and consistent. However, the remaining tools use a variety of verb prefixes (get_, authenticate_, start_, complete_, connect_, list_, describe_, discover_) that break the pattern. The redundant complete_interactive_login adds unnecessary naming inconsistency.
With 36 tools, this is a large surface, but the server covers a very broad scope (Intune MDM, Entra ID, security policies, reports). Each manage_* tool consolidates many related actions, which helps manageability. Still, the raw count is heavy and could overwhelm agents, so it's borderline.
The server provides comprehensive lifecycle coverage across Intune devices, apps, policies, users, groups, and security. Minor gaps exist: manage_admx_policies lacks update/assign, manage_security_baselines is view-only, and manage_app_registrations lacks create/update. These are workable gaps, so the tool surface is mostly complete.