Skip to main content
Glama
universal-tool-calling-protocol

UTCP-MCP Bridge

Official
by universal-tool-calling-protocol
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

Related Servers

Alternatives to UTCP-MCP Bridge

No user-submitted related servers found.

    Related Servers

    • mcp-server

      gwanghun-choi
      A
      license
      Not graded
      quality
      C
      maintenance
      A universal MCP server for registering internal, external, and OpenAPI-based APIs as MCP tools. It exposes them to MCP clients via Streamable HTTP and provides admin portal, RBAC/session auth, credential injection, and audit logging.
      Academic Free v1.1

    • proxy-mcp

      Rixmerz
      F
      license
      A
      quality
      D
      maintenance
      Universal MCP proxy server that discovers, searches, and executes tools across all configured MCP servers from a single entry point.
      7
      -

    • MCP Proxy Server

      ptbsare
      A
      license
      Not graded
      quality
      C
      maintenance
      Aggregates multiple backend MCP servers into a single unified interface with optional web management UI for tool control and configuration.
      68 npm
      196
      MIT

    • data-mcp

      Tattzy25
      A
      license
      Not graded
      quality
      B
      maintenance
      MCP server generated from an OpenAPI Specification, exposing tools via HTTP. It allows clients to invoke API operations using JSON-RPC 2.0 requests.
      7 npm
      Artistic 2.0

    • MCP Tools Hub

      lapaduga
      F
      license
      Not graded
      quality
      D
      maintenance
      MCP server with a web interface for viewing and calling tools via REST API, enabling easy tool management through a browser.
      -
    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.6/5.0

    Scored across 7 tools

    Disambiguation5/5

    Each tool targets a distinct operation: calling, registering, deregistering, listing, searching, retrieving keys, and getting info. No two tools overlap in purpose.

    Naming Consistency4/5

    Most tools follow verb_noun pattern (e.g., call_tool, list_tools), but tool_info uses noun_noun instead of get_tool_info, introducing a minor inconsistency.

    Tool Count5/5

    With 7 tools covering registration, deregistration, listing, searching, calling, and info retrieval, the count is well-scoped for a bridge server.

    Completeness5/5

    The tool set covers the full lifecycle: register, deregister, list, search, call, and retrieve necessary information (keys and details). No obvious gaps for the intended purpose.

    Maintenance

    ActivityInactive
    ResponsivenessUnresponsive

    Resources