Remote MCP · Endpoint

Remite MCP server

No. Remite answered an MCP handshake 9 hours ago.

UpLast checked 9 hours ago

Server URL

https://burofax.onmax.me/mcp/claude

The last check completed an MCP handshake.

Registry name
me.onmax/remite
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
352 ms
Tools exposed
4 tools
Uptime, last 30 days
100% from 13 checks
Described by its publisher as
Send a burofax or certified letter to a Spanish address, with proof of delivery and content.
Listing
From the official MCP registry (active).
Recent checks of Remite
CheckedResultHandshake
9 hours agoHandshake completed352 ms
4 days agoHandshake completed255 ms
14 days agoHandshake completed227 ms
15 days agoHandshake completed752 ms
15 days agoHandshake completed256 ms
17 days agoHandshake completed265 ms
18 days agoHandshake completed424 ms
19 days agoHandshake completed255 ms
20 days agoHandshake completed220 ms
21 days agoHandshake completed228 ms
23 days agoHandshake completed355 ms
26 days agoHandshake completed619 ms
28 days agoHandshake completed336 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 Remite and makes no claim about it beyond what these checks measured.