Skip to main content
Glama
WYRE-AI

Inforcer MCP Server

Official
by WYRE-AI
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Related Servers

Alternatives to Inforcer MCP Server

No user-submitted related servers found.

    Related Servers

    • LegacyMCP

      Marco-Lelli
      A
      license
      Not graded
      quality
      B
      maintenance
      MCP server that enables AI-powered assessment of Active Directory on-premises environments by exposing AD data as queryable tools for LLMs like Claude.
      MIT

    • EndpointRead-MCP

      nelladath
      A
      license
      B
      quality
      B
      maintenance
      A read-only MCP server for Microsoft Intune and Entra ID that enables list, get, search, and reporting operations for tenant visibility, audits, troubleshooting, and health reporting without write actions. It includes authentication helpers, report exports, and metadata discovery tools.
      36
      1
      MIT

    • entraid-mcp

      sedattavukcu
      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.
      -

    • a2a-trustgate

      jyswee
      A
      license
      Not graded
      quality
      D
      maintenance
      MCP server for AI agent compliance that screens actions before execution and records decisions in an immutable, SIEM-ready audit trail.
      49 npm
      -

    • SQL Server MCP

      az-coder-123
      A
      license
      B
      quality
      D
      maintenance
      An MCP server that connects AI assistants to Microsoft SQL Server databases, enabling schema exploration and read-only queries safely.
      49
      5 npm
      4
      MIT
    Deploy Server
    One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

    TDQS

    A3.9/5.0

    Scored across 24 tools

    Disambiguation5/5

    Each tool targets a distinct resource/action: tenants, users, groups, roles, policies, baselines, alignment, audit, assessments, and reports. Even close pairs like alignment_scores vs alignment_details or assessments_run vs reports_run are clearly separated by noun and purpose. The discovery and status tools also serve clearly different roles.

    Naming Consistency4/5

    All tools share the inforcer_ prefix and mostly follow a resource_verb pattern like tenants_list, users_get, and groups_list. A few names omit the verb (inforcer_status, inforcer_alignment_scores, inforcer_audit_event_types) and report actions use compound names like reports_run_status and reports_download_output, but the overall convention remains readable and predictable.

    Tool Count3/5

    With 24 tools, this server sits at the high end of the reasonable range and feels heavy relative to a tightly scoped MCP server. The count is justified by the breadth of the domain — tenants, identity, alignment, audit, assessments, and reports — but it is more than an agent will typically need in one session.

    Completeness4/5

    The toolset covers the core workflows well: tenant resolution, identity object listing/detail, baseline alignment, secure scores, audit search, assessment discovery/run, and the full report queue/status/download lifecycle. Minor gaps remain, such as no policy detail view, no role detail view, and no assessment run status polling, but these are not blocking for the main Inforcer use cases.

    Maintenance

    ActivityActive
    ResponsivenessUnresponsive

    Resources