Remote MCP · Endpoint

com.peek/mcp MCP server

No. com.peek/mcp answered an MCP handshake 1 hour ago.

UpLast checked 1 hour ago

Server URL

https://mcp.peek.com/

The last check completed an MCP handshake.

Registry name
com.peek/mcp
Transport
Streamable HTTP
Protocol negotiated
2025-03-26
Handshake latency
106 ms
Tools exposed
6 tools
Uptime, last 30 days
100% from 17 checks
Described by its publisher as
Build travel itineraries with Peek's 300k+ experiences. Search, details, and availability.
Listing
From the official MCP registry (active).
Recent checks of com.peek/mcp
CheckedResultHandshake
1 hour agoHandshake completed106 ms
2 days agoHandshake completed100 ms
4 days agoHandshake completed101 ms
5 days agoHandshake completed113 ms
7 days agoHandshake completed118 ms
8 days agoHandshake completed99 ms
9 days agoHandshake completed105 ms
12 days agoHandshake completed123 ms
13 days agoHandshake completed132 ms
15 days agoHandshake completed103 ms
16 days agoHandshake completed120 ms
17 days agoHandshake completed113 ms
18 days agoHandshake completed114 ms
19 days agoHandshake completed102 ms
20 days agoHandshake completed109 ms
21 days agoHandshake completed97 ms
22 days agoHandshake completed114 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.

Listing data comes from the official MCP registry. Glide is not affiliated with com.peek/mcp and makes no claim about it beyond what these checks measured.