ictfax-mcp
OfficialServer Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| ICTFAX_BASE_URL | Yes | ICTCore REST base, normally ending in `/api`, e.g. `https://your-ictfax/api` | |
| ICTFAX_PASSWORD | Yes | Password for that account | |
| ICTFAX_USERNAME | Yes | API account email (ICTCore logs in by email) | |
| ICTFAX_ACCOUNT_ID | No | Account id to send faxes from | 1 |
| ICTFAX_TIMEOUT_MS | No | Per-request timeout | 30000 |
| ICTFAX_TLS_INSECURE | No | Skip TLS verification — self-signed test servers only | false |
| ICTFAX_MCP_ALLOW_WRITE | No | Unlock upload/send (see Safety) | false |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| ictfax_list_faxesA | List fax transmissions on the server (inbound and outbound) with their id, contact, status and direction. Start here to find a transmission id. |
| ictfax_get_fax_statusA | Get one fax transmission by id: its status (processing, completed, failed), contact and pages. Poll this after sending a fax. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
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.