Skip to main content
Glama
ictfax-mcp

ictfax-mcp

Official

Related Servers

Alternatives to ictfax-mcp

No user-submitted related servers found.

    Related Servers

    • A
      license
      Not graded
      quality
      D
      maintenance
      Enables AI agents to send free and paid faxes to US and Canada numbers, check fax status, and purchase prepaid credits, all without leaving the chat.
      MIT
    • A
      license
      A
      quality
      A
      maintenance
      Enables AI assistants to send real faxes through the FaxDrop API. Provides safeguards including rate limiting, dry-run mode, and audit logging for secure fax operations.
      3
      255 npm
      5
      MIT
    • A
      license
      Not graded
      quality
      D
      maintenance
      Send, receive, and verify faxes from AI assistants and agents via the Model Context Protocol.
      122 npm
      MIT
    • A
      license
      A
      quality
      B
      maintenance
      Enables AI assistants to monitor ICTBroadcast outbound voice, SMS, and fax campaigns by listing campaigns, checking status, and reading summaries and per-call results, with optional start/stop control when write access is enabled.
      4
      234 npm
      16
      MIT
    • A
      license
      B
      quality
      A
      maintenance
      Enables AI assistants to monitor outbound campaigns in ICTContact/ICTDialer, including listing campaigns, checking status, reading summaries and per-call results, and optionally starting and stopping campaigns when write access is enabled.
      4
      144 npm
      16
      MIT
    • A
      license
      B
      quality
      A
      maintenance
      Enables AI assistants to monitor ICTDialer outbound campaigns by listing them, checking status, and reading summaries and per-call results, with optional start and stop capabilities when write access is enabled.
      4
      220 npm
      16
      MIT

    TDQS

    A3.7/5.0

    Scored across 2 tools

    Disambiguation5/5

    The two tools target clearly different operations: listing transmissions versus fetching a single transmission by id. Their descriptions even specify the intended workflow order (list to find an id, then get status), leaving no room for misselection.

    Naming Consistency4/5

    Both names follow a predictable ictfax_ prefix plus verb_noun structure (get_fax_status, list_faxes). The only minor wrinkle is the singular/plural split between 'fax' and 'faxes', which is natural but slightly uneven.

    Tool Count2/5

    Two tools is very thin for a fax transmission server, and one of them exists only to support the other. There is no operation to actually send or manage a fax, making the surface feel incomplete rather than deliberately minimal.

    Completeness1/5

    The domain clearly includes sending faxes ('poll this after sending a fax'), yet no send, cancel, delete, or content-retrieval tool exists. Only read operations are exposed, so core fax lifecycle workflows will dead-end.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues