Remote MCP · Endpoint
Dim Hour MCP server
No. Dim Hour answered an MCP handshake 1 hour ago.
UpLast checked 1 hour ago
Server URL
https://mcp.dimhour.com/mcp
The last check completed an MCP handshake.
- Registry name
- com.dimhour/catalog
- Transport
- Streamable HTTP
- Protocol negotiated
- 2025-06-18
- Handshake latency
- 43 ms
- Tools exposed
- 9 tools
- Uptime, last 30 days
- 100% from 17 checks
- Described by its publisher as
- Search 19,000+ verified places to eat and drink across 24 cities, each with a 0-100 quality score.
- Website
- https://dimhour.com/
- Repository
- https://github.com/Dim-hour/Dim-Hour
- Listing
- From the official MCP registry (active).
| Checked | Result | Handshake |
|---|---|---|
| 1 hour ago | Handshake completed | 43 ms |
| 2 days ago | Handshake completed | 577 ms |
| 4 days ago | Handshake completed | 3.14 s |
| 5 days ago | Handshake completed | 279 ms |
| 7 days ago | Handshake completed | 528 ms |
| 8 days ago | Handshake completed | 1.15 s |
| 9 days ago | Handshake completed | 889 ms |
| 12 days ago | Handshake completed | 558 ms |
| 13 days ago | Handshake completed | 3.08 s |
| 15 days ago | Handshake completed | 348 ms |
| 16 days ago | Handshake completed | 486 ms |
| 17 days ago | Handshake completed | 280 ms |
| 18 days ago | Handshake completed | 364 ms |
| 19 days ago | Handshake completed | 239 ms |
| 20 days ago | Handshake completed | 614 ms |
| 21 days ago | Handshake completed | 320 ms |
| 22 days ago | Handshake completed | 2.36 s |
The last 17 checks. Full history is kept for 30 days; the all-time counter stands at 17 responding of 17.
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 Dim Hour and makes no claim about it beyond what these checks measured.