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
Each tool has a clear, separate purpose: one lists all transmissions, the other retrieves a single transmission by ID. There is no overlap or ambiguity between the two.
Both tools follow the same verb_noun pattern with a consistent ictfax_ prefix (list_faxes, get_fax_status). The naming is predictable and uniform.
With only two tools, the server feels minimal and borderline thin for a fax integration. It covers listing and status checking but lacks the breadth expected of a full service, though it could be acceptable for a narrowly scoped monitoring tool.
The tool surface covers only read-oriented operations (list and get status). There is no way to send, cancel, or manage faxes, which are core actions for a fax server, leaving significant functionality absent.