Skip to main content
Glama
Sign In
ISO-toolset MCP

ISO-toolset MCP

by AMishradev
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

Related Servers

Alternatives to ISO-toolset MCP

No user-submitted related servers found.

    Related Servers

    • mcp-gateway

      gishwinantony
      A
      license
      Not graded
      quality
      C
      maintenance
      Provides a security and context-control layer that multiplexes multiple MCP servers behind a single endpoint, scanning tool definitions and results, enforcing authorization, rate limiting, and audit logging, and dynamically retrieving tools to manage context window usage.
      MIT
    • mcp-servers

      mcp-serversofficial

      DXHeroes
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables deploying standalone MCP connectors, discovering them through a validated catalog, and running an optional trusted polyglot runtime for the DX Heroes MCP Gateway.
      Apache 2.0

    • Gate22

      stewart137
      A
      license
      Not graded
      quality
      A
      maintenance
      Enables teams to onboard remote MCP servers, enforce function-level permissions and credential modes, and let developers expose permitted tools through a unified MCP endpoint with search and execute functions while auditing usage.
      MIT

    • mcpstead

      ahkohd
      A
      license
      Not graded
      quality
      D
      maintenance
      MCP Gateway that aggregates multiple upstream MCP servers into a single endpoint with persistent connections, tool registry, and authentication.
      84 npm
      2
      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

    B3.2/5.0

    Scored across 5 tools

    Disambiguation4/5

    Each tool targets a distinct lifecycle action: start, stop, status, help, and call. The only mild overlap is between cortex-start (which discovers tools on attach) and cortex-help (which returns live tool schemas), but descriptions clarify the difference well enough for correct selection.

    Naming Consistency5/5

    All five tools share a consistent cortex-<verb/noun> prefix-and-action pattern (start, status, help, call, stop). The convention is predictable and readable throughout.

    Tool Count5/5

    Five tools is well-scoped for a runtime proxy: session lifecycle plus a single call-forwarding entry point. There are no redundant or filler tools.

    Completeness4/5

    Start/status/help/call/stop cover the full session lifecycle and invocation path, which is the stated domain. Minor gaps remain, such as no dedicated tool-listing operation separate from start/help and no explicit configuration or restart operation.

    Resources