PayPerFax
REMOTE · FAX.PAYPERFAX.COM
Your AI assistant prepares the fax. You check it and pay in your browser. Pay per fax. No account.
Available components
Last scanned (18 hours ago)
Scores higher than 91% of remote servers
Reachable. Last reached 4 Nov 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 Security80
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one. See how to fix → View diagnostics → Partial
- 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 Usability61
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 1310 tokens (~436/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 Management97
- Stability observed for 29 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
- We read all 3 captured tool definition(s), and no name or description among them implies an irreversible operation.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
Capabilities100
- Implements a current MCP spec version (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.
- 4 Nov 26 0
- Stability: pass → 0.97 functional
- 3 Nov 26 0
- Stability: 0.97 → pass security
- 2 Nov 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.
- 31 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 87 to 90. That category is still filling its 30-day observation window: 26 days of observed history at the previous scan, 27 at this one. The score rises as the window fills, whether or not the server changes.
- 29 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 80 to 83. That category is still filling its 30-day observation window: 24 days of observed history at the previous scan, 25 at this one. The score rises as the window fills, whether or not the server changes.
- 27 Oct 26 +3
- HSTS header: fail → pass ▲ security
- Tool “get_fax_status” rewrote its description, which is the text the model reads security
- 26 Oct 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.
- 24 Oct 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.
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 4 Nov 2026 · Probed https://fax.payperfax.com/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=payperfax.com | CN=WE1,O=Google Trust Services,C=US | 15 Oct 2026 | 13 Jan 2027 | ECDSA 256 | ECDSA-SHA256 | 8a6381e08b0c160513e75d61fd76a1fd |
| SANs: payperfax.com, *.payperfax.com | ||||||
| CN=WE1,O=Google Trust Services,C=US (CA) | CN=GTS Root R4,O=Google Trust Services LLC,C=US | 13 Dec 2023 | 20 Feb 2029 | ECDSA 256 | ECDSA-SHA384 | 7ff31977972c224a76155d13b6d685e3 |
| CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) | CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE | 15 Nov 2023 | 28 Jan 2028 | ECDSA 384 | SHA256-RSA | 7fe530bf331343bedd821610493d8a1b |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of fax.payperfax.com. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| com. | present | 19718 | 13 | Verified |
| payperfax.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 |
| x-content-type-options | nosniff |
| x-frame-options | SAMEORIGIN |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://fax.payperfax.com/mcp | Verified | 200 | |
| http (plaintext) | http://fax.payperfax.com/mcp | HTTPS enforced | 301 | https://fax.payperfax.com/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 →
create_fax Create a fax ~913
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: 1. Email: ask the person for their email address. Do not guess it. The confirmation and the receipt go there. 2. 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. 3. 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. 4. 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. 5. 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. 6. 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 7. 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.
| Name | Type | Req | Description |
|---|---|---|---|
| country | string | – | The person's country as a two-letter code (ISO 3166-1 alpha-2), for example US, DE, GB or JP. It sets the currency of the price, and the date format on the cover page and in the emails. Without it, t… |
| cover_message | string | – | A short note on the cover page, as plain text, at most 5000 characters. Only with cover_page. |
| cover_page | boolean | – | true to put a cover page before the document. The default is no cover page. |
| string | – | The person's email address, for the confirmation and the receipt. Ask the person; do not guess. Required when you send markdown or a cover page. | |
| file_expected | boolean | – | true when the person must still add a file (a PDF, a scan, a signed form). Then the link opens a form with what you sent, and the person adds the file there. |
| language | string | – | The language of the pages that the person sees, and of the emails. The default is en. |
| markdown | string | – | The document as Markdown text that you wrote, for example a letter. Leave it out when the person has the document as a file. |
| recipient_company | string | – | The recipient's company or agency on the cover page. Only with cover_page. At most 100 characters. |
| recipient_name | string | – | The recipient's name on the cover page. Only with cover_page. At most 100 characters. |
| sender_name | string | – | The sender's name on the cover page. Only with cover_page. At most 100 characters. |
| show_sender_email | boolean | – | true to show the person's email address on the cover page, so the recipient can reply. Only with cover_page. |
| timezone | string | – | The person's time zone as an IANA name, for example America/New_York. Without it, times are shown in UTC. |
| to | string | yes | The fax number in international format: "+", the country code, the number. Example: +14155550101. |
No output schema declared.
No examples provided.
get_fax_status Get the status of a fax ~244
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.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | The id of the fax, or an address of the fax: its status address (https://.../api/fax/{id}/status), or the address of its preview, payment or confirmation page. |
No output schema declared.
No examples provided.
list_supported_formats List the supported formats ~58
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.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
How do I install the PayPerFax MCP server?
PayPerFax is a hosted endpoint at https://fax.payperfax.com/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 · fax.payperfax.com
claude mcp add --transport http com-payperfax-fax 'https://fax.payperfax.com/mcp'
What is the PayPerFax MCP server?
PayPerFax is an MCP server listed in the public MCP registry as com.payperfax/fax. Your AI assistant prepares the fax. You check it and pay in your browser. Pay per fax. No account. This page covers its hosted endpoint (https://fax.payperfax.com/mcp).
Is the PayPerFax MCP server safe to use?
PayPerFax scores 85 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 PayPerFax MCP server expose?
PayPerFax exposes 3 tools: create_fax, get_fax_status, list_supported_formats. Their descriptions and schemas cost roughly 1,215 tokens of context every time the server is loaded.
Does the PayPerFax MCP server require authentication?
No. We connected to PayPerFax without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the PayPerFax MCP server still maintained?
PayPerFax is still listed as active in the MCP registry. We last reached this channel on 4 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.