Skip to main content
Glama
hdyrawan

mcp-endpoint-central

by hdyrawan
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Related Servers

Alternatives to mcp-endpoint-central

No user-submitted related servers found.

    Related Servers

    • connectsecure-mcp

      MSPbotsAI
      F
      license
      Not graded
      quality
      B
      maintenance
      MCP server for ConnectSecure vulnerability management, exposing 285 read-only tools to query assets, vulnerabilities, Active Directory, and more via natural language.
      -

    • superops-mcp

      WYRE-AI
      A
      license
      A
      quality
      A
      maintenance
      An MCP server for SuperOps PSA/RMM, enabling MSPs to manage tickets, assets, clients, and field technician operations through SuperOps's API.
      21
      3
      Apache 2.0

    • checkpoint-mcp

      MSPbotsAI
      F
      license
      Not graded
      quality
      C
      maintenance
      MCP server for Check Point Harmony Endpoint that exposes policy, asset, vulnerability, quarantine, and remediation API methods as MCP tools, with per-request credential isolation and automatic two-step authentication.
      -

    • IntuneRW-Core

      nelladath
      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
    Deploy Server
    RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

    TDQS

    B3.4/5.0

    Scored across 86 tools

    Disambiguation4/5

    Most tools are clearly differentiated by module prefix and specific resource/action (e.g., patch_summary vs patch_scan_details vs patch_all_systems_list). A few near-duplicates like dcm_device_audit_list vs dcm_block_device_audit_list and multiple DLP report variants could cause hesitation, but descriptions clarify the distinct scopes.

    Naming Consistency3/5

    The naming is uniformly snake_case and mostly follows a noun_prefix + action_pattern, but the action words vary inconsistently (list, report, summary, details, get, exists). For example, custom_field_values_get is verb-final while most others are noun-final, and dex_meta/server_properties have no verb at all. Naming is readable but not fully predictable.

    Tool Count1/5

    With 86 tools, this is far beyond the threshold where an agent can efficiently select among them. Even for a broad enterprise management server, the sheer volume is overwhelming and the server would be better split into several focused MCP servers or consolidated.

    Completeness2/5

    The tool surface is almost entirely read-only: every tool retrieves or lists data, with no create, update, delete, or action tools (e.g., no patch deployment, policy change, or device exemption actions). This severely limits the server's usefulness for actual endpoint management, even though the read-side coverage is broad.

    Maintenance

    ActivitySlowing
    ResponsivenessNo issues

    Resources