Skip to main content
Glama
Adriftnote

Tool Box MCP Server

by Adriftnote
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Related Servers

Alternatives to Tool Box MCP Server

No user-submitted related servers found.

    Related Servers

    • Relay

      adarshp14
      A
      license
      Not graded
      quality
      D
      maintenance
      Enables AI agents to access a unified catalog of tools from various APIs (OpenAPI, GraphQL, MCP, Google Discovery) through the MCP protocol.
      MIT

    • Smart MCP Proxy

      Dumbris
      A
      license
      Not graded
      quality
      D
      maintenance
      Federating gateway for AI agents to discover and call tools from multiple MCP servers with intelligent search and dynamic tool registration.
      39
      MIT

    • agent-discover

      keshrath
      A
      license
      Not graded
      quality
      F
      maintenance
      MCP server registry and marketplace that enables dynamic discovery, installation, and activation of tools at runtime, allowing AI agents to use new tools without restarting.
      99 npm
      7
      MIT

    • executor

      UsefulSoftwareCo
      A
      license
      Not graded
      quality
      A
      maintenance
      An integration layer for AI agents that provides a catalog of tools from various sources (OpenAPI, GraphQL, MCP, etc.) and can be used as an MCP server for compatible agents.
      3,915
      MIT
    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.1/5.0

    Scored across 4 tools

    Disambiguation2/5

    toolhub_search and toolhub_cluster substantially overlap: both take a natural language query and return relevant tools with optional Knowledge Graph expansion, making it unclear when to prefer one. toolhub_expand and toolhub_health are distinct, but the boundary between search and cluster is not crisp.

    Naming Consistency3/5

    All tools share the toolhub_ prefix and snake_case, but the suffixes are inconsistent in style: search and expand are verbs, health is a noun, and cluster is a noun/verb. A pattern like toolhub_get_cluster or toolhub_check_health would be clearer.

    Tool Count5/5

    Four tools is well-scoped for a tool-discovery service: search, dependency expansion, full cluster assembly, and health checking. Each tool has a clear operational role, and the count is neither thin nor bloated.

    Completeness4/5

    The core discovery workflow (query, expand, cluster, health) is covered with no dead ends. Minor gaps exist: there is no direct list-all-tools or get-tool-detail operation, and cluster largely subsumes search, but agents can accomplish the main task.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues

    Resources