Remote MCP · Endpoint
Hunter Lease MCP server
No. Hunter Lease answered an MCP handshake 53 minutes ago.
UpLast checked 53 minutes ago
Server URL
https://hunter.lease/mcp
The last check completed an MCP handshake.
- Registry name
- lease.hunter/car-deals
- Transport
- Streamable HTTP
- Protocol negotiated
- 2025-06-18
- Handshake latency
- 434 ms
- Tools exposed
- 3 tools
- Uptime, last 30 days
- 100% from 5 checks
- Described by its publisher as
- Find new cars to lease or finance in California and calculate payments by credit tier.
- Website
- https://hunter.lease/
- Listing
- From the official MCP registry (active).
| Checked | Result | Handshake |
|---|---|---|
| 53 minutes ago | Handshake completed | 434 ms |
| 3 days ago | Handshake completed | 309 ms |
| 12 days ago | Handshake completed | 232 ms |
| 13 days ago | Handshake completed | 144 ms |
| 14 days ago | Handshake completed | 174 ms |
The last 5 checks. Full history is kept for 30 days; the all-time counter stands at 5 responding of 5.
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 Hunter Lease and makes no claim about it beyond what these checks measured.