Faxer — Send Faxes

me.faxerPublished by faxer.meOfficial publisherv1.0.0Updated Oct 24, 2026

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

VerifiedStreamable HTTPWeb executableCommunication & CollaborationBusiness & Commerce

Overview

AI-generated overview

A remote MCP server that lets an assistant quote, pay for, send and track real faxes to US, Canadian and international fax numbers.

What you can do
Get an exact price quote for faxing a PDF document or cover text to a given fax number, including international numbers, before sending anything. Create a Stripe Checkout payment link so a human can pay in their browser, returning a payment ID to use afterwards. Send the fax using either the human-paid payment ID or an autonomous machine payment challenge. Check delivery status, where success means the receiving fax machine confirmed the transmission.
When to use it
Use it when someone wants to send a real fax to a business, office or institution that still accepts faxes, and is willing to pay per fax. Useful for agents that need to transmit a publicly hosted PDF plus a short cover note and then confirm delivery.
Requirements
A remote endpoint at faxer.me over streamable HTTP; no account, API key, environment variable or header is declared. The document to fax must be a publicly downloadable PDF, and the human needs a browser to complete Stripe Checkout payment.
Before you install
Sending a fax costs money: $1 plus $0.25 per page, and the price is computed server-side. The fax is actually transmitted to a third-party fax number, so the document and cover text leave your control. Autonomous machine payment (x402/MPP) can spend funds without a human confirming each payment. The document must be publicly downloadable, so anyone with the link could reach it.

Installation

In SourceWeft

  1. Open Faxer — Send Faxes in the dashboard and add it to a workspace.
  2. 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/me.faxer%2Ffaxer/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.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config.

{
  "mcpServers": {
    "faxer-send-faxes": {
      "type": "http",
      "url": "https://faxer.me/mcp"
    }
  }
}

Tools

4

get_fax_quote

Get a fax price quote

Get the exact price to send a real fax to any US, Canadian, or international fax number via faxer.me. Call this first whenever a user wants to send, transmit, or fax a document or message. Provide document_url (a publicly downloadable PDF), cover_text (plain text that will be rendered onto fax pages), or pages (an estimated page count). Pricing is pay-per-fax ($1.00 first page + $0.25/page, returned in USD cents); no account or API key needed.

Parameterspagescover_textdocument_url

create_fax_payment

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. The Checkout link expires (see expires_at, ~24h); create a fresh one if the human delays.

Parameterstorequiredpagescover_textdocument_url

send_fax

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 and Stripe machine payments are refunded automatically if the fax fails to send or deliver (on-chain payments are refunded manually).

Parameterstorequiredcover_textpayment_iddocument_urlcover_subject

get_fax_status

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. Delivery typically takes 1-5 minutes; poll roughly every 30 seconds.

Parametersfax_idrequired

Version history

1
  1. v1.0.0LatestSep 16, 2026

Score

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.