Remote MCP · Endpoint

SendaFax MCP server

No. SendaFax answered an MCP handshake 1 day ago.

UpLast checked 1 day ago

Server URL

https://sendafax.ai/api/mcp

The last check completed an MCP handshake.

Registry name
ai.sendafax/sendafax
Transport
Streamable HTTP
Protocol negotiated
2025-03-26
Handshake latency
69 ms
Tools exposed
3 tools
Uptime, last 30 days
100% from 17 checks
Described by its publisher as
Send a fax in Australia (+61). Pay only if it delivers. Email receipt. No card at send.
Listing
From the official MCP registry (active).
Recent checks of SendaFax
CheckedResultHandshake
1 day agoHandshake completed69 ms
3 days agoHandshake completed66 ms
5 days agoHandshake completed68 ms
7 days agoHandshake completed57 ms
8 days agoHandshake completed69 ms
9 days agoHandshake completed110 ms
11 days agoHandshake completed54 ms
13 days agoHandshake completed76 ms
15 days agoHandshake completed58 ms
17 days agoHandshake completed74 ms
18 days agoHandshake completed71 ms
19 days agoHandshake completed57 ms
20 days agoHandshake completed62 ms
21 days agoHandshake completed67 ms
21 days agoHandshake completed162 ms
23 days agoHandshake completed71 ms
24 days agoHandshake completed55 ms

The last 17 checks. Full history is kept for 30 days; the all-time counter stands at 17 responding of 17.

How to read this

  • ·Handshake latency is one measurement from one probe, from our infrastructure. It is a smoke signal about the endpoint, not a benchmark of your own connection to it.
  • ·An authentication challenge counts as responding. A hosted server that refuses an anonymous prober is behaving correctly.
  • ·A tool count of “behind credentials” means the handshake worked but listing tools needed a token we do not hold.
  • ·Uptime covers the last 30 days of our own checks, at most one an hour, and says how many checks it is drawn from.

Listing data comes from the official MCP registry. Glide is not affiliated with SendaFax and makes no claim about it beyond what these checks measured.