# com.peek/mcp (remote · mcp.peek.com)

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

- Trust score: 63/100 (medium)
- Change this week: +3
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-08-03

## Components

- remote · `mcp.peek.com`: 63/100 (this document), [markdown](https://verifymcp.io/servers/com-peek-mcp/mcp.md), [page](https://verifymcp.io/servers/com-peek-mcp/mcp)

## Channel facts

- Endpoint: `https://mcp.peek.com`
- Transports: `streamable-http`
- Auth: `none`
- Version: `0.1.0`

## Trust breakdown

How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-08-03.

- **Endpoint Security**: 57/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - Authorisation not fully verified: no authorisation is required to call this server, and 6 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe.
  - HTTPS is enforced; there's no plaintext access path.
  - HSTS check failed: the Strict-Transport-Security header is absent.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 71/100
  - AI-judged instruction clarity (good).
  - Tool/resource definitions use about 573 tokens (~95/item across 6 items; 6 tools + 0 resources), lean.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 27/100
  - Stability observed for 8 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
- **Capabilities**: 40/100
  - Spec-recency check failed: implements MCP spec 2025-03-26; the latest is 2026-07-28.

## Install

### Claude

```bash
claude mcp add --transport http com-peek-mcp https://mcp.peek.com/
```

### Codex

```toml
[mcp_servers.com-peek-mcp]
url = "https://mcp.peek.com/"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "com-peek-mcp": {
      "type": "remote",
      "url": "https://mcp.peek.com/",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add com-peek-mcp --url https://mcp.peek.com/ --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  com-peek-mcp:
    url: "https://mcp.peek.com/"
```

### Other

```json
{
  "mcpServers": {
    "com-peek-mcp": {
      "type": "http",
      "url": "https://mcp.peek.com/"
    }
  }
}
```

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-08-03 (score 63, +1)

No change was recorded against any check on this day. Stability & Change Management went from 23 to 27. That category is still filling its 30-day observation window: 7 days of observed history at the previous scan, 8 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-07-31 (score 62, 0)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-07-30 (score 62, +1)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-07-28 (score 61, +1)

No change was recorded against any check on this day. Stability & Change Management went from 3 to 7. That category is still filling its 30-day observation window: 1 days of observed history at the previous scan, 2 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-07-27 (score 60, +1)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-07-26 (score 59)

First indexed and scored.

## MCP tools (6)

### `experience_availability` (~112 tokens)

Get availability information for a specific experience including dates, times, and pricing

Input parameters:

- `endDate` (string, required): End date inclusive in YYYY-MM-DD format (e.g., '2025-06-20' would return things taking place ON or BEFORE the 20th)
- `id` (string, required): The ID of the experience
- `quantity` (integer, required): Number of travelers
- `startDate` (string, required): Start date inclusive YYYY-MM-DD format (e.g., '2025-06-19')

### `experience_details` (~32 tokens)

Get detailed information about a specific experience by ID

Input parameters:

- `id` (string, required): The ID of the experience to retrieve

### `list_tags` (~13 tokens)

List all category tags

### `render_activity_tiles` (~46 tokens)

Render activity tiles for a list of activity IDs, returning an embeddable widget URI

Input parameters:

- `id` (string, required): ID or comma separate list of activity IDs to render as tiles

### `search_experiences` (~324 tokens)

Search for travel experiences with comprehensive filtering options. Returns available categories, tags, and regions with IDs for further filtering.

Input parameters:

- `categoryId` (string): Limit to only a specific activity category
- `endDate` (string): Return experiences that are available on or before this date in YYYY-MM-DD format (e.g., '2025-06-20' would return things taking place ON or BEFORE the 20th)
- `latLng` (string): When the user wants something NEAR a specific place, but not necessarily IN a specific place, limit to only those near a given lat_lng. ex: "37.7799,-122.2822". Don't use this for regions, instead us…
- `query` (string): When the user wants something w/ a specific keyword (bike, beer, art, etc) limit to experiences whose title contain a keyword. Never include location information.
- `regionId` (string): When you have determined the user wants something in a specific region (found w/ search_regions) limit to only a specific region ID
- `startDate` (string): Return experiences that are available on or after this date. YYYY-MM-DD format (e.g., '2025-06-19')
- `tagId` (string): When you have determined the user is interest in a specific vibe of activity (family friendly, romantic, etc) limit to only experiences with a specific tag (single tag ID)

### `search_regions` (~46 tokens)

Search for regions by name

Input parameters:

- `limit` (integer): Maximum number of regions to return (default: 50)
- `query` (string, required): Search query to match against region names

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/com-peek-mcp/mcp#diagnostics

## Score history

- 2026-08-03: 63
- 2026-08-02: 62
- 2026-08-01: 62
- 2026-07-31: 62
- 2026-07-30: 62
- 2026-07-29: 61
- 2026-07-28: 61
- 2026-07-27: 60
- 2026-07-26: 59

## Links

- Remote endpoint: https://mcp.peek.com/
- Changelog RSS feed: https://verifymcp.io/servers/com-peek-mcp/mcp/changelog.xml
- Changelog JSON feed: https://verifymcp.io/servers/com-peek-mcp/mcp/changelog.json
- HTML version of this page: https://verifymcp.io/servers/com-peek-mcp/mcp