Remote MCP · Endpoint

Track & Blade MCP server

No. Track & Blade answered an MCP handshake 2 hours ago.

UpLast checked 2 hours ago

Server URL

https://trackandblade.com/api/mcp

The last check completed an MCP handshake.

Registry name
com.trackandblade/listings
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
407 ms
Tools exposed
4 tools
Uptime, last 30 days
100% from 14 checks
Described by its publisher as
Marketplace for used construction equipment: read-only listings + OEM specs. Not seller of record.
Listing
From the official MCP registry (active).
Recent checks of Track & Blade
CheckedResultHandshake
2 hours agoHandshake completed407 ms
1 day agoHandshake completed104 ms
2 days agoHandshake completed153 ms
2 days agoHandshake completed164 ms
4 days agoHandshake completed173 ms
7 days agoHandshake completed148 ms
9 days agoHandshake completed144 ms
12 days agoHandshake completed99 ms
14 days agoHandshake completed122 ms
16 days agoHandshake completed102 ms
18 days agoHandshake completed68 ms
20 days agoHandshake completed76 ms
22 days agoHandshake completed411 ms
23 days agoHandshake completed72 ms

The last 14 checks. Full history is kept for 30 days; the all-time counter stands at 14 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 Track & Blade and makes no claim about it beyond what these checks measured.