Skip to main content
Glama
Sign In
detection-enabler

detection-enabler

by cjohnston33
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Related Servers

Alternatives to detection-enabler

No user-submitted related servers found.

    Related Servers

    • govmcp

      sarathalapad
      A
      license
      Not graded
      quality
      C
      maintenance
      Enables AI agents to operate a simulated IT operations environment through policy-enforced, risk-tiered tool calls with human approval for risky writes, dry-run previews, rate limits, emergency lockdown, and tamper-evident auditing.
      MIT

    • Squidbrake

      batrapulkit
      A
      license
      B
      quality
      A
      maintenance
      Enables AI agents and MCP clients to route every tool call through configurable rules that allow, block, or hold risky actions for human approval, while recording decisions in a tamper-evident audit trail.
      12
      1,104 PyPI
      18
      Apache 2.0

    • Alexa Trust Intelligence

      malathilatha
      A
      license
      Not graded
      quality
      C
      maintenance
      Enables an Alexa+ agent to check payment, access, and credential requests for fraud or social engineering before acting, using deterministic rule scoring with Bedrock-assisted signal extraction and human approval for held or reviewed cases.
      MIT

    • openstack-incidents

      jiang369-lucky
      A
      license
      B
      quality
      C
      maintenance
      Enables MCP-compatible agents to perform read-only incident investigations by querying logs, building timelines, searching runbooks, validating evidence, and creating ticket drafts only with explicit approval.
      7
      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

    A3.6/5.0

    Scored across 4 tools

    Disambiguation4/5

    check_rule_readiness and request_rule_enable both involve a readiness check, but one is read-only and the other files a request; descriptions clarify the distinction. list_rules and get_enable_request have clearly separate purposes.

    Naming Consistency4/5

    All names are snake_case with a verb-first pattern (check_, request_, get_, list_), which is consistent overall. 'request_rule_enable' is slightly awkward phrasing but still follows the verb_noun convention.

    Tool Count5/5

    Four tools for a narrow workflow (list rules, check readiness, request enable, check request status) is well-scoped; each tool earns its place without redundancy.

    Completeness4/5

    The core lifecycle is covered: list rules, check readiness, request enable, and track request status. Minor gaps exist—no tool to list all enable requests or cancel a pending request—but agents can work around these by tracking IDs from request responses.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources