Skip to main content
Glama

Related Servers

Alternatives to lugh

  • A
    license
    Not graded
    quality
    B
    maintenance
    Gives AI agents policy-checked tools for shell commands, file reads and writes, HTTP fetches and tool calls, deciding each action against a policy before it runs while tracking secret taint and recording every decision in a tamper-evident audit log.
    MIT

Related Servers

  • F
    license
    Not graded
    quality
    C
    maintenance
    Enables AI coding agents to request bounded GitHub changes through a default-deny policy, independent human approval, one-time execution with a GitHub App credential, and verifiable receipts.
    1
    -
  • A
    license
    A
    quality
    C
    maintenance
    Local zero-trust permission gateway for AI agents. Enforces policy-based tool authorization, human approvals, scoped permissions, and cryptographically verifiable audit logs.
    4
    128 PyPI
    5
    Apache 2.0
  • A
    license
    A
    quality
    B
    maintenance
    Enables AI coding agents to access live operational context like processes, containers, and git state, while providing a tamper-evident audit log and policy-as-code compliance hooks locally.
    22
    445 npm
    Business Source 1.1
  • F
    license
    Not graded
    quality
    C
    maintenance
    Enables controlled AI-agent access to enterprise-shaped tools with a deny-by-default gated write path, human approval, dry-run execution, and append-only audit logging.
    1
    -
  • A
    license
    Not graded
    quality
    A
    maintenance
    Enforces policy controls for AI agents, including spend limits, action approvals, kill switch, scoped credentials, dry-run diffs, loop prevention, and auditable hash-chained logs.
    MIT

TDQS

A4/5.0

Scored across 5 tools

Disambiguation5/5

Each tool occupies a clearly distinct stage: reference (docs), check (compile only), run (execute goals in sandbox), test (execute test blocks), and sandbox (inspect the simulated world). The descriptions explicitly contrast check vs. run vs. test, so an agent can select without guessing.

Naming Consistency4/5

All names share the consistent `lugh_` prefix with snake_case, giving a predictable namespace. Minor deviation: `reference` and `sandbox` are nouns while `check`, `run`, and `test` are verbs, so the verb_noun pattern isn't uniform.

Tool Count5/5

Five tools map neatly onto the lifecycle of writing and validating a Lugh program: read docs, compile, run, test, inspect sandbox. Nothing feels padded or missing at this scope.

Completeness4/5

The surface covers the full authoring loop through simulated execution and policy logging, which is the stated purpose. Minor gaps: no lint/format or scaffolding tool, and no way to progress from sandbox to a real deployment, but agents can work around these via reference.

Maintenance

ActivityNo data
ResponsivenessOutdated data