Faxer — Send Faxes MCP server
me.faxer/faxerfaxer.mestreamable-httpv1.0.0Scanned
Send real faxes from AI assistants. Pay per fax ($1 + $0.25/page), no account or API key.
4 tools: 2 do something that can't be undone and 2 only read.
- Reads private data · 0
- Reads text others write · 4
- Can send data out · 2
- 1 finding
Tools listed without sign-in. Remote posture
With Anlyon
2 tools here do something that can't be undone. Govern them.
- Anlyon lists the tools and adopts none.
- Each tool you adopt gets approvals and receipts.
- Your agent never holds the key.
A tool your agent calls directly is not routed through Anlyon and is not governed by it. Anlyon Radar only lists and labels, and these labels are the same either way.
What the Faxer — Send Faxes MCP server can do
The Faxer — Send Faxes MCP server is published by faxer.me, a domain the MCP Registry verified. It has 4 tools. It can do things that cannot be undone, such as sending, paying or publishing (create_fax_payment and send_fax), but cannot delete data. 2 tools only read.
4 tools bring in text other people can write (get_fax_quote, create_fax_payment, send_fax and 1 more); 2 tools can send data out of your system (create_fax_payment and send_fax).
The fixed checks matched 1 finding (credentials-mention). Each one comes with the text it matched.
Its remote endpoint lists its tools without sign-in, and its tools changed once since Anlyon Radar first saw them.
Last scanned Nov 18, 2026, version 1.0.0.
Tools
Grouped by what each tool does, most consequential first. Open one for its reasons and full description; descriptions are the publisher's own words.
4 tools
Can't be undone 2Claude Code: ask
create_fax_paymentCreate a Stripe Checkout payment link for a fax.Reads text others writeCan send data outNo findings
Why it is in this group
- The name "create_fax_payment" says "create": a word for a change.
- The input addresses people (input.to): what it sends cannot be taken back.
What it can reach
- untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
- outboundThe input takes a destination (input.to): what the tool writes goes there.
Description, as the server wrote it 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.
Annotations the server declares
- readOnlyHint: false
- destructiveHint: false
- idempotentHint: false
- openWorldHint: true
send_faxTransmit a fax.Reads text others writeCan send data out1 finding
Why it is in this group
- The name "send_fax" says "send": a word for sending, and what is sent cannot be taken back.
- The input addresses people (input.to): what it sends cannot be taken back.
What it can reach
- untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
- outboundThe name "send_fax" says "send": it sends or publishes something to other people.
- outboundThe input takes a destination (input.to): what the tool writes goes there.
Findings
- Info
The description mentions "credential".
What this check looks forMatched text
description: "...ayment Token; pay it and retry with the credential in _meta['org.paymentauth/credential']...."
Description, as the server wrote it 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; a Checkout payment is only charged once the fax is delivered (the hold is released if it fails), and Stripe machine payments are refunded automatically if the fax fails to send or deliver (on-chain payments are refunded manually).
Annotations the server declares
- readOnlyHint: false
- destructiveHint: false
- idempotentHint: false
- openWorldHint: true
Only reads 2Show 2 read-only tools
get_fax_quoteGet the exact price to send a real fax to any US, Canadian, or international fax number via faxer.me.Reads text others writeNo findings
Why it is in this group
- The name "get_fax_quote" says "get": a word for reading.
What it can reach
- untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
Description, as the server wrote it 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.
Annotations the server declares
- readOnlyHint: true
- openWorldHint: true
get_fax_statusCheck the delivery status of a fax sent with send_fax.Reads text others writeNo findings
Why it is in this group
- The name "get_fax_status" says "get": a word for reading.
What it can reach
- untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
Description, as the server wrote it 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.
Annotations the server declares
- readOnlyHint: true
- openWorldHint: true
This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.
Exfil surface
Which tools read private data, which read text someone else can write, and which can send data out. One of each is a path a prompt injection can use.
No private-data, untrusted-input, outbound path in this server alone: no tool is tagged private-data.
- Reads private data0
- Reads files, mail, messages, databases, secrets, calendars or repositories.
- Reads text others write4
- Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
- Can send data out2
- Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.
Other servers in the same agent add their own tools to these paths. Audit your whole setup to see them together.
Remote posture
What anyone on the internet sees at the remote endpoint: an anonymous initialize and tools/list, and the public OAuth metadata.
Looked at Nov 20, 2026, 19:15 UTC, unchanged since Oct 22, 2026. No credentials were sent and no tool was called. What is looked at.
- Reachable
- yes
- HTTP status of an anonymous initialize
- 200
- tools/list served without credentials
- yes
- Tools that change things, listed without credentials
- 2
- Protocol version
- 2025-06-18
- WWW-Authenticate on 401
- not observed
- resource_metadata in WWW-Authenticate
- not observed
- RFC 9728 protected resource metadata
- not observed
- Authorization servers
- not observed
- Legacy HTTP+SSE transport
- no
- Dynamic client registration
- not observed
- Client ID metadata documents
- not observed
- HighThe whole server
The endpoint served tools/list without credentials, and the list has 2 tools that change things (2 irreversible). Whether a call also works without credentials was not tested: tools are never called.
What this check looks forMatched text
https://faxer.me/mcp: tools/list returned 4 tools to an anonymous client, including create_fax_payment (irreversible), send_fax (irreversible)
Findings
Matches of fixed checks, with the text they matched.
- Infosend_fax
The description mentions "credential".
What this check looks forMatched text
description: "...ayment Token; pay it and retry with the credential in _meta['org.paymentauth/credential']...."
History
Changes to its tool definitions and to its remote endpoint, newest first.
Tools3 changed.~3 changedView diff
- Changed:create_fax_paymentCan't be undoneinputSchema
- Changed:get_fax_quoteOnly readsinputSchema
- Changed:send_faxCan't be undonedescription
Install
Pinned to version 1.0.0. Values in angle brackets are yours to fill in.
claude mcp add --transport http faxer https://faxer.me/mcpclaude mcp add --transport http faxer https://faxer.me/mcpRun in a terminal.
Claude Code permissions
Allow the reads, ask before a change or a way out, deny the deletes. Paste into .claude/settings.json.
{
"permissions": {
"allow": [
"mcp__faxer__get_fax_quote",
"mcp__faxer__get_fax_status"
],
"ask": [
"mcp__faxer__create_fax_payment",
"mcp__faxer__send_fax"
],
"deny": []
}
}Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. A read that can send data out (it takes a URL, say) asks first too. It assumes the server is installed as faxer. Review it before you use it.
Capability tags behind 4 rules
- mcp__faxer__get_fax_quote untrusted-input
- mcp__faxer__create_fax_payment untrusted-input, outbound
- mcp__faxer__send_fax untrusted-input, outbound
- mcp__faxer__get_fax_status untrusted-input
Pin
Keep the decision: fail CI when the tools change, follow every change, or show a badge.
Pin in CI
Fail a build when the tools you reviewed are not the tools the server serves today.
curl -s "https://radar.anlyon.com/api/v1/servers/me.faxer/faxer/verify?hash=be916c21dd4a48d23b5fa3957981b22669df1aefc1e973f2e7b0c642b14ff07d" | jq -e '.changed == false'Pinned hash be916c21dd4a, from Nov 18, 2026, 19:17 UTC.
Watch
Get told when its tools change: a new tool, a new description, a new class.
https://radar.anlyon.com/servers/me.faxer/faxer/changes.xmlAn Atom feed. Works in any feed reader or Slack's RSS app.
Badge
[](https://radar.anlyon.com/servers/me.faxer/faxer)Source: MCP Registry. Synced Oct 21, 2026, 18:53 UTC.
Faxer — Send Faxes MCP server: questions and answers
Answered from the scan above, not from the publisher's description.
Is the Faxer — Send Faxes MCP server safe?
- No scan can promise that. What its definitions show: 4 tools, 2 of which can change, send or delete something, and 1 finding from fixed checks. Allow the reads, ask before each change, and deny the deletes; the permissions block on this page does that.
Can the Faxer — Send Faxes MCP server delete data?
- No tool is classed as destructive: going by their definitions, none of them deletes, cancels or revokes anything.
Can the Faxer — Send Faxes MCP server do things that cannot be undone?
- Yes. 2 tools can send, pay, publish or merge: create_fax_payment and send_fax.
What tools does the Faxer — Send Faxes MCP server have?
- 4 tools: 2 irreversible, 2 read. create_fax_payment, send_fax, get_fax_quote and get_fax_status.
Does the Faxer — Send Faxes MCP server need sign-in or OAuth?
- Its remote endpoint listed its tools to an anonymous client, without sign-in.
Does the Faxer — Send Faxes MCP server send data to outside services?
- 2 tools can carry data out (it sends, posts or publishes, or takes a recipient, channel or URL): create_fax_payment and send_fax.
Has the Faxer — Send Faxes MCP server changed its tools?
- Yes, once since Anlyon Radar started tracking it, most recently on Nov 18, 2026. Every change is on this page and in its Atom feed.