Skip to main content
Glama
mcp-guarded-tools

mcp-guarded-tools

by ridwanspace

Related Servers

Alternatives to mcp-guarded-tools

No user-submitted related servers found.

    Related Servers

    • A
      license
      Not graded
      quality
      C
      maintenance
      An authenticated MCP gateway that ingests documents and orchestrates hundreds of tools via progressive discovery, keeping context cost constant. It provides per-user RAG over ingested documents and a 116-tool registry that the model navigates through search, describe, and invoke tools.
      MIT
    • A
      license
      Not graded
      quality
      D
      maintenance
      A meta-server that aggregates multiple MCP servers into a single interface, reducing token usage by 98%+ through progressive tool discovery and direct code execution that processes data between tools without consuming context window space.
      16 npm
      10
      Apache 2.0
    • A
      license
      Not graded
      quality
      D
      maintenance
      Token-optimized MCP server that reduces context window usage by 59.5% by grouping 12 tools into 5 semantic operations, preserving all original functionality for AI assistants.
      6 npm
      1
      MIT
    • A
      license
      A
      quality
      A
      maintenance
      An MCP server that keeps raw tool output out of the context window by sandboxing and compressing results (about 98% reduction), persisting file edits, git operations, tasks and decisions in SQLite with BM25 retrieval so the agent resumes after compaction, and enforcing routing across 17 platforms via MCP and hooks. It also encourages the model to write scripts that compute answers and log only results instead of reading large data into context.
      10
      45,207 npm
      2
      Elastic 2.0

    TDQS

    A4.3/5.0

    Scored across 4 tools

    Disambiguation5/5

    Each tool has a clearly distinct role: discovery (search_tools), inspection (describe_tool), authorization (confirm_action), and execution (invoke_tool). No overlap or ambiguity exists between their purposes.

    Naming Consistency5/5

    All tool names follow the same verb_noun pattern with underscores (search_tools, describe_tool, confirm_action, invoke_tool). The naming is perfectly consistent and predictable.

    Tool Count5/5

    With 4 tools, the set is tightly scoped for a proxy/guardian layer. Each tool earns its place and there is no bloat or missing essential step in the workflow.

    Completeness5/5

    The tool set covers the complete lifecycle: discovery, detail inspection, confirmation for mutations, and invocation. There are no obvious gaps; the guard mechanism is fully realized.

    Maintenance

    ActivityStale
    ResponsivenessSyncing