Remote MCP · Endpoint

Fitralo MCP server

No. Fitralo answered an MCP handshake 16 minutes ago.

UpLast checked 16 minutes ago

Server URL

https://fitralo.com/mcp

The last check completed an MCP handshake.

Registry name
com.fitralo/carriers
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
304 ms
Tools exposed
3 tools
Uptime, last 30 days
92.9% from 14 checks
Described by its publisher as
European directory of freight carriers: find carriers by route, equipment and certificates.
Listing
From the official MCP registry (active).
Recent checks of Fitralo
CheckedResultHandshake
16 minutes agoHandshake completed304 ms
9 days agoHandshake completed373 ms
9 days agoHandshake completed385 ms
11 days agoFailed - the request timed out—
12 days agoHandshake completed328 ms
13 days agoHandshake completed313 ms
14 days agoHandshake completed290 ms
14 days agoHandshake completed413 ms
16 days agoHandshake completed825 ms
19 days agoHandshake completed288 ms
21 days agoHandshake completed509 ms
24 days agoHandshake completed332 ms
26 days agoHandshake completed310 ms
28 days agoHandshake completed311 ms

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

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