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
598 ms
Tools exposed
6 tools
Uptime, last 30 days
100% from 17 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).
Recent checks of com.trip1/mcp
CheckedResultHandshake
1 hour agoHandshake completed598 ms
2 days agoHandshake completed433 ms
4 days agoHandshake completed388 ms
5 days agoHandshake completed454 ms
7 days agoHandshake completed408 ms
8 days agoHandshake completed384 ms
9 days agoHandshake completed473 ms
12 days agoHandshake completed406 ms
13 days agoHandshake completed463 ms
15 days agoHandshake completed452 ms
16 days agoHandshake completed436 ms
18 days agoHandshake completed424 ms
19 days agoHandshake completed408 ms
20 days agoHandshake completed416 ms
20 days agoHandshake completed452 ms
21 days agoHandshake completed444 ms
22 days agoHandshake completed136 ms

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.

Related

All hosted MCP serversGlide connector for AI assistantsGlide for AI agents

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.