Dimefax MCP server
com.dimefax/dimefaxdimefax.comstreamable-httpv1.1.0Scanned
Fax any US or Canada number for 10¢ a page. No subscription, no account needed first.
2 tools: 1 do something that can't be undone and 1 change things.
- Reads private data · 0
- Reads text others write · 1
- Can send data out · 1
- 1 finding
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.
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 Dimefax MCP server can do
The Dimefax MCP server is published by dimefax.com, a domain the MCP Registry verified. It has 2 tools. It can do things that cannot be undone, such as sending, paying or publishing (send_fax) and create or change data (1 tool: fax_status), but cannot delete data. None of its tools only reads.
1 tool brings in text other people can write (send_fax); 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 lists its tools without sign-in.
Last scanned Nov 11, 2026, version 1.1.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.
2 tools
Can't be undone 1Claude Code: ask
send_faxSend a fax to a US or Canada fax number with Dimefax (10¢ a page, no subscription, no account needed first).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 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.
Description, as the server wrote it Send a fax to a US or Canada fax number with Dimefax (10¢ a page, no subscription, no account needed first). Give the document as base64 (PDF, PNG or JPEG), as a public https link to one, or as the plain text of a letter you wrote. This prepares the fax and returns a link for the user: they check it and pay (Apple Pay, Google Pay or card) or use page credits they already have, and it sends automatically. Nothing is sent or charged before that. If you can’t pass the file, call this with just the number: the user can add the document at the link.
Annotations the server declares
- title: Send a fax
- readOnlyHint: false
- destructiveHint: false
- idempotentHint: false
- openWorldHint: true
Changes things 1Claude Code: ask
fax_statusHow a fax set up with send_fax is going: waiting for payment, sending, trying again, delivered, or why it didn’t go through.1 finding
Why it is in this group
- The name "fax_status" says "status": a word for reading.
- The input takes a statement or command to run (input.code), which can change anything it can reach.
- The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
Findings
- Warn
The server marks "fax_status" read-only (readOnlyHint: true), and its own name, description or input give the class "write".
What this check looks forMatched text
annotations: {"readOnlyHint":true,"destructiveHint":false,"idempotentHint":true,"openWorldHint":false}; The name "fax_status" says "status": a word for reading.
Description, as the server wrote it How a fax set up with send_fax is going: waiting for payment, sending, trying again, delivered, or why it didn’t go through.
Annotations the server declares
- title: Check a fax
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
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 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.
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 18, 2026, 16:20 UTC, unchanged since Nov 11, 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
- https://api.dimefax.com/.well-known/oauth-protected-resource
- Authorization servers
- https://api.dimefax.com
- Legacy HTTP+SSE transport
- no
- Dynamic client registration
- yes
- Client ID metadata documents
- yes
- HighThe whole server
The endpoint served tools/list without credentials, and the list has 2 tools that change things (1 irreversible, 1 write). Whether a call also works without credentials was not tested: tools are never called.
What this check looks forMatched text
https://api.dimefax.com/mcp: tools/list returned 2 tools to an anonymous client, including send_fax (irreversible), fax_status (write)
Findings
Matches of fixed checks, with the text they matched.
- Warnfax_status
The server marks "fax_status" read-only (readOnlyHint: true), and its own name, description or input give the class "write".
What this check looks forMatched text
annotations: {"readOnlyHint":true,"destructiveHint":false,"idempotentHint":true,"openWorldHint":false}; The name "fax_status" says "status": a word for reading.
History
Changes to its tool definitions and to its remote endpoint, newest first.
No change seen yet. Its tools are rescanned every day, and a remote endpoint is looked at once a week.
Install
Pinned to version 1.1.0. Values in angle brackets are yours to fill in.
claude mcp add --transport http dimefax https://api.dimefax.com/mcpclaude mcp add --transport http dimefax https://api.dimefax.com/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": [],
"ask": [
"mcp__dimefax__send_fax",
"mcp__dimefax__fax_status"
],
"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 dimefax. Review it before you use it.
Capability tags behind 1 rule
- mcp__dimefax__send_fax untrusted-input, outbound
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.dimefax/dimefax/verify?hash=51661fe620c15dd0c90baa945cd52eec1dccdc9a98c58f9a1eddf2c30a0ffd3a" | jq -e '.changed == false'Pinned hash 51661fe620c1, from Nov 11, 2026, 05:18 UTC.
Watch
Get told when its tools change: a new tool, a new description, a new class.
https://radar.anlyon.com/servers/com.dimefax/dimefax/changes.xmlAn Atom feed. Works in any feed reader or Slack's RSS app.
Badge
[](https://radar.anlyon.com/servers/com.dimefax/dimefax)Source: MCP Registry · repository. Synced Nov 11, 2026, 05:17 UTC.
Dimefax MCP server: questions and answers
Answered from the scan above, not from the publisher's description.
Is the Dimefax MCP server safe?
- No scan can promise that. What its definitions show: 2 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 Dimefax MCP server delete data?
- No tool is classed as destructive: going by their definitions, none of them deletes, cancels or revokes anything.
Can the Dimefax MCP server do things that cannot be undone?
- Yes. 1 tool can send, pay, publish or merge: send_fax.
What tools does the Dimefax MCP server have?
- 2 tools: 1 irreversible, 1 write. send_fax and fax_status.
Does the Dimefax MCP server need sign-in or OAuth?
- Its remote endpoint listed its tools to an anonymous client, without sign-in.
Does the Dimefax 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 Dimefax MCP server changed its tools?
- Not since Anlyon Radar started tracking it. Last scanned Nov 11, 2026.