Skip to main content
Glama
LuminariSoftwares

tool-guardian

by LuminariSoftwares
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Related Servers

Alternatives to tool-guardian

No user-submitted related servers found.

    Related Servers

    • MCPNexus

      KrzysztofAugiewicz
      A
      license
      A
      quality
      B
      maintenance
      A discovery and routing layer for MCP servers that loads tool definitions on demand, reducing token usage by keeping servers out of the context window until needed.
      4
      MIT

    • OmniMCP

      milkymap
      A
      license
      Not graded
      quality
      C
      maintenance
      A semantic router that provides unified access to multiple MCP servers through a single tool interface, using vector search to discover and execute tools across your entire MCP ecosystem while minimizing context token usage.
      30
      MIT

    • context-saver

      msuther898
      A
      license
      Not graded
      quality
      D
      maintenance
      MCP proxy that reduces context usage through semantic tool routing, enabling on-demand discovery and routing of relevant tools.
      MIT

    • MCP Coordinator

      CyberClash
      A
      license
      Not graded
      quality
      D
      maintenance
      Acts as a proxy for multiple MCP servers, reducing context window usage from 15,000+ tokens to ~500 tokens by dynamically loading servers on-demand and exposing only 3 tools instead of all tool definitions.
      5
      GPL 3.0

    • MCP Nexus

      Aidan-Kay
      A
      license
      Not graded
      quality
      B
      maintenance
      A single MCP endpoint for AI agents to browse, inspect, and call tools from multiple upstream MCP servers without loading all schemas upfront, reducing context overhead.
      7 npm
      ISC

    • Agent MCP Gateway

      roddutra
      A
      license
      A
      quality
      C
      maintenance
      Provides per-Subagent MCP controls to any coding agent or client across all your MCPs and prevents context window waste. Loads only 3 tools instead of all your MCP Server's tool definitions. Agents discover tools on-demand, only when needed and only the servers and tools they are allowed.
      4
      41
      MIT
    Deploy Server
    Shareable, User-Owned Context BackendPeople, applications, and agents read, write, and coordinate together in one context lake. Reach it over MCP, a CLI, a Python SDK, or REST.fulcradynamics.comAd

    TDQS

    A3.9/5.0

    Scored across 6 tools

    Disambiguation4/5

    Most tools have clearly distinct roles: call_tool invokes, retrieve_spill recovers shortened output, and list_groups_with_costs reports costs. The three discovery tools (list_capabilities, search_capabilities, describe_tool) share a 'find/inspect' space but are differentiated by scope (all, by keyword, one detail), so confusion is limited.

    Naming Consistency5/5

    All names use a consistent snake_case verb_noun pattern (list_capabilities, search_capabilities, describe_tool, call_tool, retrieve_spill, list_groups_with_costs). No mixed conventions or vague verbs.

    Tool Count5/5

    Six tools is well-scoped for a meta/gateway server, covering discovery, invocation, output recovery, and cost reporting without redundancy. Each tool earns a distinct place in the workflow.

    Completeness4/5

    The surface covers the key lifecycle of a proxy: discover tools (list/search/describe), invoke them (call_tool), and handle truncated results (retrieve_spill), plus cost awareness. Minor gap: no explicit connection/registration management, though that may be out of scope.

    Maintenance

    ActivityActive
    ResponsivenessNo issues

    Resources