FaxFair
REMOTE · API.FAXFAIR.COM
Fax API and MCP server for AI agents. Fax US and Canada, pay per request with x402. No account.
Available components
Last scanned (11 hours ago)
Scores higher than 43% of remote servers
Reachable. Last reached 4 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 Security57
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation not fully verified: no authorisation is required to call this server, and 3 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe. See how to fix → View diagnostics → Unverified
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- 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 Usability75
- AI-judged instruction clarity (good).Pass
- Context-footprint check failed: tool/resource definitions use about 416 tokens (~138/item across 3 items; 3 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 Management0
- Stability not yet verified: not enough scan history yet (needs a 30-day window).Unverified
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 Safety75
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- 0 of 1 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation; "send_fax" implies "send" and declares no destructiveHint at all, which the MCP spec reads as destructive by default. See how to fix → Fail
- An AI judge read all 4 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities60
- Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28. See how to fix → Fail
Unverified: 1 category
A category scored 0 because we could not verify it: authentication we do not have, an unreachable endpoint, or not enough scan history. We only credit what we can confirm.
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.
- 4 Nov 26 61
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 4 Nov 2026 · Probed https://api.faxfair.com/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=api.faxfair.com | CN=WE1,O=Google Trust Services,C=US | 4 Nov 2026 | 2 Feb 2027 | ECDSA 256 | ECDSA-SHA256 | cb7f7fc29a1fcba90e22799ab983c657 |
| SANs: api.faxfair.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.faxfair.com. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| com. | present | 19718 | 13 | Verified |
| faxfair.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.faxfair.com/mcp | Verified | 200 | |
| http (plaintext) | http://api.faxfair.com/mcp | HTTPS enforced | 301 | https://api.faxfair.com/mcp |
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 →
get_fax_status ~45
Read one fax by id. Status is queued, sending, delivered or failed. Does not charge.
| Name | Type | Req | Description |
|---|---|---|---|
| fax_id | string | yes | The id returned by send_fax. |
No output schema declared.
No examples provided.
quote_fax ~115
Price one fax to a US or Canadian number before sending it. Returns both tiers: standard and priority, in cents and in USDC atomic units. Does not send the fax and does not charge.
| Name | Type | Req | Description |
|---|---|---|---|
| pages | integer | yes | How many pages the PDF has. |
| payer | string | – | Wallet address, if it has credit from a failed fax. |
| priority | boolean | – | true to price the priority tier. The reply always lists both tiers. |
| to | string | yes | Fax number in the United States or Canada. |
No output schema declared.
No examples provided.
send_fax ~172
Send a PDF to a US or Canadian fax number. Pass an https pdf_url. Pay with Authorization: Bearer and a prepaid API key, or with the x402 PAYMENT-SIGNATURE header. priority true uses the priority price and is sent before other agent faxes. A website or app fax is still sent first. If neither payment is present the call answers 402 with both prices.
| Name | Type | Req | Description |
|---|---|---|---|
| idempotency_key | string | – | 8 to 64 letters, digits, hyphens or underscores. Retries return the same fax. |
| pdf_url | string | yes | https link to the PDF. |
| priority | boolean | – | true: priority price, sent before other agent faxes. Omit for the standard price. |
| to | string | yes | Fax number in the United States or Canada. |
No output schema declared.
No examples provided.
How do I install the FaxFair MCP server?
FaxFair is a hosted endpoint at https://api.faxfair.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.faxfair.com
claude mcp add --transport http nico02138-ops-faxfair 'https://api.faxfair.com/mcp'
What is the FaxFair MCP server?
FaxFair is an MCP server listed in the public MCP registry as io.github.nico02138-ops/faxfair. Fax API and MCP server for AI agents. Fax US and Canada, pay per request with x402. No account. This page covers its hosted endpoint (https://api.faxfair.com/mcp).
Is the FaxFair MCP server safe to use?
FaxFair scores 61 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 FaxFair MCP server expose?
FaxFair exposes 3 tools: quote_fax, send_fax, get_fax_status. Their descriptions and schemas cost roughly 332 tokens of context every time the server is loaded.
Does the FaxFair MCP server require authentication?
No. We connected to FaxFair without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the FaxFair MCP server still maintained?
FaxFair is still listed as active in the MCP registry. We last reached this channel on 4 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.