Remote MCP · Endpoint
POS.DO MCP Server MCP server
No. POS.DO MCP Server answered an MCP handshake 1 hour ago.
UpLast checked 1 hour ago
Server URL
https://pos.do/mcp
The last check completed an MCP handshake.
- Registry name
- io.github.posdo-io/mcp-server
- Transport
- Streamable HTTP
- Protocol negotiated
- 2024-11-05
- Handshake latency
- 552 ms
- Tools exposed
- 7 tools
- Uptime, last 30 days
- 100% from 18 checks
- Described by its publisher as
- Discover 356K+ restaurants in 20 countries: search, reviews, cultural context, time-based offers.
- Website
- https://pos.do/
- Repository
- https://github.com/posdo-io/mcp-server
- Listing
- From the official MCP registry (active).
| Checked | Result | Handshake |
|---|---|---|
| 1 hour ago | Handshake completed | 552 ms |
| 1 day ago | Handshake completed | 532 ms |
| 2 days ago | Handshake completed | 387 ms |
| 3 days ago | Handshake completed | 438 ms |
| 4 days ago | Handshake completed | 414 ms |
| 5 days ago | Handshake completed | 557 ms |
| 6 days ago | Handshake completed | 439 ms |
| 9 days ago | Handshake completed | 429 ms |
| 11 days ago | Handshake completed | 362 ms |
| 14 days ago | Handshake completed | 527 ms |
| 16 days ago | Handshake completed | 446 ms |
| 18 days ago | Handshake completed | 441 ms |
| 20 days ago | Handshake completed | 758 ms |
| 22 days ago | Handshake completed | 416 ms |
| 24 days ago | Handshake completed | 380 ms |
| 26 days ago | Handshake completed | 423 ms |
| 28 days ago | Handshake completed | 524 ms |
| 29 days ago | Handshake completed | 565 ms |
The last 18 checks. Full history is kept for 30 days; the all-time counter stands at 29 responding of 29.
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 POS.DO MCP Server and makes no claim about it beyond what these checks measured.