Remote MCP · Endpoint

Piloxa MCP server

No. Piloxa answered an MCP handshake 5 hours ago.

UpLast checked 5 hours ago

Server URL

https://piloxa.com/mcp

The last check completed an MCP handshake.

Registry name
io.github.Piloxa/piloxa
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
31 ms
Tools exposed
9 tools
Uptime, last 30 days
100% from 17 checks
Described by its publisher as
Prepare USPS Certified Mail letters from any AI assistant; a person reviews, pays and authorizes.
Listing
From the official MCP registry (active).
Recent checks of Piloxa
CheckedResultHandshake
5 hours agoHandshake completed31 ms
2 days agoHandshake completed25 ms
4 days agoHandshake completed28 ms
5 days agoHandshake completed58 ms
7 days agoHandshake completed31 ms
8 days agoHandshake completed27 ms
9 days agoHandshake completed22 ms
12 days agoHandshake completed28 ms
13 days agoHandshake completed26 ms
15 days agoHandshake completed27 ms
16 days agoHandshake completed24 ms
17 days agoHandshake completed28 ms
18 days agoHandshake completed40 ms
19 days agoHandshake completed27 ms
20 days agoHandshake completed32 ms
21 days agoHandshake completed54 ms
22 days agoHandshake completed30 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 Piloxa and makes no claim about it beyond what these checks measured.