3,400+ MCP servers ready to use
Vinkius

Bring Cloud Fax
to Claude Desktop

Learn how to connect iFax to Claude Desktop and start using 6 AI agent tools in minutes. Fully managed, enterprise secure, and ready to use without writing a single line of code.

Cancel FaxDownload FaxGet Fax StatusList FaxesResend FaxSend Fax

What is the iFax MCP Server?

Connect your iFax account to any AI agent and manage fax communications through natural conversation.

What you can do

  • Send Faxes — Transmit documents to fax numbers worldwide with delivery confirmation
  • Track Status — Monitor real-time delivery status of sent faxes
  • Fax History — Browse all sent and received faxes with timestamps and status
  • Cancel Pending — Cancel faxes that haven't been transmitted yet
  • Resend Failed — Retry failed fax transmissions automatically
  • Download Documents — Retrieve received fax documents as files

How it works

1. Subscribe to this server
2. Enter your iFax API Key
3. Start managing faxes from Claude, Cursor, or any MCP-compatible client

Who is this for?

  • Healthcare — send HIPAA-compliant faxes for medical records and prescriptions
  • Legal Teams — transmit contracts, filings, and signed documents
  • Operations — automate fax workflows for compliance and document exchange

Built-in capabilities (6)

cancel_fax

Cancel a pending fax

download_fax

Download a fax document

get_fax_status

Check fax delivery status

list_faxes

List sent faxes

resend_fax

Resend a failed fax

send_fax

Pass faxData as a JSON string containing the file metadata and base64 content. Send a new fax

Why Claude Desktop?

Claude Desktop is the definitive way to connect iFax to your AI workflow. Add Vinkius Edge URL to your config, restart the app, and Claude immediately exposes all 6 tools in the chat interface. ask a question, Claude calls the right tool, and you see the answer. Zero code, zero context switching.

  • —

    Claude Desktop is the reference MCP client. it was designed alongside the protocol itself, ensuring the most complete and stable MCP implementation available

  • —

    Zero-code configuration: add a server URL to a JSON file and Claude instantly discovers and exposes all available tools in the chat interface

  • —

    Claude's extended thinking capability lets it reason through multi-step tool usage, chaining multiple API calls to answer complex questions

  • —

    Enterprise-grade security with local config storage. your tokens never leave your machine, and connections go directly to Vinkius Edge network

See it in action

iFax in Claude Desktop

AI Agent→Vinkius
High Security·Kill Switch·Plug and Play
Why Vinkius

iFax and 3,400+ other MCP servers. One platform. One governance layer.

Teams that connect iFax to Claude Desktop through Vinkius don't need to source, host, or maintain individual MCP servers. Every tool call runs inside a hardened runtime with credential isolation, DLP, and a signed audit chain.

3,400+MCP Servers ready
<40msCold start
60%Token savings
Raw MCP
Vinkius
Server catalogFind and host yourself3,400+ managed
InfrastructureSelf-hostedSandboxed V8 isolates
Credential handlingPlaintext in configVault + runtime injection
Data loss preventionNoneConfigurable DLP policies
Kill switchNoneGlobal instant shutdown
Financial circuit breakersNonePer-server limits + alerts
Audit trailNoneEd25519 signed logs
SIEM log streamingNoneSplunk, Datadog, Webhook
HoneytokensNoneCanary alerts on leak
Custom domainsNot applicableDNS challenge verified
GDPR complianceManual effortAutomated purge + export
Enterprise Security

Why teams choose Vinkius for iFax in Claude Desktop

The iFax MCP Server runs on Vinkius-managed infrastructure inside AWS — a purpose-built runtime with per-request V8 isolates, Ed25519 signed audit chains, and sub-40ms cold starts. All 6 tools execute in hardened sandboxes optimized for native MCP execution.

Your AI agents in Claude Desktop only access the data you authorize, with DLP that blocks sensitive information from ever reaching the model, kill switch for instant shutdown, and up to 60% token savings. Enterprise-grade infrastructure, zero maintenance.

iFax
Fully ManagedVinkius Servers
60%Token savings
High SecurityEnterprise-grade
IAMAccess control
EU AI ActCompliant
DLPData protection
V8 IsolateSandboxed
Ed25519Audit chain
<40msKill switch
Stream every event to Splunk, Datadog, or your own webhook in real-time

* Every MCP server runs on Vinkius-managed infrastructure inside AWS - a purpose-built runtime with per-request V8 isolates, Ed25519 signed audit chains, and sub-40ms cold starts optimized for native MCP execution. See our infrastructure

The Vinkius Advantage

How Vinkius secures iFax for Claude Desktop

Every tool call from Claude Desktop to the iFax MCP Server is protected by DLP redaction, cryptographic audit chains, V8 sandbox isolation, kill switch, and financial circuit breakers.

< 40msCold start
Ed25519Signed audit chain
60%Token savings
FAQ

Frequently asked questions

01

Can I send a fax to any number worldwide?

Yes. The send_fax tool transmits a document to any fax number. Provide the destination number in international format and the document content. Use get_fax_status to track delivery confirmation in real-time.

02

Can I retry a failed fax transmission?

Yes. Use resend_fax with the original fax ID to retry a failed transmission. Use list_faxes to see all faxes and their status, then identify failed ones for retry.

03

How does iFax API authentication work?

iFax uses a custom accessToken header (not standard Bearer) for authentication. Your API key from the iFax dashboard is sent in all requests to api.ifaxapp.com/v1.

04

How does Claude Desktop discover MCP tools?

When Claude Desktop starts, it reads the claude_desktop_config.json file and connects to each configured MCP server. It calls the tools/list endpoint to fetch the schema for every available tool, then surfaces them as clickable options in the chat interface via the 🔌 icon.

05

What happens if the MCP server is temporarily unavailable?

Claude Desktop handles disconnections gracefully. if the server is unreachable at startup, the tools simply won't appear. Once the server becomes available again, restarting Claude Desktop will re-establish the connection. There is no timeout penalty or error loop.

06

Can I connect multiple MCP servers simultaneously?

Yes. You can add as many servers as you need in the mcpServers section of the config file. Each server appears as a separate tool provider, and Claude can use tools from multiple servers in a single conversation turn.

07

Is there a limit on the number of tools per server?

Claude Desktop can handle hundreds of tools per server. However, for optimal LLM performance, Vinkius servers are designed to expose focused, well-documented tool sets rather than overwhelming the model with too many options.

08

Does Claude Desktop support Streamable HTTP transport?

Yes. Claude Desktop supports both SSE (Server-Sent Events) and the newer Streamable HTTP transport that Vinkius uses. Simply provide the server URL. Claude auto-negotiates the transport protocol.

09

Server not appearing after restart

Ensure the JSON is valid (no trailing commas). Check the file path: ~/Library/Application Support/Claude/claude_desktop_config.json (macOS) or %APPDATA%\\Claude\\ (Windows).

10

Authentication error

Verify your Vinkius token is correct. Go to cloud.vinkius.com to regenerate it if needed.

11

Tools not showing in chat

Click the 🔌 icon at the bottom of the chat input. If it shows 0 tools, the server may still be connecting. wait a few seconds.