Skip to main content
Glama
clarenous

VeyraX MCP

by clarenous
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Remote

Related Servers

Alternatives to VeyraX MCP

No user-submitted related servers found.

    Related Servers

    • mcp-gateway

      R0Wi
      A
      license
      Not graded
      quality
      A
      maintenance
      Enables clients to access multiple backend MCP servers through a single endpoint, with OAuth 2.1 authorization, namespaced tools, and secure credential management.
      1
      MIT

    • MCPX MCP Gateway

      TheLunarCompany
      A
      license
      Not graded
      quality
      C
      maintenance
      MCPX is a remote-first MCP aggregator that enables zero-code integration, unified access, and dynamic routing across multiple MCP servers. It offers tool-level access controls, usage visibility, and customization to streamline and secure agentic workflows.
      499
      MIT

    • MCP Ambassador Server

      mcpambassador
      A
      license
      Not graded
      quality
      D
      maintenance
      Centralized authentication, authorization, and audit for MCP tools. One server governs every downstream MCP your organization uses.
      3
      Apache 2.0

    • MCP Workstation

      anshace
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables AI clients to connect once and access tools from many registered MCP servers plus built-in modules, with multi-user authentication, per-user server/tool toggles, and a skills hub.
      MIT

    • MCP Proxy Server

      adamwattis
      A
      license
      Not graded
      quality
      F
      maintenance
      A central hub that aggregates multiple MCP resource servers into a single unified interface, enabling users to access tools and capabilities from multiple backend servers through one connection point.
      68 npm
      203
      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

    A3.7/5.0

    Scored across 3 tools

    Disambiguation5/5

    Each tool has a clearly distinct purpose with no overlap: get_flow retrieves a specific workflow, get_tools lists available tools and flows, and tool_call executes a method from another tool. The descriptions explicitly differentiate their functions, making misselection unlikely.

    Naming Consistency5/5

    All tool names follow a consistent snake_case pattern with clear verb_noun structures: get_flow, get_tools, and tool_call. This uniformity enhances readability and predictability across the set.

    Tool Count5/5

    With 3 tools, this server is well-scoped for its purpose of managing workflows and dynamic tools. Each tool earns its place by covering essential operations: retrieving workflows, listing tools, and executing tool methods, without being overly sparse or bloated.

    Completeness4/5

    The tool set provides complete coverage for core workflows: retrieving tools and flows, and executing methods. A minor gap exists in lifecycle management (e.g., creating or updating flows), but agents can work around this given the dynamic nature of the tools, and the surface supports the stated purpose effectively.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues

    Resources