Remote MCP · Endpoint

Oh Fax MCP server

No. Oh Fax answered an MCP handshake 1 hour ago.

UpLast checked 1 hour ago

Server URL

https://app.ohfax.com/mcp

The last check completed an MCP handshake.

Registry name
com.ohfax/ohfax
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
326 ms
Tools exposed
4 tools
Uptime, last 30 days
94.1% from 17 checks
Described by its publisher as
Outbound US/CA fax for agents: quote PDF, pay via MPP, get delivery receipt.
Listing
From the official MCP registry (active).
Recent checks of Oh Fax
CheckedResultHandshake
1 hour agoHandshake completed326 ms
2 days agoFailed - the request timed out—
4 days agoHandshake completed407 ms
5 days agoHandshake completed51 ms
7 days agoHandshake completed325 ms
8 days agoHandshake completed284 ms
9 days agoHandshake completed476 ms
12 days agoHandshake completed344 ms
13 days agoHandshake completed604 ms
15 days agoHandshake completed77 ms
16 days agoHandshake completed284 ms
17 days agoHandshake completed335 ms
18 days agoHandshake completed288 ms
19 days agoHandshake completed581 ms
20 days agoHandshake completed335 ms
21 days agoHandshake completed378 ms
22 days agoHandshake completed357 ms

The last 17 checks. Full history is kept for 30 days; the all-time counter stands at 16 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 Oh Fax and makes no claim about it beyond what these checks measured.