SendaFax
REMOTE · SENDAFAX.AI
Send a fax in Australia (+61). Pay only if it delivers. Email receipt. No card at send.
Available components
Last scanned (6 hours ago)
Scores higher than 68% of remote servers
Reachable. Last reached 25 Oct 2026.
Category Communication
Recent critical change
Authorization (4 Sept 2026). See the changelog before you install this server.
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. How we score → Why this is hard to score →
Endpoint Security63
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation check failed: no authorisation is required to call this server, and it exposes a tool marked destructive (send_fax). See how to fix → View diagnostics → Fail
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability62
- AI-judged instruction clarity (good).Pass
- 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. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management100
- No destabilizing schema changes in the last 30 days.Pass
Tool Coverage93
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 80% of tool parameters carry a description.Partial
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- All 1 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation.Pass
- An AI judge read all 4 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities40
- Spec-recency check failed: implements MCP spec 2025-03-26; the latest is 2026-07-28. See how to fix → Fail
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 4 Oct 26 0
- Stability: 0.97 → pass security
- 3 Oct 26 +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.
- 30 Sept 26 +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.
- 28 Sept 26 +1
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 26 Sept 26 +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.
- 25 Sept 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 24 Sept 26 +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.
- 22 Sept 26 +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.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 25 Oct 2026 · Probed https://sendafax.ai/api/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=sendafax.ai | CN=YR1,O=Let's Encrypt,C=US | 29 Aug 2026 | 27 Nov 2026 | RSA 2048 | SHA256-RSA | 5727d8b431d111f4827578660b0c58ff07e |
| SANs: sendafax.ai | ||||||
| CN=YR1,O=Let's Encrypt,C=US (CA) | CN=Root YR,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | RSA 2048 | SHA256-RSA | a20253f15f2691c05dc1ce13b9bcca4e |
| CN=Root YR,O=ISRG,C=US (CA) | CN=ISRG Root X1,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | RSA 4096 | SHA256-RSA | f24b6d17f9d9ad7cb1c9fea78782699f |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of sendafax.ai. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| ai. | present | 3799 | 8 | Verified |
| sendafax.ai. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
| Header | Value |
|---|---|
| strict-transport-security | max-age=63072000 |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://sendafax.ai/api/mcp | Verified | 200 | |
| http (plaintext) | http://sendafax.ai/api/mcp | HTTPS enforced | 308 | https://sendafax.ai/api/mcp |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
get_coverage Check fax coverage ~114
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.
| Name | Type | Req | Description |
|---|---|---|---|
| destination | string | yes | Required fax number or country prefix. Used only to infer destCountry. No default. |
No output schema declared.
No examples provided.
get_fax_status Get fax status ~83
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.
| Name | Type | Req | Description |
|---|---|---|---|
| fax_id | string | yes | SendaFax job id returned by send_fax. |
No output schema declared.
No examples provided.
send_fax Send a fax ~461
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.
| Name | Type | Req | Description |
|---|---|---|---|
| body | string | – | Plain-text fax body. Required unless document_base64 is sent. Use document_base64 for a PDF. |
| content_type | string | – | – |
| destination | string | yes | 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… |
No output schema declared.
No examples provided.
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.
remote · sendafax.ai
claude mcp add --transport http ai-sendafax-sendafax 'https://sendafax.ai/api/mcp'
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.