Skip to main content
Glama

Related Servers

Alternatives to mcp-moat

No user-submitted related servers found.

    Related Servers

    • A
      license
      Not graded
      quality
      C
      maintenance
      Governs any stdio MCP server by interposing between the agent and the server, enforcing policy on every tools/call and refusing denied actions before they reach the upstream server.
      18 npm
      Apache 2.0
    • A
      license
      Not graded
      quality
      B
      maintenance
      Sits in front of any MCP server to enforce allow/ask/block policies on tool calls, paths, shell commands, and network domains, with local approval prompts and an audit log.
      MIT
    • A
      license
      Not graded
      quality
      C
      maintenance
      A transparent MCP stdio proxy that sits between an agent client and a real MCP server, intercepting tools/call requests to enforce runtime guardrails derived from the same YAML rules used for CI regression testing. It blocks forbidden, out-of-whitelist, looping, or non-idempotent tool invocations with JSON-RPC errors and writes every decision to an audit log.
      1
      MIT
    • F
      license
      Not graded
      quality
      B
      maintenance
      A firewall proxy for any stdio MCP server: every tool call is checked against a restrict-only policy before it runs, with encoded-argument inspection, taint tracking so private data can't leave, tool pinning, and a write-ahead audit log.
      1
      -
    • A
      license
      Not graded
      quality
      D
      maintenance
      A local-first stdio proxy for MCP servers that traps destructive tool calls and holds them for manual commit or discard, preventing accidental mutations.
      AGPL 3.0
    • A
      license
      Not graded
      quality
      B
      maintenance
      Policy sidecar for any MCP server: deny-by-default tool allowlist with argument rules, call and USD budget caps, and a hash-chained audit log with RFC 3161 timestamps.
      9
      Apache 2.0

    TDQS

    A3.6/5.0

    Scored across 16 tools

    Disambiguation3/5

    The deprecated read_file sits alongside read_text_file with the same purpose, forcing the agent to remember which to use; the three listing tools (list_directory, list_directory_with_sizes, directory_tree) also overlap. Descriptions do a good job of pointing to the right variant in each case, but the deprecated duplicate is a real misselection hazard.

    Naming Consistency4/5

    Nearly all names follow a snake_case verb_noun pattern (read_file, write_file, create_directory, list_directory, get_file_info). The main deviations are the bare noun 'directory_tree' and the adjective in 'list_allowed_directories', which are readable but break the pattern slightly.

    Tool Count4/5

    16 tools is on the heavy side of the suggested 3-15 band, but a filesystem server genuinely needs read/write/list/search/metadata coverage. The deprecated read_file is a wasted slot that could be removed to tighten the set.

    Completeness3/5

    Core read/write/move/copy/edit/directory operations are well covered, but there is no delete/remove operation at all, which is a notable lifecycle gap for a filesystem server. Content search (grep) is also absent — search_files is explicitly name-only — so agents can hit dead ends on common tasks.

    Maintenance

    ActivityMaintained
    ResponsivenessNo recent community issues