Skip to main content
Glama
co2water

agentegress

by co2water
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Go
Local

Related Servers

Alternatives to agentegress

No user-submitted related servers found.

    Related Servers

    • a2a-trustgate

      jyswee
      F
      license
      Not graded
      quality
      D
      maintenance
      MCP server for AI agent compliance that screens actions before execution and records decisions in an immutable, SIEM-ready audit trail.
      47 npm
      -

    • MCP IT Ops Server

      m3yyyyy
      A
      license
      Not graded
      quality
      C
      maintenance
      Enables AI clients to perform safe, read-only IT diagnostics and retrieve local runbooks, asset records, and knowledge articles through MCP, with allowlisted network checks and audit logging.
      MIT

    • dibs

      JoshTerAvest
      A
      license
      Not graded
      quality
      B
      maintenance
      A local MCP server that lets multiple AI agents safely share a Windows desktop by coordinating exclusive access to the mouse, keyboard, screen, and windows, with human consent, takeover, and full activity logging.
      2 npm
      MIT

    • Velociraptor MCP

      mgreen27
      F
      license
      Not graded
      quality
      C
      maintenance
      A proof-of-concept MCP bridge that exposes Velociraptor's forensic triage tools to LLMs, enabling natural language querying of Windows endpoints for artifacts like network connections and suspicious processes.
      94
      -
    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

    A4.1/5.0

    Scored across 8 tools

    Disambiguation5/5

    Each tool targets a clearly distinct resource or action: agent trees, listening ports, outgoing connections, autostarts, findings, logon events, single-process detail, and an aggregate scan. The descriptions actively cross-reference each other (e.g. list_agents vs list_connections vs explain_process) to steer correct selection, leaving little ambiguity.

    Naming Consistency4/5

    Five tools follow a clean list_* verb_noun pattern (list_agents, list_connections, list_listening_ports, list_autostarts, list_findings), and explain_process/scan_summary fit verb_noun. login_activity deviates slightly as a noun phrase, but overall the convention is predictable.

    Tool Count5/5

    Eight tools is well-scoped for a host/agent security-monitoring server, with each tool covering a distinct facet (summary, agents, connections, ports, persistence, findings, logons, process detail). No tool feels redundant or missing at this granularity.

    Completeness4/5

    The surface covers the full read-only monitoring lifecycle: an aggregate verdict, per-process detail, network exposure, persistence, findings, and logon history, with escalation paths between tools. It lacks any remediation or acknowledgment action (e.g. dismissing findings or terminating a process), a minor gap for a monitoring-focused server.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources