Skip to main content
Glama
hermes-local-agent-lanes

hermes-local-agent-lanes

Related Servers

Alternatives to hermes-local-agent-lanes

No user-submitted related servers found.

    Related Servers

    • F
      license
      Not graded
      quality
      C
      maintenance
      Provides a secure MCP boundary for AI agents, intercepting and validating tool calls, redacting secrets, and requiring human approval for sensitive actions with a tamper-evident audit trail.
      -
    • A
      license
      Not graded
      quality
      C
      maintenance
      Enables MCP clients such as Claude Desktop and Claude Code to read café rules, rota, and staff data, check proposed rota changes against the owner's rules, and evaluate customer chat replies before sending. Every tool is read-only, with code checks applied first and AI judging used only when needed.
      1
      MIT
    • A
      license
      Not graded
      quality
      D
      maintenance
      A safe, allowlisted MCP server that lets AI agents run only a tiny set of harmless tools (echo, datetime, hash, dig, GET-only curl, whois, status checks) against explicitly allowed hosts, with sanitization, rate limiting, timeouts, and full audit logging.
      MIT
    • A
      license
      A
      quality
      D
      maintenance
      An MCP server that sits between coding agents and local tools, using a tiny on-device model to route tool calls and requiring confirmations for destructive actions, while only exposing four tools to the host.
      4
      MIT
    • A
      license
      Not graded
      quality
      C
      maintenance
      Enables AI agents to securely discover, invoke, and manage tools through a hardened MCP endpoint with protections like injection detection, circuit breakers, retry backoff, response caching, context-window limiting, and state snapshots.
      7 npm
      MIT

    TDQS

    A3.8/5.0

    Scored across 2 tools

    Disambiguation5/5

    The two tools are clearly distinct: one is for querying a local model with restrictions, the other is a health check for endpoint connectivity. No overlap in purpose.

    Naming Consistency4/5

    Both tools share the prefix 'local_support', creating a consistent pattern. The health tool appends '_health', which is predictable but not a strict verb_noun structure.

    Tool Count3/5

    With only two tools, the surface is minimal. While a focused health-check server might justify this count, the support tool covers broad tasks, suggesting additional tools (e.g., configuration) could be expected.

    Completeness3/5

    The set provides a basic query interface and health check, covering primary needs. However, missing tools for configuration, model listing, or error handling leaves notable gaps for a local model server.

    Maintenance

    ActivityInactive
    ResponsivenessNo recent community issues