Skip to main content
Glama
WYRE-AI

CyberQP MCP Server

by WYRE-AI

Related Servers

Alternatives to CyberQP MCP Server

No user-submitted related servers found.

    Related Servers

    • F
      license
      A
      quality
      B
      maintenance
      Provides read-only visibility into Gorelo PSA data, enabling AI assistants to query tickets, clients, contacts, contracts, assets, and time entries through MCP tools.
      24
      -
    • A
      license
      Not graded
      quality
      F
      maintenance
      Provides AI assistants with read-only access to Secureframe's compliance data, enabling querying of security controls, tests, users, vendors, and more across frameworks like SOC 2 and ISO 27001.
      8
      MIT
    • A
      license
      Not graded
      quality
      C
      maintenance
      Provides read-only access to Tactical RMM, enabling agent searches, detailed agent information, audit log queries, and execution of information-gathering PowerShell scripts on agents, with Entra ID authentication and a strict read-only guard.
      MIT
    • A
      license
      Not graded
      quality
      B
      maintenance
      Enables AI assistants to query an organization's device posture, compliance, policies, and software/CVE status through a remote, read-only, OAuth-secured MCP endpoint.
      MIT
    • F
      license
      Not graded
      quality
      B
      maintenance
      Enables AI assistants to query internal business data for insights into customers, revenue, subscriptions, sales, and churn through controlled, read-only MCP tools.
      -
    • F
      license
      A
      quality
      B
      maintenance
      Enables AI assistants and the WYRE Conduit gateway to access Telivy's security assessment data for MSPs, including external scans, deep-scan risk assessments, device inventory, M365/Google Workspace user exposure, PII summaries, and finding-level details.
      16
      -

    TDQS

    A3.9/5.0

    Scored across 10 tools

    Disambiguation4/5

    Most tools cleanly map to distinct resources and actions: customers, accounts, event logs, JIT policies, and tenant profile. The only possible confusion is among the JIT status/existence tools, especially get_customer_jit_status and check_jit_account_exists, but their descriptions sufficiently differentiate scope.

    Naming Consistency5/5

    All tools share the cyberqp_ prefix, use snake_case, and follow a clear verb_noun pattern such as list_customers, get_events, and check_jit_account_exists. The naming is consistent and predictable.

    Tool Count5/5

    Ten tools is well within the ideal range for a focused read-only utility server. Each tool covers a meaningful slice of the domain, and none feels redundant or unnecessary.

    Completeness4/5

    For a read-only visibility/verification server, the surface is fairly complete: customer listing, account metadata and counts, event logs, tenant profile, and JIT policy/status checks. Minor gaps exist, such as lack of a single-customer detail endpoint or pagination tooling, but agents can complete typical monitoring and verification workflows.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues