Remote MCP · Endpoint

Rack Warehouse fitment MCP server

No. Rack Warehouse fitment answered an MCP handshake 5 hours ago.

UpLast checked 5 hours ago

Server URL

https://mcp.rackwarehouse.com/mcp

The last check completed an MCP handshake.

Registry name
com.rackwarehouse/fitment
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
36 ms
Tools exposed
5 tools
Uptime, last 30 days
100% from 14 checks
Described by its publisher as
What fits your vehicle at Rack Warehouse: roof racks, carriers, truck and ladder racks.
Listing
From the official MCP registry (active).
Recent checks of Rack Warehouse fitment
CheckedResultHandshake
5 hours agoHandshake completed36 ms
9 days agoHandshake completed35 ms
10 days agoHandshake completed37 ms
11 days agoHandshake completed32 ms
12 days agoHandshake completed34 ms
14 days agoHandshake completed44 ms
14 days agoHandshake completed47 ms
15 days agoHandshake completed54 ms
17 days agoHandshake completed35 ms
19 days agoHandshake completed42 ms
21 days agoHandshake completed41 ms
24 days agoHandshake completed39 ms
26 days agoHandshake completed35 ms
28 days agoHandshake completed34 ms

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

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