Remote MCP · Endpoint

PayPerFax MCP server

No. PayPerFax answered an MCP handshake 1 hour ago.

UpLast checked 1 hour 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
162 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
1 hour agoHandshake completed162 ms
2 days agoHandshake completed243 ms
5 days agoHandshake completed236 ms
7 days agoHandshake completed258 ms
9 days agoHandshake completed373 ms
11 days agoHandshake completed185 ms
13 days agoHandshake completed249 ms
15 days agoHandshake completed287 ms
17 days agoHandshake completed77 ms
19 days agoHandshake completed311 ms
20 days agoHandshake completed290 ms
21 days agoHandshake completed264 ms
23 days agoHandshake completed363 ms

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

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.