Remote MCP · Endpoint

PayPerFax MCP server

No. PayPerFax answered an MCP handshake 7 hours ago.

UpLast checked 7 hours ago

Server URL

https://fax.payperfax.com/mcp

The last check completed an MCP handshake.

Registry name
com.payperfax/fax
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
82 ms
Tools exposed
3 tools
Uptime, last 30 days
100% from 13 checks
Described by its publisher as
Your AI assistant prepares the fax. You check it and pay in your browser. Pay per fax. No account.
Listing
From the official MCP registry (active).
Recent checks of PayPerFax
CheckedResultHandshake
7 hours agoHandshake completed82 ms
4 days agoHandshake completed301 ms
14 days agoHandshake completed220 ms
15 days agoHandshake completed820 ms
15 days agoHandshake completed228 ms
17 days agoHandshake completed203 ms
18 days agoHandshake completed220 ms
19 days agoHandshake completed503 ms
20 days agoHandshake completed238 ms
21 days agoHandshake completed289 ms
23 days agoHandshake completed162 ms
26 days agoHandshake completed243 ms
28 days agoHandshake completed236 ms

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

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 PayPerFax and makes no claim about it beyond what these checks measured.