Skip to content

PayPerFax MCP server

com.payperfax/faxpayperfax.comstreamable-httpv1.0.4Scanned

Your AI assistant prepares the fax. You check it and pay in your browser. Pay per fax. No account.

3 tools: 1 do something that can't be undone and 2 only read.

Tools: 0 delete, 1 irreversible, 0 write, 2 read.
  • Reads private data · 1
  • Reads text others write · 1
  • Can send data out · 1
  • No findings

Tools listed without sign-in. Remote posture

With Anlyon

1 tool here does something that can't be undone. Govern it.

  • Anlyon lists the tools and adopts none.
  • Each tool you adopt gets approvals and receipts.
  • Your agent never holds the key.
Govern this server →

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 PayPerFax MCP server can do

The PayPerFax MCP server is published by payperfax.com, a domain the MCP Registry verified. It has 3 tools. It can do things that cannot be undone, such as sending, paying or publishing (create_fax), but cannot delete data. 2 tools only read.

1 tool reads private data (list_supported_formats); 1 tool brings in text other people can write (list_supported_formats); 1 tool can send data out of your system (create_fax). On its own it has all three parts of a prompt-injection exfiltration path: private data, text others write, and a way out.

None of the fixed checks matched anything in its tool definitions. That is not a safety guarantee.

Its remote endpoint lists its tools without sign-in, and its tools changed 2 times since Anlyon Radar first saw them.

Last scanned Nov 19, 2026, version 1.0.4.

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

Can't be undone 1Claude Code: ask
  • create_faxPrepare a fax for a person to send with PayPerFax, the pay-per-fax service: no account, no subscription, one payment for one fax.Can send data outNo findings

    Why it is in this group

    • The name "create_fax" says "create": a word for a change.
    • The input addresses people (input.to): what it sends cannot be taken back.

    What it can reach

    • outboundThe input takes a destination (input.to): what the tool writes goes there.
    Description, as the server wrote it
    Prepare a fax for a person to send with PayPerFax, the pay-per-fax service: no account, no subscription, one payment for one fax. A common use is a letter or a form for the IRS, a doctor, a court, an insurer or a landlord. The tool does not send the fax and does not charge. It returns a link for the person. The person opens the link, sees the preview and the price, and pays in the browser. Then the fax is sent. Rules: 1. Email: ask the person for their email address. Do not guess it. The confirmation and the receipt go there. 2. A document that the person has as a file (a PDF, a scan, a signed form): do not retype it as text. A typed copy of a signed form is not the form. Set file_expected to true, and tell the person that they add the file on the page of the link. 3. The fax number of an agency or a company: take it from its official website (for the IRS: irs.gov), and show the person the source. A number from memory can send private papers to a stranger. 4. A letter that you write goes in markdown. With no cover page, the letter must have its own date, names and address block. With a cover page, keep cover_message short: a long message is cut off. 5. Limits: the markdown text can be at most 100 KB. Headings, lists, bold text and tables are printed. An image is printed as its alt text, a link as its text, and raw HTML as text. 6. If you can run shell commands and the document is a local file, send it with the HTTP call: curl -F "to=+14155550101" -F "email=person@example.com" -F "documents[]=@/path/to/file.pdf" https://fax.payperfax.com/api/fax 7. After the call, give the person the link, and say that nothing is sent and nothing is charged before they pay. The confirmation email comes after the payment. If the status of the fax is later "failed", the person is not charged, and can send the fax again.

    Annotations the server declares

    • readOnlyHint: false
    • destructiveHint: false
    • title: Create a fax
