Remote MCP · Endpoint
com.getvaletparking/valet-parking-directory MCP server
No. com.getvaletparking/valet-parking-directory answered an MCP handshake 1 hour ago.
UpLast checked 1 hour ago
Server URL
https://api.getvaletparking.com/mcp
The last check completed an MCP handshake.
- Registry name
- com.getvaletparking/valet-parking-directory
- Transport
- Streamable HTTP
- Protocol negotiated
- 2025-06-18
- Handshake latency
- 991 ms
- Tools exposed
- 8 tools
- Uptime, last 30 days
- 100% from 19 checks
- Described by its publisher as
- MCP server for valet parking: 789 US operators across 31,186 cities. 7 tools. No auth.
- Listing
- From the official MCP registry (active).
| Checked | Result | Handshake |
|---|---|---|
| 1 hour ago | Handshake completed | 991 ms |
| 18 hours ago | Handshake completed | 933 ms |
| 2 days ago | Handshake completed | 803 ms |
| 3 days ago | Handshake completed | 818 ms |
| 4 days ago | Handshake completed | 1.16 s |
| 5 days ago | Handshake completed | 966 ms |
| 6 days ago | Handshake completed | 956 ms |
| 7 days ago | Handshake completed | 883 ms |
| 10 days ago | Handshake completed | 965 ms |
| 13 days ago | Handshake completed | 444 ms |
| 15 days ago | Handshake completed | 889 ms |
| 17 days ago | Handshake completed | 524 ms |
| 19 days ago | Handshake completed | 677 ms |
| 21 days ago | Handshake completed | 705 ms |
| 23 days ago | Handshake completed | 867 ms |
| 25 days ago | Handshake completed | 934 ms |
| 27 days ago | Handshake completed | 939 ms |
| 28 days ago | Handshake completed | 749 ms |
| 29 days ago | Handshake completed | 459 ms |
The last 19 checks. Full history is kept for 30 days; the all-time counter stands at 30 responding of 30.
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 com.getvaletparking/valet-parking-directory and makes no claim about it beyond what these checks measured.