Skip to main content
Glama
ridwanspace

mcp-guarded-tools

by ridwanspace
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Related Servers

Alternatives to mcp-guarded-tools

No user-submitted related servers found.

    Related Servers

    • Harbormaster

      theonetheycallneo
      A
      license
      Not graded
      quality
      B
      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

    • MCP of MCPs

      eliavamar
      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

    • everything-slim

      mcpslim
      A
      license
      Not graded
      quality
      C
      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.
      7 npm
      1
      MIT

    • MCP OpsBridge

      SaADii09
      F
      license
      B
      quality
      B
      maintenance
      Unified MCP server exposing 12 DevOps tools across GitHub, PostgreSQL, Slack, and Google Calendar for AI agents, with rate limiting, input validation, and per-service scoped tokens.
      30
      -
    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

    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

    ActivitySlowing
    ResponsivenessNo issues

    Resources