Remote MCP · Endpoint

Trail Fortress Fitment MCP server

No. Trail Fortress Fitment answered an MCP handshake 2 hours ago.

UpLast checked 2 hours ago

Server URL

https://trailfortress.com/mcp/

The last check completed an MCP handshake.

Registry name
com.trailfortress/fitment
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
73 ms
Tools exposed
6 tools
Uptime, last 30 days
100% from 15 checks
Described by its publisher as
Free, read-only truck and Jeep parts fitment: what fits your vehicle, fit checks, tire sizes.
Listing
From the official MCP registry (active).
Recent checks of Trail Fortress Fitment
CheckedResultHandshake
2 hours agoHandshake completed73 ms
2 days agoHandshake completed72 ms
4 days agoHandshake completed88 ms
6 days agoHandshake completed67 ms
8 days agoHandshake completed70 ms
10 days agoHandshake completed70 ms
12 days agoHandshake completed97 ms
13 days agoHandshake completed182 ms
14 days agoHandshake completed72 ms
16 days agoHandshake completed150 ms
18 days agoHandshake completed146 ms
20 days agoHandshake completed69 ms
21 days agoHandshake completed61 ms
23 days agoHandshake completed132 ms
24 days agoHandshake completed144 ms

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

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