Remote MCP server that lets an assistant price, send and track real faxes to EU institutions, paid per fax or from prepaid credit.
What you can do
Get a price quote in euro cents for a fax, including page and VAT rules
Submit an uploaded PDF for faxing, after uploading it over plain HTTP multipart
Poll a fax's status through its lifecycle from draft to delivered or failed
Check the prepaid credit balance of the API key used for the connection
When to use it
Useful when you need to send a document by fax, for example to EU institutions, and want the assistant to quote the cost, submit the PDF and follow delivery status without leaving the conversation.
Requirements
A remote MCP endpoint over streamable HTTP; no local package. Sending requires a PDF uploaded first via a separate HTTP multipart request to the service's upload endpoint. An optional bearer API key in the Authorization header enables prepaid autonomous sending; without it, sending goes through pay-per-fax checkout links. Network access to the service is required.
Before you install
Sending a fax costs money: 5.00 EUR for up to 5 pages plus 0.50 EUR per extra page, plus VAT depending on the payer's billing country. The optional Authorization header carries a prepaid API key that can spend credit. Faxes are real outbound transmissions to third parties and cannot be recalled once sent; check the uploaded PDF and recipient before submitting. Payment status moves through checkout, so a fax may stay pending until paid.
Enable the server for the chats that should use its tools.
Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.
Use with an agent
Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.
Read https://sourceweft.com/mcp/com.sendthisfax%2Ffax/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.
Get the price quote in euro cents for sending a fax. Pricing: 5.00 EUR for up to 5 pages, plus 0.50 EUR per extra page, plus VAT based on the payer's billing country (0% VAT outside the EU).
Submit an uploaded PDF for faxing.
Step 1 (before this tool): upload the PDF over plain HTTP multipart, using any HTTP client you have — shell, JavaScript fetch with FormData, Python, etc.:
curl -F "[email protected]" https://www.sendthisfax.com/api/upload
fetch("https://www.sendthisfax.com/api/upload", {method: "POST", body: formDataWithFile})
The response contains fax_public_id and page_count. PDFs must be unencrypted, at most 50 MB and 1000 pages.
Step 2: call this tool with the fax_public_id and the recipient fax number.
Two modes:
- With an API key (Authorization: Bearer stf_live_... on this MCP connection): the fax price is debited from the prepaid credit balance and sending starts immediately — no checkout, no browser. sender_email and billing_country are optional (they default to the key's records). Buy credits at https://www.sendthisfax.com/en/credits.
- Without an API key: sender_email and billing_country are REQUIRED and the tool returns a checkout_url the USER must pay in a browser; the fax is sent automatically once paid.
In both modes, poll get_fax_status until status reaches "delivered" or "failed" (failures after payment are auto-refunded).
For integration testing, +19898989898 is the designated test recipient number.
Get the current status of a fax. Poll this after send_fax until a terminal state.
Fax lifecycle: draft (uploaded, not submitted) -> pending (submitted, awaiting payment) -> sending -> delivered | failed.
Payment lifecycle: unpaid -> verifying/open (checkout in progress) -> paid | failed | canceled | expired.
A fax that fails after payment is refunded automatically to the payer.
Parametersfax_idrequired
check_balance
Check credit balance
Get the prepaid credit balance of the API key used to authenticate this MCP connection. Requires a bearer API key (stf_live_...). Buy or top up credits at https://www.sendthisfax.com/en/credits — credits never expire and failed faxes are re-credited automatically.
Takes no parameters.
Version history
1
v1.0.0LatestSep 16, 2026
Score
72%
72% of the applicable checks met
How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.
Reached in the last 30 daysRequired25 pts
Auth declaredRequired10 pts
Tools listedRequired15 pts
DescriptionRequired15 pts
Logo10 pts
Publish an icon in the registry entry.
Documentation15 pts
Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.
LicenseNot applicable
A hosted service is used under its provider's terms, so no license is expected here. This check is left out of the percentage.