Remote MCP · Endpoint

RevvedUpCars True Cost Index MCP server

No. RevvedUpCars True Cost Index answered an MCP handshake 1 hour ago.

UpLast checked 1 hour ago

Server URL

https://revvedupcars.com/api/mcp

The last check completed an MCP handshake.

Registry name
com.revvedupcars/true-cost-index
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
652 ms
Tools exposed
4 tools
Uptime, last 30 days
100% from 14 checks
Described by its publisher as
What a new car costs a month to own in the US: loan, insurance, maintenance, fuel. No key.
Listing
From the official MCP registry (active).
Recent checks of RevvedUpCars True Cost Index
CheckedResultHandshake
1 hour agoHandshake completed652 ms
2 days agoHandshake completed90 ms
4 days agoHandshake completed96 ms
6 days agoHandshake completed80 ms
8 days agoHandshake completed105 ms
10 days agoHandshake completed100 ms
12 days agoHandshake completed97 ms
14 days agoHandshake completed201 ms
15 days agoHandshake completed128 ms
16 days agoHandshake completed500 ms
18 days agoHandshake completed96 ms
20 days agoHandshake completed62 ms
22 days agoHandshake completed85 ms
24 days agoHandshake completed115 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 RevvedUpCars True Cost Index and makes no claim about it beyond what these checks measured.