Skip to main content
Glama
nelladath

EndpointRead-MCP

by nelladath

Related Servers

Alternatives to EndpointRead-MCP

No user-submitted related servers found.

    Related Servers

    • F
      license
      Not graded
      quality
      C
      maintenance
      Read-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.
      -
    • F
      license
      Not graded
      quality
      C
      maintenance
      Provides read-only access to Microsoft Intune through the Microsoft Graph API, enabling MCP clients to query managed devices, apps, compliance policies, and configuration profiles.
      -
    • A
      license
      Not graded
      quality
      C
      maintenance
      A 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
    • A
      license
      A
      quality
      A
      maintenance
      A local, read-only MCP server that inspects and explains Microsoft Intune assignments through Microsoft Graph /beta, with delegated sign-in and secure token caching.
      6
      6 npm
      3
      MIT
    • A
      license
      Not graded
      quality
      B
      maintenance
      MCP 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.
      1
      MIT
    • F
      license
      Not graded
      quality
      C
      maintenance
      Read-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

    B3.4/5.0

    Scored across 36 tools

    Disambiguation3/5

    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.

    Naming Consistency3/5

    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.

    Tool Count3/5

    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.

    Completeness4/5

    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.

    Maintenance

    ActivitySlowing
    ResponsivenessNo issues