Skip to main content
Glama
WYRE-AI

Teramind MCP Server

by WYRE-AI

Related Servers

Alternatives to Teramind MCP Server

No user-submitted related servers found.

    Related Servers

    • A
      license
      Not graded
      quality
      B
      maintenance
      Enables AI agents to read protected computers and their check-ins, computer groups, approval requests, the unified audit log, and child organizations through a zero-trust endpoint security portal API. Every operation is read-only, with credentials supplied per request as headers and never stored.
      Apache 2.0
    • A
      license
      B
      quality
      D
      maintenance
      Enables read-only access to FileMaker databases through the Data API, allowing users to retrieve records, analyze metadata, search across layouts, and infer relationships while maintaining data security.
      16
      MIT
    • A
      license
      Not graded
      quality
      C
      maintenance
      Enables read-only access to Crisp customer support, live chat, CRM, and helpdesk data, including conversations, contacts, knowledge base, campaigns, operators, visitors, and site settings, via the official REST API v1.
      MIT
    • A
      license
      Not graded
      quality
      B
      maintenance
      Enables read-only access to Wise Business API profiles, balances, account statements, and card-spending data through MCP tools.
      MIT
    • A
      license
      Not graded
      quality
      B
      maintenance
      Enables authenticated, read-only access to stored account, options, and monitoring data for bounded research. It also permits pausing/resuming monitoring, with no brokerage write or proxy capabilities.
      MIT

    TDQS

    A4.2/5.0

    Scored across 16 tools

    Disambiguation5/5

    Each tool targets a distinct resource or operation: computers, agents, departments, alerts, rules, policies, groups, profiles, and account settings are clearly separated. The list/get pairs are unambiguous, and descriptions clarify potentially overlapping concepts like anomaly rules versus behavior policies.

    Naming Consistency5/5

    All tools follow a consistent teramind_list_<plural> / teramind_get_<singular> pattern with snake_case throughout. Minor exceptions like teramind_get_account and teramind_list_alerts still fit the broader list/get convention and do not create confusion.

    Tool Count4/5

    With 16 tools, the server is slightly above the typical 3-15 range, but each tool maps to a meaningful entity or lookup operation in the Teramind domain. The count is reasonable for the breadth of resources covered and does not feel bloated.

    Completeness4/5

    The read-only metadata surface covers the major Teramind entities: computers, agents, departments, alerts, anomaly rules, behavior policies, policy groups, and monitoring profiles. Minor gaps exist, such as no single-alert getter or monitoring-profile detail endpoint, but agents can accomplish core monitoring and configuration-discovery workflows without dead ends.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues