ictfax-mcp
OfficialRelated Servers
Alternatives to ictfax-mcp
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityDmaintenanceEnables 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
- AlicenseAqualityAmaintenanceEnables 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.3255 npm5MIT
- AlicenseNot gradedqualityDmaintenanceSend, receive, and verify faxes from AI assistants and agents via the Model Context Protocol.122 npmMIT

ictbroadcast-mcpofficial
AlicenseAqualityBmaintenanceEnables 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.4234 npm16MIT
ictcontact-mcpofficial
AlicenseBqualityAmaintenanceEnables 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.4144 npm16MIT
ictdialer-mcpofficial
AlicenseBqualityAmaintenanceEnables 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.4220 npm16MIT
TDQS
Scored across 2 tools
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.
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.
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.
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.