Skip to main content
Glama
Petra Security MCP Server

Petra Security MCP Server

by WYRE-AI

Related Servers

Alternatives to Petra Security MCP Server

No user-submitted related servers found.

    Related Servers

    • A
      license
      Not graded
      quality
      B
      maintenance
      Enables AI assistants to query and manage OpenCTI threat intelligence data, including indicators, observables, reports, malware, and more, with read-only and optional write operations.
      1
      MIT
    • A
      license
      A
      quality
      B
      maintenance
      Enables AI assistants to query RoboShadow's Rubicon Platform Data API for read-only endpoint security, asset inventory, applications, users, vulnerabilities, and remediation status data.
      40
      1
      Apache 2.0
    • A
      license
      Not graded
      quality
      B
      maintenance
      Enables AI agents to ask Purple AI hunting questions, run PowerQueries over the Singularity Data Lake, and read alerts, vulnerabilities, misconfigurations and asset inventory from a SentinelOne console, plus VirusTotal and public CVE lookups. It is read-only and accepts per-request console credentials, making it stateless and multi-tenant.
      Apache 2.0
    • A
      license
      Not graded
      quality
      C
      maintenance
      Enables AI agents to read and act on managed security data from the Huntress API, covering accounts, organizations, protected endpoints, incident reports and their remediations, escalations, signals, users, invoices and summary reports. Read operations are safe by default, while data-changing actions such as resolving incidents, approving remediations, and managing organizations or users require explicit write and confirm flags.
      Apache 2.0
    • A
      license
      A
      quality
      B
      maintenance
      Enables AI assistants to triage an Atera help desk by ranking open tickets with plain reasons, summarizing site health and alerts, and producing a one-call morning brief. It redacts personal data, fences user-written text as untrusted, and stays read-only unless writes are explicitly enabled.
      6
      MIT

    TDQS

    A4.2/5.0

    Scored across 7 tools

    Disambiguation5/5

    Each tool targets a clearly distinct resource or action: tenants, org-level usage, per-tenant billable users, incidents, incident detail, failed attacks, and posture reports. The billing-related tools overlap conceptually but are clearly separated by aggregate vs. user-level scope, and list vs. get incident tools have an explicit summary/detail boundary.

    Naming Consistency5/5

    All tools use a consistent snake_case verb_noun pattern with the same petra_ prefix. The verbs are predictable list/get pairs, and no mixed naming conventions appear.

    Tool Count5/5

    Seven tools is well-scoped for a read-only security and billing reporting server. Each tool covers a meaningful surface area without excessive fragmentation.

    Completeness4/5

    The surface covers the core reporting lifecycle: tenant discovery, usage, user-level billing, incidents, blocked attacks, and posture reports. Minor gaps exist around per-tenant aggregate usage, explicit report retrieval beyond defaults, and remediation/write operations, but agents can largely work around these.

    Maintenance

    ActivityMaintained
    ResponsivenessNo recent community issues