Only reads 2Show 2 read-only tools
  • get_fax_statusRead where a fax is.No findings

    Why it is in this group

    • The name "get_fax_status" says "get": a word for reading.
    Description, as the server wrote it
    Read where a fax is. Give the id from create_fax, or an address of the fax: the status address from the tracking prompt of the person, or the address of a page of the fax. "status" is pending, delivered, failed or expired. While it is pending, "stage" says more: rendering (we prepare the pages), awaiting_payment (the person did not pay yet; "pages" and "price" are given, and they can still change), sending (paid, on its way). delivered: the fax arrived. failed: the fax was not delivered, the person is not charged, and can send it again; with "render_failed", the document could not be prepared, and the person opens the link to change it. expired: the fax was not paid in time, or it is no longer available. Do not call this in a loop: read the status when the person asks.

    Annotations the server declares

    • readOnlyHint: true
    • title: Get the status of a fax
  • list_supported_formatsList what PayPerFax can fax, and the limits: the text that create_fax takes, the file types that a person can add on the form or that a shell can send to the HTTP call, the sizes, …Reads private dataReads text others writeNo findings

    Why it is in this group

    • The name "list_supported_formats" says "list": a word for reading.

    What it can reach

    • private-dataThe description's first sentence says "list" and "file": it reads files.
    • untrusted-inputThe description's first sentence says "list" and "http": it reads web pages, which anyone can write.
    Description, as the server wrote it
    List what PayPerFax can fax, and the limits: the text that create_fax takes, the file types that a person can add on the form or that a shell can send to the HTTP call, the sizes, and the languages.

    Annotations the server declares

    • readOnlyHint: true
    • title: List the supported formats

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.

1 path in this server alone from private data, through text someone else wrote, to a way out. Denying 1 outbound tool breaks every one.

Reads private data1
Reads files, mail, messages, databases, secrets, calendars or repositories.
Reads text others write1
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.
deny to break every path
{
  "permissions": {
    "deny": [
      "mcp__fax__create_fax"
    ]
  }
}

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.

Tools listed without sign-in

Looked at Nov 20, 2026, 18:44 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
1
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 1 tool that changes things (1 irreversible). Whether a call also works without credentials was not tested: tools are never called.

    Matched text

    https://fax.payperfax.com/mcp: tools/list returned 3 tools to an anonymous client, including create_fax (irreversible)

    What this check looks for

Findings

Matches of fixed checks, with the text they matched.

No check matched anything in these tool definitions. That is not a safety guarantee.

History

Changes to its tool definitions and to its remote endpoint, newest first.

  1. Tools1 changed.~1 changedView diff
  2. Tools2 changed.~2 changedView diff

Install

Pinned to version 1.0.4. Values in angle brackets are yours to fill in.

claude mcp add --transport http fax https://fax.payperfax.com/mcp
claude mcp add --transport http fax https://fax.payperfax.com/mcp

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

.claude/settings.json
{
  "permissions": {
    "allow": [
      "mcp__fax__get_fax_status",
      "mcp__fax__list_supported_formats"
    ],
    "ask": [
      "mcp__fax__create_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 fax. Review it before you use it.

Capability tags behind 2 rules
  • mcp__fax__create_fax outbound
  • mcp__fax__list_supported_formats private-data, 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/com.payperfax/fax/verify?hash=35442755c4282ad476ebefa0060785bd68fc2c558218f1fc0d1b34cce1e3b86f" | jq -e '.changed == false'

Pinned hash 35442755c428, from Nov 19, 2026, 19:18 UTC.

Watch

Get told when its tools change: a new tool, a new description, a new class.

https://radar.anlyon.com/servers/com.payperfax/fax/changes.xml

An Atom feed. Works in any feed reader or Slack's RSS app.

Badge

Anlyon Radar badge for com.payperfax/fax
[![Anlyon Radar](https://radar.anlyon.com/badge/com.payperfax/fax.svg)](https://radar.anlyon.com/servers/com.payperfax/fax)

Source: MCP Registry · repository. Synced Nov 5, 2026, 21:17 UTC.

PayPerFax MCP server: questions and answers

Answered from the scan above, not from the publisher's description.

Is the PayPerFax MCP server safe?

No scan can promise that. What its definitions show: 3 tools, 1 of which can change, send or delete something, and 0 findings from fixed checks. Allow the reads, ask before each change, and deny the deletes; the permissions block on this page does that.

Can the PayPerFax MCP server delete data?

No tool is classed as destructive: going by their definitions, none of them deletes, cancels or revokes anything.

Can the PayPerFax MCP server do things that cannot be undone?

Yes. 1 tool can send, pay, publish or merge: create_fax.

What tools does the PayPerFax MCP server have?

3 tools: 1 irreversible, 2 read. create_fax, get_fax_status and list_supported_formats.

Does the PayPerFax MCP server need sign-in or OAuth?

Its remote endpoint listed its tools to an anonymous client, without sign-in.

Does the PayPerFax 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): create_fax.

Has the PayPerFax MCP server changed its tools?

Yes, 2 times since Anlyon Radar started tracking it, most recently on Nov 5, 2026. Every change is on this page and in its Atom feed.