Mmcp.market

Faxer — Send Faxes MCP server

by faxer.me·me.faxer/faxer·v1.0.0

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

C60/100grade C
What users say
No reviews yet
Be the first
Safety scan
C60/100

full report

Adoption
New

Little public usage data yet

Reviews

Write one

Nobody has reviewed Faxer — Send Faxes yet.

If you have run it, two minutes of your experience saves the next person an afternoon.

Faxer — Send Faxes tools (4, 2 write)

write = sends, deletes, buys or posts
  • create_fax_paymentwrite actionFree

    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.

  • get_fax_quoteFree

    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.

  • get_fax_statusFree

    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.

  • send_faxwrite actionFree

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

Public scan report

scanner v0.1.9 · 2026-09-24 · same rubric, same numbers if you re-run it

1 high1 low
  • Code scanremote-only server, no package to scann/a
  • Live reliabilityremote reachable in 774ms20/20
  • Tool poisoning4 tool descriptions checked15/15
  • Auth qualityopen endpoint exposes 2 write-action tools with no auth3/15
  • Maintenanceno repository listed3/15
  • Maintainer identityverified namespace with website, no repo4/10

Findings (2)

  • highWrite-action tools reachable without authenticationauth.open-write
  • lowNo source repository listedmaint.no-repo
Overall 60/100. Components that don't apply are left out of the denominator. Any critical finding is an F.RubricAppeal a findingJSON

Install directly

claude mcp add --transport http faxer https://faxer.me/mcp
Add to Cursor

Faxer — Send Faxes: common questions

Is Faxer — Send Faxes MCP server safe?
With care: it is graded C, so read the findings first (60/100). Read the Faxer — Send Faxes safety report
How do I install Faxer — Send Faxes?
It runs remotely at faxer.me. Add it to Claude Code, Claude Desktop or Cursor with the snippets above, or call it through the mcp.market gateway without installing anything.
Does Faxer — Send Faxes need an API key?
Not as far as the registry entry and our scan can tell: no credentials are declared or required.
Is Faxer — Send Faxes maintained?
The latest release is v1.0.0.
Is Faxer — Send Faxes up?
100% of our last 19 checks got an answer. We check remote servers about four times a day.

More from faxer.me