Skip to main content
Glama
theYahia

@theyahia/mts-exolve-mcp

by theYahia

Related Servers

Alternatives to @theyahia/mts-exolve-mcp

No user-submitted related servers found.

    Related Servers

    • A
      license
      Not graded
      quality
      C
      maintenance
      Enables AI agents to manage Rostelecom Virtual PBX telephony, including contacts, subscribers, call groups, call history, call recordings, numbers and routing, balance, and transparent proxy to any of ~240 endpoints.
      MIT
    • A
      license
      A
      quality
      B
      maintenance
      Enables managing Kontur.Elba data through the official Public API, including organizations, bank accounts, counterparties, products, documents, invoices, and public links via MCP tools.
      4
      4 npm
      MIT

    TDQS

    B3.2/5.0

    Scored across 8 tools

    Disambiguation5/5

    Each tool targets a distinct resource and action: SMS vs Viber, call vs SMS, status vs recording. There's no overlap between send_sms, send_viber_message, make_call, or get_call_recording. Even similar pairs like get_sms_status and get_call_status are clearly separated by context.

    Naming Consistency5/5

    All tools follow a verb_noun snake_case pattern: send_sms, get_sms_status, make_call, get_call_status, get_call_recording, list_numbers, buy_number, send_viber_message. Verbs are simple and consistent across actions.

    Tool Count5/5

    With 8 tools, the server covers multiple communication channels (SMS, calls, Viber) and number management without excess. The scope is focused and each tool adds distinct value, fitting the typical 3-15 range perfectly.

    Completeness4/5

    The surface covers core SMS and call lifecycles (send/status, make/status/recording), number listing and purchasing, and Viber sending. Minor gaps exist: no Viber status check, no number release/deletion, and no call or SMS history listing, but the essential workflows are functional.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues