Remote MCP · Endpoint

Trail Fortress Fitment MCP server

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

UpLast checked 6 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
78 ms
Tools exposed
6 tools
Uptime, last 30 days
100% from 14 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
6 hours agoHandshake completed78 ms
9 days agoHandshake completed167 ms
10 days agoHandshake completed198 ms
11 days agoHandshake completed186 ms
12 days agoHandshake completed251 ms
14 days agoHandshake completed86 ms
15 days agoHandshake completed83 ms
15 days agoHandshake completed186 ms
17 days agoHandshake completed75 ms
19 days agoHandshake completed67 ms
22 days agoHandshake completed91 ms
24 days agoHandshake completed73 ms
26 days agoHandshake completed72 ms
28 days agoHandshake completed88 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 Trail Fortress Fitment and makes no claim about it beyond what these checks measured.