Skip to main content
Glama
muhammadyusuf-kurbonov

utel-mcp

Related Servers

Alternatives to utel-mcp

No user-submitted related servers found.

    Related Servers

    • A
      license
      A
      quality
      D
      maintenance
      A Model Context Protocol server that enables AI assistants to make HTTP requests (GET, POST, PUT, DELETE) to external APIs through standardized MCP tools.
      4
      2
      MIT
    • A
      license
      B
      quality
      C
      maintenance
      An MCP server that enables AI assistants to interact with the VoIPbin CPaaS platform, exposing tools for managing calls, flows, messaging, conferencing, and more.
      52
      1
      MIT
    • F
      license
      Not graded
      quality
      C
      maintenance
      Official MCP server for interacting with Bandwidth APIs (messaging, voice, number lookup, etc.) via AI agents. Supports configurable tool filtering and multiple deployment modes.
      2
      -
    • A
      license
      Not graded
      quality
      D
      maintenance
      A generic MCP server that dynamically converts OpenAPI-defined REST APIs into tools for LLMs like Claude. It supports multiple authentication methods and transport protocols, enabling seamless interaction with any OpenAPI-compliant API.
      8 npm
      MIT
    • F
      license
      A
      quality
      D
      maintenance
      An MCP server that enables LLMs to make arbitrary HTTP requests (GET, POST, PUT, DELETE, etc.) with custom headers, bodies, and cookies, supporting JSON and error handling.
      1
      2
      -

    TDQS

    A3.5/5.0

    Scored across 1 tool

    Disambiguation5/5

    With only one tool, there is no potential for confusion between tools. The single tool has a distinct purpose: sending requests to the UTEL API.

    Naming Consistency5/5

    Only one tool exists, so naming consistency is not an issue. The name 'send_request' follows a verb_noun pattern.

    Tool Count1/5

    A single generic tool for an entire API surface is an extreme mismatch. The tool count is far too low for any non-trivial domain; it forces the agent to manage all API logic internally.

    Completeness1/5

    The single tool provides no specialized operations (e.g., CRUD, search), leaving agents to manually construct requests for every action. This is severely incomplete for a typical API interface.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues