# Faxer — Send Faxes (remote · faxer.me)

Send real faxes from AI assistants. Pay per fax ($1 + $0.25/page), no account or API key.

- Trust score: 71/100 (medium)
- Change this week: +5
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-08-17

## Components

- remote · `faxer.me`: 71/100 (this document), [markdown](https://verifymcp.io/servers/me-faxer-faxer/faxer.md), [page](https://verifymcp.io/servers/me-faxer-faxer/faxer)

## Channel facts

- Endpoint: `https://faxer.me/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `1.0.0`

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

- **Endpoint Security**: 63/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - Authorisation not fully verified: no authorisation is required to call this server, and 2 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe.
  - 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**: 73/100
  - AI-judged instruction clarity (excellent).
  - Context-footprint check failed: tool/resource definitions use about 891 tokens (~222/item across 4 items; 4 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 40/100
  - Stability observed for 12 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.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

## Install

### Claude

```bash
claude mcp add --transport http me-faxer-faxer https://faxer.me/mcp
```

### Codex

```toml
[mcp_servers.me-faxer-faxer]
url = "https://faxer.me/mcp"
```

### opencode

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

### OpenClaw

```bash
openclaw mcp add me-faxer-faxer --url https://faxer.me/mcp --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  me-faxer-faxer:
    url: "https://faxer.me/mcp"
```

### Other

```json
{
  "mcpServers": {
    "me-faxer-faxer": {
      "type": "http",
      "url": "https://faxer.me/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-08-17 (score 71, +1)

No change was recorded against any check on this day. Stability & Change Management went from 37 to 40. That category is still filling its 30-day observation window: 11 days of observed history at the previous scan, 12 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-08-15 (score 70, +1)

No change was recorded against any check on this day. Stability & Change Management went from 30 to 33. That category is still filling its 30-day observation window: 9 days of observed history at the previous scan, 10 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-08-13 (score 69, +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.

### 2026-08-11 (score 68, +2)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-08-09 (score 66, +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.

### 2026-08-07 (score 65, +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.

### 2026-08-06 (score 64, 0)

- [functional improvement] Stability: unverified → 0.03

### 2026-08-05 (score 64)

First indexed and scored.

## MCP tools (4)

### `get_fax_quote` (~141 tokens)

Get a fax price quote

Get the exact price (USD cents) to send a fax via faxer.me. Provide document_url (a publicly downloadable PDF), cover_text (plain text that will be rendered onto fax pages), or pages (an estimated page count). No account needed; pricing is pay-per-fax.

Input parameters:

- `cover_text` (string): Plain text to fax instead of a document (rendered as PDF pages, ~3000 chars/page).
- `document_url` (string): Public http(s) URL of the PDF to fax. The server downloads it and counts real pages.
- `pages` (integer): Estimated page count, if you only need a rough quote.

### `create_fax_payment` (~166 tokens)

Create a fax payment link

Create a Stripe Checkout payment link for a fax. Returns payment_url — give this link to the human so they can pay in their browser (agents never handle card details) — and payment_id, which you pass to send_fax after the human has paid. The price is computed server-side from the document or text.

Input parameters:

- `cover_text` (string): Plain text to fax instead of a document.
- `document_url` (string): Public http(s) URL of the PDF to fax (same one you will pass to send_fax).
- `pages` (integer): Page count, if pricing without the document. send_fax re-verifies against the real content.
- `to` (string, required): Recipient fax number in international format, e.g. +15551234567.

### `send_fax` (~260 tokens)

Send the fax

Transmit a fax. Two ways to pay: (1) human-in-the-loop — pass the payment_id from create_fax_payment after the human has paid the Stripe Checkout link; (2) autonomous machine payment (x402/MPP) — call WITHOUT payment_id and the server replies with a payment challenge (JSON-RPC error -32042) for USDC-on-Tempo or a Stripe Shared Payment Token; pay it and retry with the credential in _meta['org.paymentauth/credential']. Either way the server verifies the payment covers the server-computed price of the actual content before sending via a real fax carrier. One fax per payment; card/Checkout payments are refunded automatically if transmission fails.

Input parameters:

- `cover_subject` (string): Optional heading for a cover_text fax.
- `cover_text` (string): Plain text to fax instead of a document.
- `document_url` (string): Public http(s) URL of the PDF to fax.
- `payment_id` (string): The payment_id from create_fax_payment (Stripe Checkout Session id). Omit to pay autonomously via an x402/MPP machine-payment challenge instead.
- `to` (string, required): Recipient fax number in international format, e.g. +15551234567.

### `get_fax_status` (~75 tokens)

Check fax delivery status

Check the delivery status of a fax sent with send_fax. Status 'success' means the receiving fax machine confirmed the transmission; 'inprogress'/'queued' mean it is still sending; 'failure' means it could not be delivered.

Input parameters:

- `fax_id` (string, required): The fax_id returned by send_fax.

## Diagnostics

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

## Score history

- 2026-08-17: 71
- 2026-08-16: 70
- 2026-08-15: 70
- 2026-08-14: 69
- 2026-08-13: 69
- 2026-08-12: 68
- 2026-08-11: 68
- 2026-08-10: 66
- 2026-08-09: 66
- 2026-08-08: 65
- 2026-08-07: 65
- 2026-08-06: 64
- 2026-08-05: 64

## Links

- Remote endpoint: https://faxer.me/mcp
- Website: https://faxer.me/mcp
- Changelog RSS feed: https://verifymcp.io/servers/me-faxer-faxer/faxer.xml
- Changelog JSON feed: https://verifymcp.io/servers/me-faxer-faxer/faxer.json
- HTML version of this page: https://verifymcp.io/servers/me-faxer-faxer/faxer