Remote MCP · Endpoint

DERATE — truck fault codes MCP server

No. DERATE — truck fault codes answered an MCP handshake 2 hours ago.

UpLast checked 2 hours ago

Server URL

https://derate.app/mcp

The last check completed an MCP handshake.

Registry name
app.derate/derate
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
1.07 s
Tools exposed
15 tools
Uptime, last 30 days
100% from 15 checks
Described by its publisher as
Heavy-duty truck SPN/FMI and OBD fault codes: meaning, safe-to-drive verdict, parts and recalls.
Listing
From the official MCP registry (active).
Recent checks of DERATE — truck fault codes
CheckedResultHandshake
2 hours agoHandshake completed1.07 s
1 day agoHandshake completed860 ms
3 days agoHandshake completed1.01 s
3 days agoHandshake completed1.46 s
4 days agoHandshake completed885 ms
5 days agoHandshake completed796 ms
7 days agoHandshake completed844 ms
10 days agoHandshake completed1.05 s
12 days agoHandshake completed550 ms
15 days agoHandshake completed1.02 s
17 days agoHandshake completed1.37 s
19 days agoHandshake completed988 ms
21 days agoHandshake completed1.33 s
23 days agoHandshake completed957 ms
25 days agoHandshake completed540 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 DERATE — truck fault codes and makes no claim about it beyond what these checks measured.