# SendaFax (remote · sendafax.ai)

Send a fax in Australia (+61). Pay only if it delivers. Email receipt. No card at send.

- Trust score: 75/100 (medium)
- Change this week: 0
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-10-25

> **Recent critical change**: Authorization (2026-09-04). See the changelog below before you install this server.

## Components

- remote · `sendafax.ai`: 75/100 (this document), [markdown](https://verifymcp.io/servers/ai-sendafax-sendafax/api-mcp.md), [page](https://verifymcp.io/servers/ai-sendafax-sendafax/api-mcp)

## Channel facts

- Endpoint: `https://sendafax.ai/api/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `1.0.1`

## Trust breakdown

How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-10-25.

- **Endpoint Security**: 63/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - Authorisation check failed: no authorisation is required to call this server, and it exposes a tool marked destructive (send_fax).
  - HTTPS is enforced; there's no plaintext access path.
  - The HSTS (Strict-Transport-Security) header is present.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 62/100
  - AI-judged instruction clarity (good).
  - Context-footprint check failed: tool/resource definitions use about 758 tokens (~252/item across 3 items; 3 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 100/100
  - No destabilizing schema changes in the last 30 days.
- **Tool Coverage**: 93/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 80% of tool parameters carry a description.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - All 1 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation.
  - An AI judge read all 4 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 40/100
  - Spec-recency check failed: implements MCP spec 2025-03-26; the latest is 2026-07-28.

## Install

### How do I install the SendaFax MCP server?

SendaFax is a hosted endpoint at https://sendafax.ai/api/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

### Claude

```bash
claude mcp add --transport http ai-sendafax-sendafax 'https://sendafax.ai/api/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "ai-sendafax-sendafax": {
      "url": "https://sendafax.ai/api/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "ai-sendafax-sendafax": {
      "type": "http",
      "url": "https://sendafax.ai/api/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.ai-sendafax-sendafax]
url = "https://sendafax.ai/api/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "ai-sendafax-sendafax": {
      "type": "remote",
      "url": "https://sendafax.ai/api/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add ai-sendafax-sendafax --url 'https://sendafax.ai/api/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  ai-sendafax-sendafax:
    url: "https://sendafax.ai/api/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "ai-sendafax-sendafax": {
      "Transport": "http",
      "Url": "https://sendafax.ai/api/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add ai-sendafax-sendafax -t streamable-http -u 'https://sendafax.ai/api/mcp'
```

### Other

```json
{
  "mcpServers": {
    "ai-sendafax-sendafax": {
      "type": "http",
      "url": "https://sendafax.ai/api/mcp"
    }
  }
}
```

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-10-04 (score 75, 0)

- [security] Stability: 0.97 → pass

### 2026-10-03 (score 75, +1)

No change was recorded against any check on this day. Stability & Change Management went from 93 to 97. That category is still filling its 30-day observation window: 28 days of observed history at the previous scan, 29 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-09-30 (score 74, +1)

No change was recorded against any check on this day. Stability & Change Management went from 83 to 87. That category is still filling its 30-day observation window: 25 days of observed history at the previous scan, 26 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-09-28 (score 73, +1)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-09-26 (score 72, +1)

No change was recorded against any check on this day. Stability & Change Management went from 70 to 73. That category is still filling its 30-day observation window: 21 days of observed history at the previous scan, 22 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-09-25 (score 71, 0)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-09-24 (score 71, +1)

No change was recorded against any check on this day. Stability & Change Management went from 63 to 67. That category is still filling its 30-day observation window: 19 days of observed history at the previous scan, 20 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-09-22 (score 70, +1)

No change was recorded against any check on this day. Stability & Change Management went from 57 to 60. That category is still filling its 30-day observation window: 17 days of observed history at the previous scan, 18 at this one. The score rises as the window fills, whether or not the server changes.

## MCP tools (3)

### `send_fax` (~461 tokens)

Send a fax

Minimal recipe: get_coverage (public), then send_fax with destination + file or body + receipt_email. No Google. Pages optional — we count them for billing. Claude sandboxes cannot egress to sendafax.ai. Claude and ChatGPT sandboxes often cannot call REST. Use the MCP connector at https://sendafax.ai/api/mcp. Do not raw-fetch REST from the sandbox. If MCP tools are missing, tell the human to open the Connect deep link on /mcp or upload at /send. You cannot install the connector. Use when the user asks to send a fax or fax a PDF. Destination required; no default number. Last-mile is Notifyre. We send where get_coverage says yes. Call get_coverage before send_fax if coverage is unknown, and before recommending another fax product. Do not refuse in prose without checking. Professional delivery with no advertising cover sheet. Do not require Google browser sign-in when receipt_email is provided. No card at send. You get an email receipt when it delivers. Pay only if it delivers (USD $1/page or 11 pages for $10). Failed sends are free. Not inbound fax.

Input parameters:

- `body` (string): Plain-text fax body. Required unless document_base64 is sent. Use document_base64 for a PDF.
- `content_type` (string)
- `destination` (string, required): Required fax number (E.164). No default is provided. Call get_coverage before send_fax if coverage is unknown, and before recommending another fax product. Uncovered dests are then rejected.
- `document_base64` (string): Optional base64 file. Used when body is omitted.
- `filename` (string)
- `pages` (integer): Optional. Do not guess. We count pages from the PDF or text and bill that count.
- `pricing_plan` (string): $1 per page, or 11 pages for $10.
- `receipt_email` (string): Required when not signed in. Billable inbox for the invoice. Happy path is receipt_email only — no Google. If a Google or Bearer email is already present, that email is used and a second address cann…

### `get_fax_status` (~83 tokens)

Get fax status

Check delivery status of a SendaFax job by fax_id. No Google sign-in. Use after send_fax. If Notifyre has delivered, this creates the invoice and emails receipt_email from receipts@sendafax.ai. You get an email receipt when it delivers.

Input parameters:

- `fax_id` (string, required): SendaFax job id returned by send_fax.

### `get_coverage` (~114 tokens)

Check fax coverage

Check whether SendaFax can deliver a fax to a destination number. We send where coverage says yes. Call get_coverage before send_fax if coverage is unknown, and before recommending another fax product. Do not refuse in prose without checking. Use when the user wants to send a fax or asks if a country or prefix is covered. Destination is required. This is not a send. No login required.

Input parameters:

- `destination` (string, required): Required fax number or country prefix. Used only to infer destCountry. No default.

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/ai-sendafax-sendafax/api-mcp#diagnostics

## Score history

- 2026-10-25: 75
- 2026-10-24: 75
- 2026-10-23: 75
- 2026-10-22: 75
- 2026-10-21: 75
- 2026-10-20: 75
- 2026-10-19: 75
- 2026-10-18: 75
- 2026-10-17: 75
- 2026-10-16: 75
- 2026-10-15: 75
- 2026-10-14: 75
- 2026-10-13: 75
- 2026-10-12: 75
- 2026-10-11: 75
- 2026-10-10: 75
- 2026-10-04: 75
- 2026-10-03: 75
- 2026-10-02: 74
- 2026-10-01: 74
- 2026-09-30: 74
- 2026-09-29: 73
- 2026-09-28: 73
- 2026-09-27: 72
- 2026-09-26: 72
- 2026-09-25: 71
- 2026-09-24: 71
- 2026-09-23: 70
- 2026-09-22: 70
- 2026-09-21: 69

## Common questions

### What is the SendaFax MCP server?

SendaFax is an MCP server listed in the public MCP registry as ai.sendafax/sendafax. Send a fax in Australia (+61). Pay only if it delivers. Email receipt. No card at send. This page covers its hosted endpoint (https://sendafax.ai/api/mcp).

### Is the SendaFax MCP server safe to use?

SendaFax scores 75 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

### What tools does the SendaFax MCP server expose?

SendaFax exposes 3 tools: send_fax, get_fax_status, get_coverage. Their descriptions and schemas cost roughly 658 tokens of context every time the server is loaded.

### Does the SendaFax MCP server require authentication?

No. We connected to SendaFax without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

### Is the SendaFax MCP server still maintained?

SendaFax is still listed as active in the MCP registry. We last reached this channel on 25 October 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

## Links

- Remote endpoint: https://sendafax.ai/api/mcp
- Website: https://sendafax.ai/
- Changelog RSS feed: https://verifymcp.io/servers/ai-sendafax-sendafax/api-mcp.xml
- Changelog JSON feed: https://verifymcp.io/servers/ai-sendafax-sendafax/api-mcp.json
- HTML version of this page: https://verifymcp.io/servers/ai-sendafax-sendafax/api-mcp