Skip to main content
Glama
gaharivatsa

ToolBox

by gaharivatsa
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Related Servers

Alternatives to ToolBox

No user-submitted related servers found.

    Related Servers

    • jev-router by ini8labs

      jev-routerofficial

      ini8labs
      A
      license
      A
      quality
      C
      maintenance
      Enables agents to connect through a single gateway that has a decision model pick which MCP tools and playbooks are relevant to each request, so the LLM only sees the few schemas it needs, and to then invoke those tools on the underlying servers. This cuts tool-selection cost and prompt size dramatically when many MCP servers are connected.
      2
      4
      MIT

    • MCP Nexus

      dsk-dev-ai
      A
      license
      Not graded
      quality
      A
      maintenance
      Provides a single MCP endpoint that dynamically discovers, routes, policy-checks, and executes hundreds of MCP tools from any agent, with optional LLM-based routing.
      4 npm
      1
      Apache 2.0

    • mcp-nexus

      fyrlabs
      A
      license
      A
      quality
      A
      maintenance
      Enables AI harnesses to connect to a single MCP endpoint that routes to multiple downstream MCP servers, discovering and executing capabilities on demand while keeping tool schemas out of context.
      4
      13 npm
      Apache 2.0

    • smart-router

      chris-asmussen
      A
      license
      A
      quality
      D
      maintenance
      A single MCP server that fronts many downstream MCP servers and Skills, exposing only four tools (search, call_tool, use_skill, admin) so that an agent's context window only ever sees search results on demand.
      5
      10
      MIT

    • gatehouse

      srikrishnavansi
      A
      license
      Not graded
      quality
      C
      maintenance
      Sits between an agent and an upstream MCP server to enforce per-profile tool grants, deterministic allow/deny/handoff rules, field and PII masking, idempotent writes, and one-line audit logging from a single YAML config. Enables regulated deployments to add guardrails that fail closed without changing the customer's tools or the agent's prompt.
      MIT

    • MCP Gateway

      SachuJames
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables agents to access multiple upstream Model Context Protocol servers through a single endpoint with API-key authentication, scoped access, rate limiting, guardrails, and audit logging. Tools are namespaced by upstream so clients can discover and call them via one tools/list and tools/call surface.
      13 npm
      MIT
    Deploy Server
    Context Every Agent Can ShareAgents share what they learn, hand off work, and keep it when you switch models. Start with 5 GB free.fulcradynamics.comAd

    TDQS

    A4.3/5.0

    Scored across 3 tools

    Disambiguation4/5

    find_tools and browse_tools both aid discovery, but descriptions clearly distinguish them: find_tools uses natural-language search, while browse_tools is a fallback catalog browser. call_tool is unambiguously for execution, so only minor overlap exists.

    Naming Consistency4/5

    All names use snake_case and follow a verb_noun pattern (find_tools, call_tool, browse_tools). The only inconsistency is call_tool using singular 'tool' while the others use plural 'tools', which is a minor deviation.

    Tool Count5/5

    Three tools form a minimal, well-scoped interface for a meta-server: search for tools, execute a tool, and browse the catalog when search fails. Each tool earns its place without redundancy.

    Completeness5/5

    The surface covers the full lifecycle of tool discovery and invocation: find_tools returns tool IDs with schemas, call_tool executes with arguments, and browse_tools provides fallback listing and detailed descriptions. No obvious operational gaps exist for this domain.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources