Faxwell
REMOTE · API.SENDFAXWELL.COM · 2 COMPONENTS
Fax any US or Canada number, as low as 6¢ a page. No subscription, no account needed first.
Available components
Last scanned (6 hours ago)
Scores higher than 52% of remote servers
Reachable. Last reached 5 Nov 2026.
Category Communication
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 → Why this is hard to score →
Endpoint Security63
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one. See how to fix → View diagnostics → Partial
- HTTPS enforcement could not be verified: the plaintext port answered with HTTP 405, which proves neither a plaintext path nor enforcement. View diagnostics → Unverified
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- 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 Usability68
- AI-judged instruction clarity (good).Pass
- Context-footprint check failed: tool/resource definitions use about 432 tokens (~216/item across 2 items; 2 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 Management7
- Stability observed for 2 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
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- All 1 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation.Pass
- An AI judge read all 3 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
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.
- 5 Nov 26 0
- The server rewrote its instructions, which are the text every model session reads security
- Tool “send_fax” rewrote its description, which is the text the model reads security
- 4 Nov 26 +1
- Stability: unverified → 0.03 ▲ functional
- 3 Nov 26 65
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 5 Nov 2026 · Probed https://api.sendfaxwell.com/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=sendfaxwell.com | CN=WE1,O=Google Trust Services,C=US | 29 Oct 2026 | 27 Jan 2027 | ECDSA 256 | ECDSA-SHA256 | c551d1221fed06a0e77d96c911162a1 |
| SANs: sendfaxwell.com, api.sendfaxwell.com, *.api.sendfaxwell.com | ||||||
| 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 |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of api.sendfaxwell.com. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| com. | present | 19718 | 13 | Verified |
| sendfaxwell.com. | 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 |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://api.sendfaxwell.com/mcp | Verified | 200 | |
| http (plaintext) | http://api.sendfaxwell.com/mcp | Inconclusive | 405 |
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. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
fax_status Check a fax ~58
How a fax set up with send_fax is going: waiting for payment, sending, trying again, delivered, or why it didn’t go through.
| Name | Type | Req | Description |
|---|---|---|---|
| code | string | yes | The code send_fax returned (the end of the link). |
No output schema declared.
No examples provided.
send_fax Send a fax ~248
Send a fax to a US or Canada fax number with Faxwell (as low as 6¢ 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.
| Name | Type | Req | Description |
|---|---|---|---|
| document_base64 | string | – | The document, base64-encoded: a PDF, PNG or JPEG. |
| document_url | string | – | A public https link to a PDF, PNG or JPEG. |
| text | string | – | The text of a letter to fax, if there is no file. Faxwell sets it on letter-size pages. |
| to | string | yes | The fax number, US or Canada, e.g. "(503) 555-0147" or "+15035550147". |
No output schema declared.
No examples provided.
How do I install the Faxwell MCP server?
Faxwell is a hosted endpoint at https://api.sendfaxwell.com/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
remote · api.sendfaxwell.com
claude mcp add --transport http com-sendfaxwell-faxwell 'https://api.sendfaxwell.com/mcp'
What is the Faxwell MCP server?
Faxwell is an MCP server listed in the public MCP registry as com.sendfaxwell/faxwell. Fax any US or Canada number, as low as 6¢ a page. No subscription, no account needed first. This page covers its hosted endpoint (https://api.sendfaxwell.com/mcp).
Is the Faxwell MCP server safe to use?
Faxwell scores 66 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the Faxwell MCP server expose?
Faxwell exposes 2 tools: send_fax, fax_status. Their descriptions and schemas cost roughly 306 tokens of context every time the server is loaded.
Does the Faxwell MCP server require authentication?
No. We connected to Faxwell without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the Faxwell MCP server still maintained?
Faxwell is still listed as active in the MCP registry. We last reached this channel on 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.