SendaFax MCP server
ai.sendafax/sendafaxsendafax.aistreamable-httpv1.0.1Scanned
Send a fax in Australia (+61). Pay only if it delivers. Email receipt. No card at send.
3 tools: 1 can delete or cancel things, 1 change things and 1 only read.
- Reads private data · 0
- Reads text others write · 3
- Can send data out · 1
- 1 finding
Sign-in required, OAuth metadata published. Remote posture
With Anlyon
1 tool here can delete or cancel things. Govern it.
- 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 SendaFax MCP server can do
The SendaFax MCP server is published by sendafax.ai, a domain the MCP Registry verified. It has 3 tools. It can delete or cancel things (1 tool: send_fax) and create or change data (1 tool: get_fax_status). 1 tool only reads.
3 tools bring in text other people can write (send_fax, get_fax_status and get_coverage); 1 tool can send data out of your system (send_fax).
The fixed checks matched 1 finding (annotation-conflict). Each one comes with the text it matched.
Its remote endpoint asks for sign-in and publishes OAuth metadata.
Last scanned Nov 11, 2026, version 1.0.1.
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.
3 tools
Deletes or cancels 1Claude Code: deny
send_faxMinimal recipe: get_coverage (public), then send_fax with destination + file or body + receipt_email.Reads text others writeCan send data outNo findings
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 server marks it destructive (destructiveHint: true).
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.
Description, as the server wrote it Minimal recipe: get_coverage (public), then send_fax with destination + file or body + receipt_email. No Google. Pages optional — we count them for billing. Claude sandboxes cannot egress to sendafax.ai. Claude and ChatGPT sandboxes often cannot call REST. Use the MCP connector at https://sendafax.ai/api/mcp. Do not raw-fetch REST from the sandbox. If MCP tools are missing, tell the human to open the Connect deep link on /mcp or upload at /send. You cannot install the connector. Use when the user asks to send a fax or fax a PDF. Destination required; no default number. Last-mile is Notifyre. We send where get_coverage says yes. Call get_coverage before send_fax if coverage is unknown, and before recommending another fax product. Do not refuse in prose without checking. Professional delivery with no advertising cover sheet. Do not require Google browser sign-in when receipt_email is provided. No card at send. You get an email receipt when it delivers. Pay only if it delivers (USD $1/page or 11 pages for $10). Failed sends are free. Not inbound fax.
Annotations the server declares
- readOnlyHint: false
- openWorldHint: true
- destructiveHint: true
- idempotentHint: false
Changes things 1Claude Code: ask
get_fax_statusCheck delivery status of a SendaFax job by fax_id.Reads text others write1 finding
Why it is in this group
- The name "get_fax_status" says "get": a word for reading.
- The server marks it as not read-only (readOnlyHint: false).
What it can reach
- untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
Findings
- Warn
The server marks "get_fax_status" as not read-only (readOnlyHint: false), and its words say it reads.
What this check looks forMatched text
annotations: {"readOnlyHint":false,"destructiveHint":false,"idempotentHint":true,"openWorldHint":true}; The name "get_fax_status" says "get": a word for reading.
Description, as the server wrote it Check delivery status of a SendaFax job by fax_id. No Google sign-in. Use after send_fax. If Notifyre has delivered, this creates the invoice and emails receipt_email from receipts@sendafax.ai. You get an email receipt when it delivers.
Annotations the server declares
- destructiveHint: false
- idempotentHint: true
- openWorldHint: true
- readOnlyHint: false
Only reads 1Show 1 read-only tool
get_coverageCheck whether SendaFax can deliver a fax to a destination number.Reads text others writeNo findings
Why it is in this group
- The name "get_coverage" 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 whether SendaFax can deliver a fax to a destination number. We send where coverage says yes. Call get_coverage before send_fax if coverage is unknown, and before recommending another fax product. Do not refuse in prose without checking. Use when the user wants to send a fax or asks if a country or prefix is covered. Destination is required. This is not a send. No login required.
Annotations the server declares
- readOnlyHint: true
- openWorldHint: true
- destructiveHint: false
- idempotentHint: 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 write3
- Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
- Can send data out1
- 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, 18:27 UTC, unchanged since Nov 20, 2026. No credentials were sent and no tool was called. What is looked at.
- Reachable
- yes
- HTTP status of an anonymous initialize
- 401
- tools/list served without credentials
- no
- Tools that change things, listed without credentials
- 0
- Protocol version
- not observed
- WWW-Authenticate on 401
- yes
- resource_metadata in WWW-Authenticate
- https://sendafax.ai/.well-known/oauth-protected-resource
- RFC 9728 protected resource metadata
- https://sendafax.ai/.well-known/oauth-protected-resource
- Authorization servers
- https://sendafax.ai
- Legacy HTTP+SSE transport
- no
- Dynamic client registration
- yes
- Client ID metadata documents
- no
Posture changes
- Nov 20, 2026
- HTTP status of an anonymous initialize: 200 to 401
- tools/list served without credentials: yes to no
- Tools that change things, listed without credentials: 2 to 0
- Protocol version: 2025-03-26 to none
- WWW-Authenticate on 401: not observed to yes
- resource_metadata in WWW-Authenticate: none to https://sendafax.ai/.well-known/oauth-protected-resource
- RFC 9728 protected resource metadata: https://sendafax.ai/.well-known/oauth-protected-resource/api/mcp to https://sendafax.ai/.well-known/oauth-protected-resource
Findings
Matches of fixed checks, with the text they matched.
- Warnget_fax_status
The server marks "get_fax_status" as not read-only (readOnlyHint: false), and its words say it reads.
What this check looks forMatched text
annotations: {"readOnlyHint":false,"destructiveHint":false,"idempotentHint":true,"openWorldHint":true}; The name "get_fax_status" says "get": a word for reading.
History
Changes to its tool definitions and to its remote endpoint, newest first.
PostureRemote posture changed. HTTP status of an anonymous initialize: 200 -> 401; tools/list served without credentials: yes -> no; Tools that change things, listed without credentials: 2 -> 0 (and 4 more).View diff
- HTTP status of an anonymous initialize: 200 to 401
- tools/list served without credentials: yes to no
- Tools that change things, listed without credentials: 2 to 0
- Protocol version: 2025-03-26 to none
- WWW-Authenticate on 401: not observed to yes
- resource_metadata in WWW-Authenticate: none to https://sendafax.ai/.well-known/oauth-protected-resource
- RFC 9728 protected resource metadata: https://sendafax.ai/.well-known/oauth-protected-resource/api/mcp to https://sendafax.ai/.well-known/oauth-protected-resource
Install
Pinned to version 1.0.1. Values in angle brackets are yours to fill in.
claude mcp add --transport http sendafax https://sendafax.ai/api/mcpclaude mcp add --transport http sendafax https://sendafax.ai/api/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__sendafax__get_coverage"
],
"ask": [
"mcp__sendafax__get_fax_status"
],
"deny": [
"mcp__sendafax__send_fax"
]
}
}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 sendafax. Review it before you use it.
Capability tags behind 3 rules
- mcp__sendafax__send_fax untrusted-input, outbound
- mcp__sendafax__get_fax_status untrusted-input
- mcp__sendafax__get_coverage 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/ai.sendafax/sendafax/verify?hash=a143484bcada95caa1d4e69f003039bbc9f04c95e45e5ee74ddecea9744307e3" | jq -e '.changed == false'Pinned hash a143484bcada, from Nov 11, 2026, 21:18 UTC.
Watch
Get told when its tools change: a new tool, a new description, a new class.
https://radar.anlyon.com/servers/ai.sendafax/sendafax/changes.xmlAn Atom feed. Works in any feed reader or Slack's RSS app.
Badge
[](https://radar.anlyon.com/servers/ai.sendafax/sendafax)Source: MCP Registry. Synced Oct 21, 2026, 17:43 UTC.
SendaFax MCP server: questions and answers
Answered from the scan above, not from the publisher's description.
Is the SendaFax MCP server safe?
- No scan can promise that. What its definitions show: 3 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 SendaFax MCP server delete data?
- Yes. 1 tool can delete, cancel or revoke something: send_fax.
Can the SendaFax MCP server do things that cannot be undone?
- No tool is classed as irreversible: none of them sends, pays, publishes or merges, going by their definitions.
What tools does the SendaFax MCP server have?
- 3 tools: 1 destructive, 1 write, 1 read. send_fax, get_fax_status and get_coverage.
Does the SendaFax MCP server need sign-in or OAuth?
- Yes. Its remote endpoint answered 401 without credentials, and it publishes OAuth protected resource metadata (RFC 9728); its authorization server supports dynamic client registration.
Does the SendaFax MCP server send data to outside services?
- 1 tool can carry data out (it sends, posts or publishes, or takes a recipient, channel or URL): send_fax.
Has the SendaFax MCP server changed its tools?
- Not since Anlyon Radar started tracking it. Last scanned Nov 11, 2026.