SendFaxFast (AI Fax Credits)
REMOTE · SENDFAXFAST.COM
Send faxes from AI chat with prepaid credits (1 credit = 1 fax, up to 100 pages). PDF, JPG, PNG.
Available components
Last scanned (17 hours ago)
Scores higher than 47% of remote servers
Reachable. Last reached 18 Oct 2026.
Category Documents and Files
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 Security51
- 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 enforcement could not be verified: the plaintext port answered with HTTP 405, which proves neither a plaintext path nor enforcement. View diagnostics → Unverified
- 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 Usability70
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 905 tokens (~181/item across 5 items; 5 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 Management27
- Stability observed for 8 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
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 6 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
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.
- 18 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 23 to 27. That category is still filling its 30-day observation window: 7 days of observed history at the previous scan, 8 at this one. The score rises as the window fills, whether or not the server changes.
- 16 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 17 to 20. That category is still filling its 30-day observation window: 5 days of observed history at the previous scan, 6 at this one. The score rises as the window fills, whether or not the server changes.
- 14 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 10 to 13. That category is still filling its 30-day observation window: 3 days of observed history at the previous scan, 4 at this one. The score rises as the window fills, whether or not the server changes.
- 12 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 3 to 7. That category is still filling its 30-day observation window: 1 days of observed history at the previous scan, 2 at this one. The score rises as the window fills, whether or not the server changes.
- 11 Oct 26 0
- Stability: unverified → 0.03 ▲ functional
- 10 Oct 26 61
First indexed and scored.
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 18 Oct 2026 · Probed https://sendfaxfast.com/api/mcp-credits.php
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=sendfaxfast.com | CN=YE2,O=Let's Encrypt,C=US | 3 Oct 2026 | 1 Jan 2027 | ECDSA 256 | ECDSA-SHA384 | 545625da89e8fb9be6c878bba3e23f6b703 |
| SANs: sendfaxfast.com, www.sendfaxfast.com | ||||||
| CN=YE2,O=Let's Encrypt,C=US (CA) | CN=Root YE,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | ECDSA 384 | ECDSA-SHA384 | 4df3b15dd6c0784c507cd37b58e6f115 |
| CN=Root YE,O=ISRG,C=US (CA) | CN=ISRG Root X2,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | ECDSA-SHA384 | 872165fc34b6e5fba8add5b3705fb53a |
| CN=ISRG Root X2,O=Internet Security Research Group,C=US (CA) | CN=ISRG Root X1,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | SHA256-RSA | 6c8f1dc727c7117f7baf853ac980f9cd |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of sendfaxfast.com. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| com. | present | 19718 | 13 | Verified |
| sendfaxfast.com. | 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=31536000; includeSubDomains; preload |
| x-content-type-options | nosniff |
| x-frame-options | SAMEORIGIN |
| referrer-policy | strict-origin-when-cross-origin |
| permissions-policy | geolocation=(), microphone=(), camera=() |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://sendfaxfast.com/api/mcp-credits.php | Verified | 200 | |
| http (plaintext) | http://sendfaxfast.com/api/mcp-credits.php | Inconclusive | 405 |
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 →
create_upload_link Create upload link ~108
Creates a secure one-time upload link (valid 30 minutes) for the fax document (PDF, JPG or PNG, max. 10 MB) – upload from phone or computer by drag & drop, file picker or camera. For files on the user's device, or chat attachments that are not available as send_fax's "file" parameter. The user opens upload_url and uploads the file; send_fax then accepts the returned upload_id. Creating a link sends nothing and costs nothing.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
get_account_balance Get credit balance ~30
Check how many fax credits remain on your account. Requires your credits API key (sfx_...).
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
get_fax_price Check fax price ~117
Check if a fax destination is supported and how many credits it costs (a flat 1 credit per fax, up to 100 pages). No API key required. Supported: USA, Canada, Australia, New Zealand and 39 more countries (same list as sendfaxfast.com); premium-rate numbers are not supported.
| Name | Type | Req | Description |
|---|---|---|---|
| fax_number | string | yes | Recipient fax number in E.164 format (e.g. +12125550100 for USA, +61212345678 for Australia, +911123456789 for India) |
No output schema declared.
No examples provided.
get_fax_status Get fax status ~60
Check the delivery status of one of your faxes. Use the fax_id returned by send_fax. Requires your credits API key; only your own faxes are visible.
| Name | Type | Req | Description |
|---|---|---|---|
| fax_id | integer | yes | Fax ID returned by send_fax |
No output schema declared.
No examples provided.
send_fax Send fax (uses 1 credit) ~386
Send a fax using 1 prepaid credit. Requires your credits API key (sfx_...) and a direct, publicly accessible HTTPS link to a PDF (max. 10 MB, 100 pages). Supported: USA, Canada, Australia, New Zealand and 39 more countries (same list as sendfaxfast.com); premium-rate numbers are not supported. Each call transmits a real fax to the given number. DOCUMENT (exactly one): "upload_id" from create_upload_link (for files on the user's device), "file" (a file attached in ChatGPT, filled in automatically), "document_url" (direct public HTTPS link to a PDF) or "document_base64" (tiny files only, max. 700 KB). For an attachment that is not available as "file", create_upload_link provides an upload link. The result states whether the fax was sent, scheduled or is awaiting payment.
| Name | Type | Req | Description |
|---|---|---|---|
| document_base64 | string | – | Only for very small files (max. 700 KB): the PDF, JPG or PNG as base64 or data: URI. Prefer create_upload_link. |
| document_name | string | – | Optional: original file name of the document (e.g. "invoice.pdf"), shown on the transmission report. Not needed with upload_id or file. |
| document_url | string | – | Direct, publicly accessible HTTPS URL of the PDF document to fax (no login or preview pages) Alternative to upload_id / file. |
| fax_number | string | yes | Recipient fax number in E.164 format (e.g. +12125550100) |
| file | object | – | ChatGPT: the fax document the user attached in the chat (PDF, JPG or PNG). Filled in automatically by ChatGPT. |
| upload_id | string | – | upload_id returned by create_upload_link (after the user uploaded the file). One-time use. |
No output schema declared.
No examples provided.
How do I install the SendFaxFast (AI Fax Credits) MCP server?
SendFaxFast (AI Fax Credits) is a hosted endpoint at https://sendfaxfast.com/api/mcp-credits.php, 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 · sendfaxfast.com
claude mcp add --transport http com-sendfaxfast-fax-credits 'https://sendfaxfast.com/api/mcp-credits.php'
What is the SendFaxFast (AI Fax Credits) MCP server?
SendFaxFast (AI Fax Credits) is an MCP server listed in the public MCP registry as com.sendfaxfast/fax-credits. Send faxes from AI chat with prepaid credits (1 credit = 1 fax, up to 100 pages). PDF, JPG, PNG. This page covers its hosted endpoint (https://sendfaxfast.com/api/mcp-credits.php).
Is the SendFaxFast (AI Fax Credits) MCP server safe to use?
SendFaxFast (AI Fax Credits) scores 65 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 SendFaxFast (AI Fax Credits) MCP server expose?
SendFaxFast (AI Fax Credits) exposes 5 tools: get_account_balance, get_fax_price, send_fax, get_fax_status, create_upload_link. Their descriptions and schemas cost roughly 701 tokens of context every time the server is loaded.
Does the SendFaxFast (AI Fax Credits) MCP server require authentication?
No. We connected to SendFaxFast (AI Fax Credits) without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the SendFaxFast (AI Fax Credits) MCP server still maintained?
SendFaxFast (AI Fax Credits) is still listed as active in the MCP registry. We last reached this channel on 18 October 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.