Faxer — Send Faxes
REMOTE · FAXER.ME · SCANNED AUG 17
Send real faxes from AI assistants. Pay per fax ($1 + $0.25/page), no account or API key.
Available components
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 →
Endpoint Security63
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- 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. See how to fix → View diagnostics → Unverified
- 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 Usability73
- AI-judged instruction clarity (excellent).Pass
- 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. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management40
- Stability observed for 12 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
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
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Add this component to your MCP client. Where a client-specific snippet is available, pick your client below and copy it straight into your config; otherwise use the connection detail shown.
remote · faxer.me
claude mcp add --transport http me-faxer-faxer https://faxer.me/mcp
[mcp_servers.me-faxer-faxer] url = "https://faxer.me/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"me-faxer-faxer": {
"type": "remote",
"url": "https://faxer.me/mcp",
"enabled": true
}
}
} openclaw mcp add me-faxer-faxer --url https://faxer.me/mcp --transport streamable-http
mcp_servers:
me-faxer-faxer:
url: "https://faxer.me/mcp" {
"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.
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.
- 17 Aug 26 +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.
- 15 Aug 26 +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.
- 13 Aug 26 +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.
- 11 Aug 26 +2
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 9 Aug 26 +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.
- 7 Aug 26 +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.
- 6 Aug 26 0
- Stability: unverified → 0.03 ▲ functional
- 5 Aug 26 64
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 17 Aug 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 | 7 Aug 2026 | 5 Nov 2026 | ECDSA 256 | ECDSA-SHA256 | 4d3a755c83ae65da0e629d02f954764a |
| 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 |
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 |
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.
create_fax_payment Create a fax payment link ~166
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.
| 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 ~141
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.
| 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 ~75
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.
| 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 ~260
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.
| 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.