mcpbeat

Peek MCP Server

com.peek/mcp
answering

Peek is answering right now. Last checked 14 min ago. It exposes 6 tools.

Build travel itineraries with Peek's 300k+ experiences. Search, details, and availability.

Uptime history 39 hours of history
39 hours agonow
100.0%
Uptime 24h
91 of 91 checks
6
Tools
read from the server
375 ms
Response time
average over 24h
open, no key
Access
streamable-http

Connect this server

Endpoint below is the one we actually reach during checks — not the one copied from a README. Last verified 14 min ago.

run in your terminal
claude mcp add mcp --transport http https://mcp.peek.com
~/Library/Application Support/Claude/claude_desktop_config.json
{
  "mcpServers": {
    "mcp": {
      "url": "https://mcp.peek.com"
    }
  }
}
~/.codex/config.toml
[mcp_servers.mcp]
url = "https://mcp.peek.com"
.cursor/mcp.json
{
  "mcpServers": {
    "mcp": {
      "url": "https://mcp.peek.com"
    }
  }
}
.vscode/mcp.json
{
  "mcpServers": {
    "mcp": {
      "url": "https://mcp.peek.com"
    }
  }
}

Available tools 6

Read directly from the server with tools/list, grouped by what they act on. If a tool disappears, we record the date.

experience
experience_availability
Get availability information for a specific experience including dates, times, and pricing
experience_details
Get detailed information about a specific experience by ID
experiences
search_experiences
Search for travel experiences with comprehensive filtering options. Returns available categories, tags, and regions with IDs for further filtering.
regions
search_regions
Search for regions by name
render
render_activity_tiles
Render activity tiles for a list of activity IDs, returning an embeddable widget URI
tags
list_tags
List all category tags

Endpoints

URLTransportStateLatencyChecked
https://mcp.peek.com streamable-http answering 406 ms 14 min ago

Peek — questions

Answers built from our own checks of this server.

What can Peek do?
It exposes 6 tools, read directly from the server on our last check. Among them: experience_availability, experience_details, list_tags, render_activity_tiles, search_experiences, search_regions. The full list with descriptions is on this page — we take it from the server itself via tools/list, not from a README. How MCP servers expose tools in the first place →
Is Peek working right now?
We send a real MCP handshake every 15 minutes. Over the last 24 hours 91 of 91 checks got a reply (100.0%), average response time 375 ms. The bar chart above shows every period we have measured.
How do I connect Peek?
Copy the ready config from this page — we generate it for Claude Code, Claude Desktop, Codex, Cursor and VS Code, each with the file path that client actually reads. It is a remote server, so there is nothing to install — the client connects to the address.
Does Peek need an API key?
No. Peek completed a full MCP handshake with us as an anonymous client and listed its tools without asking for anything. All 6 of them are readable on this page. This is what we observed, not what the docs claim.
How fast is Peek?
It answers our handshake in 375 ms on average, which is faster than 37% of all working MCP servers we measure. The comparison comes from our own checks across the whole registry, every 15 minutes.