Skip to main content
Glama
just5ky

axur-mcp

by just5ky
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Related Servers

Alternatives to axur-mcp

No user-submitted related servers found.

    Related Servers

    • rocketcyber-mcp

      WYRE-AI
      A
      license
      Not graded
      quality
      A
      maintenance
      An MCP server for the RocketCyber Managed SOC platform that provides read-only access to security data including incidents, agents, and events. It enables users to monitor and query security information through 10 specialized tools and resources.
      Apache 2.0

    • mcp-ticketing-server

      ShaiviBansal
      F
      license
      Not graded
      quality
      C
      maintenance
      MCP server for ticketing automation that exposes tools to create, search, and update IT helpdesk tickets, with metrics tracking.
      -

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

    • Archery MCP

      lyj5812
      A
      license
      A
      quality
      B
      maintenance
      A read-only MCP server for Archery that enables secure instance query, ticket management, and restricted SQL execution through AI clients.
      10
      1
      MIT

    • incident-copilot

      Varshini1612
      A
      license
      Not graded
      quality
      C
      maintenance
      MCP server for investigating cloud incidents and managing approvals. Provides read-only tools to list incidents, investigate incidents, and list approvals, keeping remediation behind human approval.
      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

    B3.3/5.0

    Scored across 3 tools

    Disambiguation4/5

    The tools are mostly distinct: 'tickets' handles search, list, and summary retrieval; 'ticket_details' provides deep single-ticket information; 'ticket_stats' covers statistics. However, there is potential overlap between 'tickets' get action and 'ticket_details', as both retrieve ticket info, but descriptions suggest different detail levels.

    Naming Consistency5/5

    All tool names follow a consistent 'ticket_' prefix with descriptive suffixes: 'tickets', 'ticket_details', 'ticket_stats'. The naming is predictable and uses snake_case uniformly.

    Tool Count3/5

    With only 3 tools, the count is at the lower borderline. While the 'tickets' tool bundles multiple actions (list, get, bulk_get, history, types), the overall set feels slightly thin for a platform that likely involves CRUD and lifecycle management.

    Completeness2/5

    The tools are purely read-only (retrieve, search, stats). Missing operations to create, update, delete, or take action on tickets (e.g., takedown) is a significant gap for a security platform, limiting agent ability to respond to threats.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues

    Resources