Faxer — Send Faxes
REMOTE · FAXER.ME
Send real faxes from AI assistants. Pay per fax ($1 + $0.25/page), no account or API key.
Available components
Last scanned (23 hours ago)
Scores higher than 94% of remote servers
Reachable. Last reached 16 Oct 2026.
Category Communication
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 Usability67
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 1013 tokens (~253/item across 4 items; 4 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 Management100
- No destabilizing schema changes in the last 30 days.Pass
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
- All 1 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation.Pass
- An AI judge read all 5 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 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.
- 28 Sept 26 +7
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 25 Sept 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 4 Sept 26 0
- Stability: 0.97 → pass security
- 31 Aug 26 0
- The server rewrote its instructions, which are the text every model session reads security
- Tool “create_fax_payment” rewrote its description, which is the text the model reads security
- Tool “get_fax_quote” rewrote its description, which is the text the model reads security
- Tool “get_fax_status” rewrote its description, which is the text the model reads security
- Tool “send_fax” rewrote its description, which is the text the model reads security
- Schema quality: 222 → 253 ▼ functional
- 26 Aug 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 11 Aug 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 6 Aug 26 0
- Stability: unverified → 0.03 ▲ functional
- 5 Aug 26 0
First indexed and scored.
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 16 Oct 2026 · Probed https://faxer.me/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=faxer.me | CN=WE1,O=Google Trust Services,C=US | 5 Oct 2026 | 3 Jan 2027 | ECDSA 256 | ECDSA-SHA256 | 6dc1bc8bf565a48e138a194029b8ccd6 |
| SANs: faxer.me, *.faxer.me | ||||||
| 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 faxer.me. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| me. | present | 45352 | 8 | Verified |
| faxer.me. | 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=63072000; includeSubDomains |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://faxer.me/mcp | Verified | 200 | |
| http (plaintext) | http://faxer.me/mcp | HTTPS enforced | 301 | https://faxer.me/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_payment Create a fax payment link ~188
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.
| Name | Type | Req | Description |
|---|---|---|---|
| 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 | yes | Recipient fax number in international format, e.g. +15551234567. |
No output schema declared.
No examples provided.
get_fax_quote Get a fax price quote ~187
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.
| Name | Type | Req | Description |
|---|---|---|---|
| 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. |
No output schema declared.
No examples provided.
get_fax_status Check fax delivery status ~91
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.
| Name | Type | Req | Description |
|---|---|---|---|
| fax_id | string | yes | The fax_id returned by send_fax. |
No output schema declared.
No examples provided.
send_fax Send the fax ~275
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).
| Name | Type | Req | Description |
|---|---|---|---|
| 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 | yes | Recipient fax number in international format, e.g. +15551234567. |
No output schema declared.
No examples provided.
How do I install the Faxer — Send Faxes MCP server?
Faxer — Send Faxes is a hosted endpoint at https://faxer.me/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 · faxer.me
claude mcp add --transport http me-faxer-faxer 'https://faxer.me/mcp'
What is the Faxer — Send Faxes MCP server?
Faxer — Send Faxes is an MCP server listed in the public MCP registry as me.faxer/faxer. Send real faxes from AI assistants. Pay per fax ($1 + $0.25/page), no account or API key. This page covers its hosted endpoint (https://faxer.me/mcp).
Is the Faxer — Send Faxes MCP server safe to use?
Faxer — Send Faxes scores 86 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 Faxer — Send Faxes MCP server expose?
Faxer — Send Faxes exposes 4 tools: get_fax_quote, create_fax_payment, send_fax, get_fax_status. Their descriptions and schemas cost roughly 741 tokens of context every time the server is loaded.
Does the Faxer — Send Faxes MCP server require authentication?
No. We connected to Faxer — Send Faxes without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the Faxer — Send Faxes MCP server still maintained?
Faxer — Send Faxes is still listed as active in the MCP registry. We last reached this channel on 16 October 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.