Remote MCP · Endpoint
com.trip1/mcp MCP server
No. com.trip1/mcp answered an MCP handshake 1 hour ago.
UpLast checked 1 hour ago
Server URL
https://trip1.com/api/mcp
The last check completed an MCP handshake.
- Registry name
- com.trip1/mcp
- Transport
- Streamable HTTP
- Protocol negotiated
- 2025-06-18
- Handshake latency
- 429 ms
- Tools exposed
- 6 tools
- Uptime, last 30 days
- 100% from 18 checks
- Described by its publisher as
- Book hotels over MCP. Pay over x402. 3M+ properties in 200+ countries, USDC on Base.
- Website
- https://trip1.com/agents
- Repository
- https://github.com/trivial-corp/agents
- Listing
- From the official MCP registry (active).
| Checked | Result | Handshake |
|---|---|---|
| 1 hour ago | Handshake completed | 429 ms |
| 1 day ago | Handshake completed | 413 ms |
| 2 days ago | Handshake completed | 505 ms |
| 3 days ago | Handshake completed | 152 ms |
| 4 days ago | Handshake completed | 421 ms |
| 5 days ago | Handshake completed | 431 ms |
| 6 days ago | Handshake completed | 819 ms |
| 9 days ago | Handshake completed | 440 ms |
| 12 days ago | Handshake completed | 425 ms |
| 14 days ago | Handshake completed | 426 ms |
| 16 days ago | Handshake completed | 151 ms |
| 18 days ago | Handshake completed | 444 ms |
| 20 days ago | Handshake completed | 598 ms |
| 22 days ago | Handshake completed | 433 ms |
| 24 days ago | Handshake completed | 388 ms |
| 26 days ago | Handshake completed | 454 ms |
| 27 days ago | Handshake completed | 408 ms |
| 28 days ago | Handshake completed | 384 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 com.trip1/mcp and makes no claim about it beyond what these checks measured.