PayPerFax
Server Details
Your AI assistant prepares the fax. You check it and pay in your browser. Pay per fax. No account.
- Status
- Healthy
- Uptime
- 100.0% over the last 24 hours
- Last Tested
- Transport
- Streamable HTTP · MCP 2025-11-25
- URL
- Repository
- payperfax/fax-mcp
- GitHub Stars
- 0
- Server Listing
- PayPerFax
- ChatGPT
- –
- Claude
- PayPerFax
TDQS
Scored across 3 tools
Each tool targets a distinct action on a distinct resource: creating a fax, reading one fax's status, and listing static capability info. There is no plausible way to confuse them, and the descriptions reinforce the boundaries.
All three tools follow a consistent snake_case verb_noun pattern (create_fax, get_fax_status, list_supported_formats). The get_fax_status name is slightly longer but still follows the same convention.
Three tools is on the lean side but matches the deliberately narrow scope of a no-account pay-per-fax flow where payment happens in the browser. Nothing feels padded or obviously missing from the set.
The core lifecycle (create -> pay -> check status) plus a format/limits reference covers the domain well, including failure and expiry states. Minor gaps exist around cancellation, history listing, or resend, though the status tool notes a failed fax can simply be re-sent.
Publisher details
- Operator
- Ediblesites Ltd
- Operator website
- https://ediblesites.com
- Vendor relationship
- First-party
- Documentation
- https://payperfax.com/fax-mcp/
- Privacy policy
- Not provided
- Trust center
- https://payperfax.com/policy/
- Restrictions
- Unknown
Available Tools
3 toolscreate_faxCreate a faxAInspect
Prepare a fax for a person to send with PayPerFax, the pay-per-fax service: no account, no subscription, one payment for one fax. A common use is a letter or a form for the IRS, a doctor, a court, an insurer or a landlord.
The tool does not send the fax and does not charge. It returns a link for the person. The person opens the link, sees the preview and the price, and pays in the browser. Then the fax is sent.
Rules:
Email: ask the person for their email address. Do not guess it. The confirmation and the receipt go there.
A document that the person has as a file (a PDF, a scan, a signed form): do not retype it as text. A typed copy of a signed form is not the form. Set file_expected to true, and tell the person that they add the file on the page of the link.
The fax number of an agency or a company: take it from its official website (for the IRS: irs.gov), and show the person the source. A number from memory can send private papers to a stranger.
A letter that you write goes in markdown. With no cover page, the letter must have its own date, names and address block. With a cover page, keep cover_message short: a long message is cut off.
Limits: the markdown text can be at most 100 KB. Headings, lists, bold text and tables are printed. An image is printed as its alt text, a link as its text, and raw HTML as text.
If you can run shell commands and the document is a local file, send it with the HTTP call: curl -F "to=+14155550101" -F "email=person@example.com" -F "documents[]=@/path/to/file.pdf" https://fax.payperfax.com/api/fax
After the call, give the person the link, and say that nothing is sent and nothing is charged before they pay. The confirmation email comes after the payment. If the status of the fax is later "failed", the person is not charged, and can send the fax again.
Inputs: to (required), email, country, language, +9 more.
get_fax_statusGet the status of a faxARead-onlyInspect
Read where a fax is. Give the id from create_fax, or an address of the fax: the status address from the tracking prompt of the person, or the address of a page of the fax. "status" is pending, delivered, failed or expired. While it is pending, "stage" says more: rendering (we prepare the pages), awaiting_payment (the person did not pay yet; "pages" and "price" are given, and they can still change), sending (paid, on its way). delivered: the fax arrived. failed: the fax was not delivered, the person is not charged, and can send it again; with "render_failed", the document could not be prepared, and the person opens the link to change it. expired: the fax was not paid in time, or it is no longer available. Do not call this in a loop: read the status when the person asks.
Inputs: id (required).
list_supported_formatsList the supported formatsARead-onlyInspect
List what PayPerFax can fax, and the limits: the text that create_fax takes, the file types that a person can add on the form or that a shell can send to the HTTP call, the sizes, and the languages.
Inputs: no named parameters.
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
Related MCP Connectors
Send real faxes from AI assistants. Pay per fax ($1 + $0.25/page), no account or API key.
Send real faxes worldwide from your AI assistant. Prepaid, no subscription, PDF send report.
Send real faxes from AI chat (DE/AT + 40 countries). PDF, JPG, photo. Pay per fax via Stripe.
Send a one-off fax from inside ChatGPT or Claude. Pay-per-use, $2-$4.50 per delivered fax.
Related MCP Servers
AlicenseAqualityBmaintenanceEnables AI agents to prepare, preview, quote, and send approved faxes, track delivery and evidence, read inbound faxes, extract data, and request human approvals through a fax API.171,081 npmMIT- AlicenseNot gradedqualityDmaintenanceSend, receive, and verify faxes from AI assistants and agents via the Model Context Protocol.59 npmMIT
- AlicenseAqualityBmaintenanceEnables AI assistants to send real faxes through the FaxDrop API. Provides safeguards including rate limiting, dry-run mode, and audit logging for secure fax operations.395 npm5MIT
- AlicenseNot gradedqualityDmaintenanceEnables AI agents to send free and paid faxes to US and Canada numbers, check fax status, and purchase prepaid credits, all without leaving the chat.MIT
Glama MCP Gateway
Add one secure layer between your agents and this server.