# PayPerFax (remote · fax.payperfax.com)

Your AI assistant prepares the fax. You check it and pay in your browser. Pay per fax. No account.

- Trust score: 85/100 (high trust)
- Change this week: +3
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-04

## Components

- remote · `fax.payperfax.com`: 85/100 (this document), [markdown](https://verifymcp.io/servers/com-payperfax-fax/fax.md), [page](https://verifymcp.io/servers/com-payperfax-fax/fax)

## Channel facts

- Endpoint: `https://fax.payperfax.com/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `1.0.3`

## Trust breakdown

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. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-11-04.

- **Endpoint Security**: 80/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one.
  - HTTPS is enforced; there's no plaintext access path.
  - The HSTS (Strict-Transport-Security) header is present.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 61/100
  - AI-judged instruction clarity (excellent).
  - 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.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 97/100
  - Stability observed for 29 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 3 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 4 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a current MCP spec version (2026-07-28).

## Install

### 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.

### Claude

```bash
claude mcp add --transport http com-payperfax-fax 'https://fax.payperfax.com/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "com-payperfax-fax": {
      "url": "https://fax.payperfax.com/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "com-payperfax-fax": {
      "type": "http",
      "url": "https://fax.payperfax.com/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.com-payperfax-fax]
url = "https://fax.payperfax.com/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "com-payperfax-fax": {
      "type": "remote",
      "url": "https://fax.payperfax.com/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add com-payperfax-fax --url 'https://fax.payperfax.com/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  com-payperfax-fax:
    url: "https://fax.payperfax.com/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "com-payperfax-fax": {
      "Transport": "http",
      "Url": "https://fax.payperfax.com/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add com-payperfax-fax -t streamable-http -u 'https://fax.payperfax.com/mcp'
```

### Other

```json
{
  "mcpServers": {
    "com-payperfax-fax": {
      "type": "http",
      "url": "https://fax.payperfax.com/mcp"
    }
  }
}
```

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-11-04 (score 85, 0)

- [functional] Stability: pass → 0.97

### 2026-11-03 (score 85, 0)

- [security] Stability: 0.97 → pass

### 2026-11-02 (score 85, +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.

### 2026-10-31 (score 84, +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.

### 2026-10-29 (score 83, +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.

### 2026-10-27 (score 82, +3)

- [security improvement] HSTS header: fail → pass
- [security] Tool “get_fax_status” rewrote its description, which is the text the model reads

### 2026-10-26 (score 79, +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.

### 2026-10-24 (score 78, +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.

## MCP tools (3)

### `create_fax` (~913 tokens)

Create a fax

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.

Input parameters:

- `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.
- `email` (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, required): The fax number in international format: "+", the country code, the number. Example: +14155550101.

### `get_fax_status` (~244 tokens)

Get the status of a fax

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.

Input parameters:

- `id` (string, required): 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.

### `list_supported_formats` (~58 tokens)

List the supported formats

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.

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/com-payperfax-fax/fax#diagnostics

## Score history

- 2026-11-04: 85
- 2026-11-03: 85
- 2026-11-02: 85
- 2026-11-01: 84
- 2026-10-31: 84
- 2026-10-30: 83
- 2026-10-29: 83
- 2026-10-28: 82
- 2026-10-27: 82
- 2026-10-26: 79
- 2026-10-25: 78
- 2026-10-24: 78
- 2026-10-23: 77
- 2026-10-22: 77
- 2026-10-21: 76
- 2026-10-20: 76
- 2026-10-19: 75
- 2026-10-18: 75
- 2026-10-17: 74
- 2026-10-16: 74
- 2026-10-15: 74
- 2026-10-14: 73
- 2026-10-13: 73
- 2026-10-12: 72
- 2026-10-10: 71
- 2026-10-07: 70
- 2026-10-06: 69
- 2026-10-04: 68

## Common questions

### 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.

## Links

- Remote endpoint: https://fax.payperfax.com/mcp
- Repository: https://github.com/payperfax/fax-mcp
- Website: https://payperfax.com/fax-mcp/
- Changelog RSS feed: https://verifymcp.io/servers/com-payperfax-fax/fax.xml
- Changelog JSON feed: https://verifymcp.io/servers/com-payperfax-fax/fax.json
- HTML version of this page: https://verifymcp.io/servers/com-payperfax-fax/fax